I think I know what happened. Did you do something like
PATH="/usr/bin/golang"?
Because doing that overwrite your path variable. You need to set it like this:
PATH="{PATH}:/usr/bin/golang" to append to the path.
And well… I hope you got a backup of your /root/.bashrc or whatever you use as a terminal. Restoring it should fix it
Edit: you should be able to use any program by appending /usr/bin/ to your commands, as long as it’s in this directory
Now do brainpower
Good job. I fell for it
Beware of child predators
Usb killer: you guys do things with the computer?
I think the meme refers to the joke that “all guys just want a big tiddy goth girlfriend” meme.
The bottom text is just a joke to divert from the obvious meme
No idea for Tiberius, but for SQLite I’m stuck with converting to timestamp and back. Ugly but works
P.S. add a getter to your data struct and you can be “seamless”
Sadly sqlx seems to have gone semi-proprietary with their MSQL driver. Personally never understood the appeal of mssql when there’s Postgres and SQLite, but hey, it does work.
I’ve started using welds as my new ORM of choice as SeaORM and Diesel is just not a friendly experience, and supports Mssql OOB. So it’s nice there’s still options for it.
Half joking. Lifetimes can be hard but once you understand the concept it’s quite easy.
The second joke is about you never learn Rust. You’re always on the learning rollercoaster. Always one step away but each time it makes you rethink the whole language.
Don’t get me wrong, I’m a rust main. But does issues does exist
Rewrite it in rust. Now get a lifetime of problems
Oh no. This is so bad. Who in their right mind would assume that a login user remains the same user throughout the session!?
Oh wait. Windows.
What? No! I leave at 6pm. (But start at 2)
I get 100m up front, right?
Right?
? I’m agreeing with you?
There’s a difference between helping people with misunderstanding a tool and belittling them for being wrong. It’s just a matter of wording that separate an helpful answer from a toxic one
I could tell you “You should actually use Y instead of X. They are numerous benefits like A, B and C. The doc actually have a great example you may have missed or not understood it was for this purpose. It will help you a lot more than what you are thinking of doing.” And this would be fine.
But “Just use Y. X is bad because Y is made for that. You not willing to use Y shouldn’t make you do X. There’s even a the first Google link on how to do it” isn’t fine.
And I have not belittled them at all. I have said that it wasn’t what I was looking for. A lot of times people post questions they think should solve their issue, but only to realise that they didn’t fully understand the full picture and theirs problem is on a larger scale.
Seems like the best solution. I’ll look into it
But can it prevent killing only docker, and not the build/big containers processes?
Oh that’s not a problem to let a container get killed. It’s perfectly fine. What I want is just not crippling my whole server because one container did a funny.
If it keeps docker and the portainer VM I’ll be 100% ok, because I can just restart it. I don’t want to have remote access to my server outside of my home for security reasons, so this is just the bare minimum
Netgear is one letter away from nepgear… So they must do other game consoles, right?