this post was submitted on 24 Oct 2024
33 points (88.4% liked)

Selfhosted

59939 readers
313 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
33
Where to start as a beginner (lemm.ee)
submitted 2 years ago by BobGnarley@lemm.ee to c/selfhosted@lemmy.world
16 comments fedilink hide all child comments
 

My ultimate goal with learning this is I want to self host my own Monero node and eventually maybe even self host emails and after that learn docker as well.

But I am a long, long way from there.

Where do I start with something like this if I have no experience with networking?

Should I just start with learning a VPS? I just don't like the idea of me not being able to physically control the server because I think one day Monero might be outlawed or something.

But I'll do whatever I have to to learn.

you are viewing a single comment's thread
view the rest of the comments
[–] brewery@lemmy.world 1 points 2 years ago

My experience has taught me not to 'apt autoremove' unless im really sure what they are!

Take it one software at a time. See it's running fine then move on to another. You'll often realise something down the line will be helpful so will go back to make changes.

Keep a running list of software and the ports used.

With docker, do not automatically do :latest on important software (nginx proxy manager, SSO software, password database, anything you use regularly, etc). I did that and was burned a few times.

Also that at some point you'll either mess up or realise it would just be easier and start again with a fresh OS install. Keep copying data (docker compose files and persistent storage) on working software before starting a new one, or before installing anything directly onto the OS, or before major updates.