2 ms·
My two primary tips: 1) Keep notes as you set it up. Include problems you encountered and what the solution was, develop lists of how to install and configure
by JohnFen 3y ago
My two primary tips:
1) Keep notes as you set it up. Include problems you encountered and what the solution was, develop lists of how to install and configure the various services so you can refer to them should you need to reinstall things in the future.
2) Do it one service at a time and get each service completely running before starting on the next. Your server isn't a single thing, it's a home for multiple things. Do each of those one at a time.
- goat-throwaway 3y ago> Keep notes as you set it up. This. I still have a 10 year old server setup file that I refer whenever I am setting up a new server.
- amingilani 3y agoIn the off chance you don’t keep notes, I’ve found reconstructing what happened on the server from its history to be invaluable. I once joined a company after they ran out of backend engineers and had to restore a server from a backup. Figuring out how to bring all the services up based on history was a fun ride.
- Ensorceled 3y agoTrouble shooting problems caused by someone else this way is also fun... "I see, they edited the nginx config ... let's check out what they did."
- Ensorceled 3y agoI'd recommend a note taking app, something like Obsidian, and create a page for each new service you set up. Copy the commands and add notes to this file. Later, when you upgrade or modify the service, you can keep adding to this notes. Also, copy any configuration files OFF the server and into you notes when you are done editing them.
- ctxc 3y agoI use obsidian, but brought my old hierarchical folder structure mentality into it. I now think I just should've created single files and let the auto-linking take care of the hierarchy. What do you think?
- Ensorceled 3y agoI have a folder called operations/recipes and I put separate files in that folder. I have files like nginx, supervisor, etc. etc.
- 20after4 3y agoIt may not be appropriate for a complete beginner, such as the OP, however, ideally setups should be documented by using a configuration management tool like Ansible, puppet, terraform, docker, etc. This way the setup is easily reproducible. The best notes are executable notes.
- ctxc 3y agoYeah I think I'll try Ansible out. Maybe play around a bit with the bare instance and redo it with Ansible.
- ctxc 3y agoThanks, I try to do it with my normal dev process as well. "preferably one unknown at a time" I call it, although I always end up wishing I had more notes. At least my blog would have more than 5 entries if I had half decent notes. But never too late eh :P