Self Hosted - Self-hosting your services.

11503 readers

2 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)

Unfortunately, there is not a lot of information to go off of here. I was able to upgrade to 0.18.4 with no hitches, and I haven't seen similar reports of this.

Are you using any custom configs? Do the logs for just the Lemmy service show you anything of note?

docker compose -p lemmy-easy-deploy logs lemmy

In the past, Lemmy itself has had some strange edge cases causing crashes, such as an improper audit log value causing the entire audit log to fail. It's possible this is a similar case, in which case you may need to file a bug on Lemmy's tracker.

You are welcome to file an issue with some more information and logs, but if this is an issue caused by a bug in Lemmy, unfortunately I won't be able to fix it.

If you're still having issues, feel free to give me some more info on my tracker and I can take a look:

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

[–] carrmcg 1 points 1 year ago

Thanks for the response! I probably won’t be able to look at this again until the weekend. That’s good to hear that you’ve had 0.18.4 working. I’ve been testing this out on Ubuntu server 22.04 in a Windows Hyper-V VM.

I’ll gather what I can and get back to you. Thanks again.