Self Hosted - Self-hosting your services.

11503 readers

1 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.

Cross-posting

[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed if topic has to do with selfhosting.
[email protected] is allowed!

If you see a rule-breaker please DM the mods!

founded 3 years ago

MODERATORS

[email protected]

[Project] Having trouble deploying Lemmy? Try my new script! Get up and running in minutes! (github.com)

submitted 1 year ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

In the past few days, I've seen a number of people having trouble getting Lemmy set up on their own servers. That motivated me to create Lemmy-Easy-Deploy, a dead-simple solution to deploying Lemmy using Docker Compose under the hood.

To accommodate people new to Docker or self hosting, I've made it as simple as I possibly could. Edit the config file to specify your domain, then run the script. That's it! No manual configuration is needed. Your self hosted Lemmy instance will be up and running in about a minute or less. Everything is taken care of for you. Random passwords are created for Lemmy's microservices, and HTTPS is handled automatically by Caddy.

Updates are automatic too! Run the script again to detect and deploy updates to Lemmy automatically.

If you are an advanced user, plenty of config options are available. You can set this to compile Lemmy from source if you want, which is useful for trying out Release Candidate versions. You can also specify a Cloudflare API token, and if you do, HTTPS certificates will use the DNS challenge instead. This is helpful for Cloudflare proxy users, who can have issues with HTTPS certificates sometimes.

Try it out and let me know what you think!

https://github.com/ubergeek77/Lemmy-Easy-Deploy

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

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

I tried to run your script on a proxmox Debian 12 lxc but i hit a few issues.. i already run a reverse proxy etc..

So.. what VPS would you recommend to run this on ? It will literally only be for myself to maintain my subscriptions and have a singular account...

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Unfortunately, Lemmy Easy Deploy isn't well suited for running behind a reverse proxy. It is a complete "do everything for me," and I don't have a good way to support people running a webserver already. I've pushed an update a few minutes ago, so you can try playing with the ports and maybe turning off Caddy's TLS (so that certificates are managed by your webserver instead of the one in LED), but I'm sorry to say you're on your own in that case :(

Lemmy can basically run on a potato. Any VPS will do, but the main metric you'll want to keep track of is disk space. Any $5/month instance will be fine.

I am a moderate-to-heavy user of Lemmy, and I go through about 700MB of new data per day. If you federate with less communities than me, this may be less for you. At my current rate of storage, I can go for about a month and a half before I have to worry about storage space.

After that, I'm thinking about clearing my thumbnail cache, and seeing if Lemmy has some way to prune old data. I haven't been using Lemmy long enough to know what to do to clean things up, but if I figure out something clever in a month or two, I'll share what I learn.

EDIT: Turns out ~90% of my Lemmy data is just for debugging and not needed:

https://github.com/LemmyNet/lemmy/issues/3103#issuecomment-1631643416

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

I unretired an old racknerd vps and got it running on there.. works great!

Just need to now figure out how to move it to something that can actually cope with it lol..

Any ideas how to backup an instance and move it?

[–] [email protected] 1 points 1 year ago

Yes, you will want to copy the entirety of the Lemmy-Easy-Deploy folder recursively, including the live folder.

However, all important data is also stored in Docker volumes on the system. There isn't a great way to migrate Docker volumes between systems, but there are a few options. One I have not personally used, but seems to look good, is vackup:

https://github.com/BretFisher/docker-vackup

You'll want to run docker volume ls on your current system, and make sure that when you migrate them to the new system, all the volume names are exactly the same. Then, if you run deploy.sh -f, it should pick everything up and deploy.

Do note: if Docker Compose itself does not create the volume with the right tags, it will still work, but it will print some warnings to the console. Here is an issue discussing it and some potential hacks you can use to add the right tags:

https://github.com/docker/compose/issues/10087

Finally, if you need to re-create a volume on the new system with tags like the above issue mentions, you can try migrating data over between named volumes on the same system using this helpful oneliner (don't forget to change the volume names in all the places in this command):

https://www.commands.dev/workflows/rename_docker_volume

In short, it's a bit hacky, but it can be done.

Good luck!