this post was submitted on 28 Jun 2023
30 points (94.1% liked)

Selfhosted

40226 readers
1049 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 posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Or maybe a two click solution? :)

you are viewing a single comment's thread
view the rest of the comments
[–] Disregard3145@lemmy.world 11 points 1 year ago (13 children)

Self hosting what?

In general

  1. Install docker
  2. Copy and paste docker run commands from the getting started guide
  3. Learn from mistakes
[–] aeternum@kbin.social 1 points 1 year ago (2 children)

It's so easy to self host these days. I remember when you'd have to fuck around with Apache configs and fuck around with app config files etc. Now you just run docker. It's so great these days!

[–] zib@kbin.social 1 points 1 year ago (1 children)

I'm still fucking with the apache configs (I fucking hate apache...). As someone with no docker experience whatsoever, are there any getting started guides you would recommend for someone looking to make the switch?

[–] aeternum@kbin.social 1 points 1 year ago* (last edited 1 year ago)

I don't have any specific guides in mind, but you'll want to use docker-compose as much as possible, also create /home/your_user/docker/app/ for each app, and keep your docker compose files. If you use docker run, keep a copy of the commands you use, because if you need to restart your services, it will be a lot easier than having to search up the command in your bash history again. You can just cat docker.txt | bash and it will recreate your docker containers for you. That's all i can really think of for getting started. Also, docker ps will be a godsend.

load more comments (10 replies)