Homelab

938 readers

54 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 2 years ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

What is the most painful step on setting up a homelab in your experience? (alien.top)

submitted 2 years ago by submain@alien.top to c/homelab@selfhosted.forum

68 comments fedilink hide all child comments

For me it is writting docker compose files describing my services. I like to test them on my machine before pushing them to the server(s). But I guess that's my own fault for not using something like portainer or even SSHFS.

What's the most annoying / painful step for you?

you are viewing a single comment's thread
view the rest of the comments

[–] disguy2k@alien.top 1 points 2 years ago

You can have a central repo for your files. I have a different folder for each server. VSCode has access to these folders to edit any data needed.

Most of the compose files are managed in Portainer, but some of the containers need to exist outside of Portainer.