mandatory reviews on code before merging (PR) with mandatory fixes.
This one. Open PR, review by at least one peer, address concerns, merge.
Code review is not punishment - it’s part of your job. You should be willing and able to provide meaningful feedback to your peers. It also gives the team an opportunity to see how other people write code and to agree on norms and standards.
You’re talking a lot of storage - it might be worth investing in some low-end server hardware. A Dell tower or something, maybe one off eBay if you’re looking to cut costs.
I picked up a PowerEdge T110II a long time ago and it’s been… flawless. Just a simple server with a 4x4TB RAID5. No hardware problems (aside from occasional disk failures over the years), easy to manage. It costs a bit more - but server hardware is often just more reliable and for a NAS that’s job #1. This server just runs.
I just upgraded the memory in it to 32GB for ~$100USD. Before that it had 8GB. I needed more for restic doing backups. I probably could have gotten away with 16GB but I figured I’d max it out for that price.
Wow, this question takes me back to like the 00’s when laptops had battery life measured in minutes.
How about “no”.
This week - Apache Airflow setup to automate running backups (replacing cron).
I love how you came up with a completely different scenario to answer “yes” to .
You willing to go to jail then? Or just asking others to do so?
Probably because it’s not illegal.
When you open and read files from a program the OS (kernel) will typically cache part or all of those files in memory. This is to speed up subsequent reads of that file since disk access is slow.
“preload” seems to be making use of that feature.
The kernel maintains this cache and evicts (unloads) things from it as needed. You don’t need to worry about it.
Gonna make provisioning servers a lot more interesting…
Their community still a cespool?
Man, what’s up with Linux filesystem developers?
Compared to checks notes reinstalling an entirely different distro???
Jesus the cli phobia here is ridiculous.
While learning about all the Linux stuff I came to know about desktops, and I felt like, if I wanted to ever use a different one, yes, it could be installed the hard way, but I would rather have a distro that can be installed with my desired desktop by default, and the one that got my attention was KDE.
‘sudo apt install kde-full’ is “the hard way”?
I’ve been accused of “gate keeping” when I tell people that this is a shitty way to deploy applications and that nobody should do it.
No shit. Why would they even say that?
Ahhh, self doubt, my old friend…
“There is probably a better way” is a fairly common feeling. In fact there probably is a better way. But at some point you need to be pragmatic and be happy with “good enough”. Don’t let perfect be the enemy of good (enough) as they say…
That said - follow your intuitions as well that things could be done better. Don’t be afraid to just re-write a bunch of things to see if an idea works better. Like grouping things from some “common.php” into domain specific functionality (dates.php, db.php, etc.). Or re-working how your front-end works. Maybe read other code or ask for code review from people more experienced, or even from an AI (yes, yes, I know, but they can be useful).
One problem you can find yourself in is that you’ve created code that’s very difficult to understand, but since you’re “in it” right now you understand it completely. If you put the code down for a week or two and come back to it you may find it very difficult to re-learn. If using classes, creating a DAO layer, or some other pattern helps to make your code easier to read then it’s worth following.
Some people get into self hosting because they want their data to be their data. They don’t care about the particulars, they just want that peace of mind.
These people are the worst. What they want is fine - but the idea that you don’t need to worry about the particulars is ridiculous.
Networking. If you want to understand the reasoning behind things this is where you start. A good foundation in tcp/ip, the 7 layer network stack, as well as basic network protocols (dns, dhcp, http, etc.) will go a long way toward helping you troubleshoot when things go wrong.
Maybe throw in some operating systems study as well for when you start to use docker.