this post was submitted on 07 Jul 2023
39 points (93.3% liked)

Selfhosted

40329 readers
713 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
 

I have Mastodon running on a VPS running Debian 11. Now I would like to add a Lemmy instance on the same server. I tried using the from scratch method from Lemmy documentation, but ran into errors that likely stemmed from minor version incompatibilities of the dependencies. I tried using the Lemmy easy deploy script but it wants to bind all traffic on port 443 for Lemmy which would break my Mastodon install. Has anyone managed to get Lemmy and Mastodon running on the same box, and if so, can you share any details of your setup?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (3 children)

I would personally recommend putting them both in Docker containers, but I'm glad it's working for you.

[–] TrinityTek 1 points 1 year ago (2 children)

Thanks for the suggestion. What would be the benefit of switching to a docker install of Mastodon?

[–] [email protected] 1 points 1 year ago (1 children)

Basically the whole point of docker is that it keeps all the fiddly junk involved in actually running an application separated off into its own little box where it can't affect the host system. So by taking one of those applications and putting it directly on the host system you're sort of undoing all that.

The idea is that the docker host basically shouldn't do anything other than run docker itself. That way there's minimal chance of anything getting screwy. Also using docker installs for all your critical apps means that you can use Watchtower to auto update them, which is a nice bonus.

[–] TrinityTek 1 points 1 year ago

Thanks for the perspective! I am a reluctant newcomer to Docker so I appreciate it. Time for me to get with the times and embrace Docker since that's the most popular installation method for many of my favorite self hosted platforms these days. It might take a while for me to really get used to it though. Since I have this setup and working it will probably remain as is, but I'll make a point to do a pure Docker setup on a similar build in the future.