Does there need to be a need? Some people just like to create things to see if they can. Some people like TUIs. There may not be a huge need for this, but it’s pretty freaking awesome to have.
Does there need to be a need? Some people just like to create things to see if they can. Some people like TUIs. There may not be a huge need for this, but it’s pretty freaking awesome to have.
Oof. Thanks. I deleted mine as well. Never really use it anyway because I was always afraid of what they might do with my money.
Yes, you have iptables and nftables, but it’s not always enabled. So, when I said installed, I really meant enabled. I 100% agree with what you are saying though.
Unfortunately a lot of places just have shitty IT and people go rogue because of it. Some people are just impatient though as it sounds like in this case.
You also have things like apparmor and selinux. If those are enabled, you might be chasing your tail trying to figure out why something is not working. You would need to know where to look and how to fix it.
This story has nothing to do with why Linux would be any better than Windows. Sure, if you lie to people, then anything can be convincing. What if I had a firewall installed in Linux, wouldn’t you have had the same issues?
This is sort of the problem I have with a lot of Linux enthusiasts, when you have a hammer, everything is a nail.
Compared to Windows and MacOS as a client desktop, Linux still severely falls behind, but it is getting better. For a server, Linux is just far superior.
I didn’t even know this was a thing. This worked for me.
The status code that gets returned should be the status code of the messenger and not the data. If you want to add a status code about the data, then please do.
If something can return null and empty and it’s valid, that is not a 404. That is a 200.
As far as a 403, the messenger is telling you that you shall not pass. There is no data. 403 is appropriate here. The return response can be anything since 403 is pretty self explanatory, but I would probably return json to be consistent. I would also use the field message. Something like the first one for this use case only.
In other cases where i do get data, I would use data, message, status (optional). But status in the json response would be status about the message.
Somewhat, but just a few pieces of it. Podman build is mainly a way to be backwards compatible with the docker cli. Buildah has some more flexibility and the way it builds the images are slightly different. You can use podman to build, but it’s probably better to move to buildah for the build step as time permits.
You typically don’t use podman to build images and you would instead use something like buildah.
If you don’t want to use a hosted provider, you can at least just start using git. Just do git init. Then you can start commiting changes. This way, you at least have a history of changes. Then just back that folder up like normal
You can use a few tools.
RSync
Rclone - probably want this one over RSync though.
Tarsnap
Duplicati
Restic
There’s obviously a lot more, but these are some of the more popular ones.
Now you need a way to back it up. Probably the best way is to tar it up first and then dump that file. You can also get something like deadmans snitch to ensure backups don’t break.
As you mentioned, if this is just source code, then the best thing would be to create source control and have it set up that way. Then you automate it and deploy the code when you make updates and have a history of changes.
It sounds like tarsnap is your best bet though. It will be the cheapest.
You can also backup to another storage provider like Google, Dropbox, or even AWS s3. S3 can get costly, but you can archive everything to the glacier tier which is pretty cheap.
I know what you mean. There are tools I see everyday and I ask, but why? I have started to just ask, why not? There doesn’t always have to be a use case and sometimes people just want to create shit. They don’t even care if others use it, but want to share it anyway in case there is that one other person that does.