You can look at rclone’s docs on how to hook that into B2 (or wherever you’d like to dump your backups, B2 is jusut cheap). I also set up a crypt in rclone so it encrypts it as it uploads (optional).
Then just put those on cron jobs at different times, I do them every 6 hours. One at <hour>:15 and one at <hour>:45
Then in B2 I set the bucket to keep files for 10 days.
Thank you very much. Seriously, that lays it all out perfectly. I was looking at the pict-rs docs for how to switch but then work called… so I really appreciate you taking the time to do this. 🙌 🍾 🎉 🥂
Oh and for those scripts the user needs paswordless sudo and needs to be part of the docker group, or you could add it to root’s cron tab. Or maybe a systemd task. (Since the default ansible deploy of lemmy makes the pict-rs volume not readable by a normal system user)
You’re in the wrong field, my man. I sit at a chair 60 hours a week staring into a empty void that is my monitor. Wait, maybe we are not really that different after all.
I just really don’t know how to get in, while living in central Florida, with no degree, while not taking a pay cut which I can’t afford as the sole earner in my household :/
If you’re thinking about shifting careers, I’ve been there. I started as a self-learner with no degree, before the ease of joining a freelance service was a thing. My starting point was a small firm where I did tech support for the coders. I got involved in automation projects and gradually built trust by proving I could deliver what I promised.
I think that the core principles I learned remain valid today: Learn by doing projects, learn in public, and be patient.
If I was starting again, and if I didn’t have a job next to the right people, I’d probably do the following. Start with creating useful projects. Treat these as opportunities to learn and simulate real job conditions. If your work involves coding, share it on GitHub. If it’s about building infrastructure, treat it as Infrastructure as Code and share it on GitHub. If it’s not code-related, or even if it is, document your work and what you’ve learned on a blog.
Regardless of your project’s nature, make sure to record your learnings and pass on your knowledge. It helps reinforce your understanding and it gives you something to point to during interviews.
Reddit and Twitter are multimillion dollar enterprises
I’m just some fool who rents a little virtual server so I can help people use the fediverse
I mean I’m not even an IT guy by trade (just by hobby) - I’m a truck driver.
It’s a good thing it’s a virtual server. I can’t imagine the issues you would have if you hosted it from the back of your truck.
Hosting from the back of a truck would be a technological marvel in its own right.
Sat internet would be the solution. Just costs a lot.
It sounds like the plot of an action movie.
“We have to keep this truck above 50mph at all cost”
“OMG, IS IT GONNA EXPLODE?!”
“Oh no much worse. It’ll ruin my server uptime stat.”
Kinda like this: https://youtu.be/OLRldZjty_s
Here is an alternative Piped link(s): https://piped.video/OLRldZjty_s
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
Lmao I’m home every night now (local)
I do host some things at my house, but just for personal use. I don’t need a public site running on my home network.
I am an it guy and mine still goes down… Lol. Your doing great to get an instance going! That setup isn’t exactly non tech friendly.
Mine went down yesterday because my backup job for my docker vols filled up my entire vps.
I was starting to run into that until I moved pict-rs to object storage a few days back.
I gzip the backups, keep one local, upload the rest to Backblaze. The local one gets deleted before the next backup starts.
Oh that’s genius, you got any good docs on doing that?
For the backups I have these bash scripts (the pict-rs one takes much less time now that I use object storage so the images aren’t on the server): https://gist.github.com/bdonvr/5d4e56dadcb29de656368a1cb78cc00e
You can look at rclone’s docs on how to hook that into B2 (or wherever you’d like to dump your backups, B2 is jusut cheap). I also set up a crypt in rclone so it encrypts it as it uploads (optional).
Then just put those on cron jobs at different times, I do them every 6 hours. One at <hour>:15 and one at <hour>:45
Then in B2 I set the bucket to keep files for 10 days.
To migrate to object storage check pict-rs docs here: https://git.asonix.dog/asonix/pict-rs.git#user-content-filesystem-to-object-storage-migration
Took about 20 minutes for me with 30gb of files, but your instance has to be down for it. I use Cloudflare R2 for pict-rs.
Thank you very much. Seriously, that lays it all out perfectly. I was looking at the pict-rs docs for how to switch but then work called… so I really appreciate you taking the time to do this. 🙌 🍾 🎉 🥂
No problem
Oh and for those scripts the user needs paswordless sudo and needs to be part of the docker group, or you could add it to
root’s cron tab. Or maybe a systemd task. (Since the default ansible deploy of lemmy makes the pict-rs volume not readable by a normal system user)Finally got my stuff moved over to object storage. I really appreciate it. It wasn’t hard at all! THANK YOU
I cannot express my appreciation, and dude I assure you, you got bigger balls than elon’s chest
that’s about unrelated as I can think
awesome, I love technology accessibility
To be fair I’m also a huge fucking nerd
You’re in the wrong field, my man. I sit at a chair 60 hours a week staring into a empty void that is my monitor. Wait, maybe we are not really that different after all.
I just really don’t know how to get in, while living in central Florida, with no degree, while not taking a pay cut which I can’t afford as the sole earner in my household :/
If you’re thinking about shifting careers, I’ve been there. I started as a self-learner with no degree, before the ease of joining a freelance service was a thing. My starting point was a small firm where I did tech support for the coders. I got involved in automation projects and gradually built trust by proving I could deliver what I promised.
I think that the core principles I learned remain valid today: Learn by doing projects, learn in public, and be patient.
If I was starting again, and if I didn’t have a job next to the right people, I’d probably do the following. Start with creating useful projects. Treat these as opportunities to learn and simulate real job conditions. If your work involves coding, share it on GitHub. If it’s about building infrastructure, treat it as Infrastructure as Code and share it on GitHub. If it’s not code-related, or even if it is, document your work and what you’ve learned on a blog.
Regardless of your project’s nature, make sure to record your learnings and pass on your knowledge. It helps reinforce your understanding and it gives you something to point to during interviews.
My dude, if you’re renting and running a VPS you’re an IT guy.
truck drivers are basically IT anyways /j