this post was submitted on 18 Jun 2023
210 points (97.7% liked)

Selfhosted

40345 readers
626 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
 

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

(page 2) 50 comments
sorted by: hot top controversial new old
[–] orca@orcas.enjoying.yachts 1 points 1 year ago* (last edited 1 year ago)

This was the only tool that I was able to get running. I recommend it to anyone curious about running their own instance. I tried both the official Ansible and Docker instructions, and neither worked.

[–] SonyJunkie@lemmy.world 1 points 1 year ago (4 children)

Hi @ubergeek77@lemmy.ubergeek77.chat

I must be doing something wrong here because unlike many others I can't seem to get this working! Please can you offer some advice?

I have amended the config.env file to change the HOSTNAME, SITE NAME and ADMIN USER but left everything else the same.

I then ran ./deploy.sh and everything seems to have worked because it presented me with the admin login credentials and basic instructions to shutdown and start the instance. I tried simply typing the IP address of the docker container in to a browser but that didn't work and TBH I didn't expect it to. I then typed the URL into the browser and I'm getting a "ERR_TOO_MANY_REDIRECTS" error message. I read through the trouble shooting on your Github but the only reference to too many redirects mentions a Cloudflare API token, I'm not using Cloudflare nut I am using nginx proxy manager to point my URL to the docker container.

I hope some of this makes sense.

load more comments (4 replies)
[–] Linuturk@lemmy.onitato.com 1 points 1 year ago

Any tips on how to customize the favicon for my instance? Using the docker-compose method.

[–] BlueEther@no.lastname.nz 1 points 1 year ago* (last edited 1 year ago) (6 children)

Threw an error:

Creating lemmy-easy-deploy_pictrs_1 ... 
Creating lemmy-easy-deploy_postgres_1 ... error

ERROR: for lemmy-easy-deploy_postgres_1  Cannot start service postgres: failed to create task for container: failed to create shim task: OCI runtime create failed: runc cr
Creating lemmy-easy-deploy_pictrs_1   ... error: permission denied: unknown
load more comments (6 replies)
[–] Declared0978@lemmy.world 1 points 1 year ago (2 children)

So stupid question - how do you shut them down? Docker compose down or stop don't seem to work.

Also, as an intermediate (spoiled Unraid) user, if I'm behind nginx proxy manager with custom ports do I just change 80 and 443 in the lemmy docker-compose? I'm doing this in a Debian VM.

load more comments (2 replies)
[–] Kir@feddit.it 1 points 1 year ago

You are helping the whole community! Thank you, I will give a try to it, since I'm quite new in self-hosted platform!

[–] Stijn@lemmy.antemeridiem.xyz 1 points 1 year ago (1 children)

Will try this tomorrow. Tried them all. Nothing seems to work! I have been at it the whole week trying.

load more comments (1 replies)
[–] mfn@mfn.pub 1 points 1 year ago

After trying to do it with docker or ansible manually for hours and failing, this was soo helpful. So thank you.

[–] marketingpro123@kbin.social 1 points 1 year ago

Exploring Go High Level:

What’s the Enthusiasm About?
Hello there! Are you familiar with Go High Level? If not, let's break it down. Imagine managing multiple apps for marketing. Sounds busy. That's where Go High Level comes in. It's like that friend who has a solution for everything. Whether you are working on creating an outstanding sales funnel or sending out an email campaign, this platform has your back. The best part? They let you test drive everything with a 14-day free trial. It's like trying out a new car but for your business. And if you ever need assistance, their support team is just a click away. Pretty exciting, huh?

So, How Much Does It Cost?
Alright, let's talk about the financial side. Go High Level offers 3 main plans. The Agency Starter Plan is perfect if you're just starting or have a small business. It's loaded with all the essential tools, and it's quite cost-effective. But if you're looking to scale up, the Agency Unlimited Plan is your best choice. It's like the VIP pass at a concert, giving you access to everything without any limitations. Not sure about committing? Remember that 14-day free trial I mentioned? It's a great way to give it a try without any obligations. Lastly, they offer a Pro plan that includes "SaaS mode," where you can white label the product under your brand. Fantastic!

Why Everyone's Raving About It:
In a world full of sophisticated digital tools, Go High Level is like that all-in-one Swiss Army knife. There's no need to switch between apps because it has everything under one roof. Whether you're a newcomer or an experienced marketer, it's super user-friendly. It's not just about launching impressive campaigns; they ensure you understand their performance with top-notch analytics. There's even a white-label feature for marketing agencies, so you can add your brand and impress your clients.

Here is a link to their 14-day free trial:
https://www.gohighlevel.com/?fp_ref=get-started-now.

[–] moons1de@lemmy.moonside.cc 1 points 1 year ago

Marius Hosting published a good guide this week that I used on my nas without an issue (via docker compose).

[–] HorseFD@lemmy.world 1 points 1 year ago (2 children)

Is this easier than the Ansible deployment? That was very straight forward if you’re running a system with apt.

load more comments (2 replies)
[–] SurvivaLlama@lemmy.world 1 points 1 year ago (1 children)

Way cool. Can you provide something for unRaid?

Sorry, I don't have access to an unRaid system to test it with.

However, I know most NAS systems at least support CLI-style Docker and Docker Compose, so if you can manage to get Docker running, it might work? The script has some Docker detection if you're not sure.

However, I know Synology hogs use of port 80 and 443. I'm not sure if unRaid is the same way. If it is, this might not be the best solution for you. But, if you want to give it a shot, I do have some advanced options in my config that lets you change to different ports and turn off HTTPS (so you can run a proxy in front of it). I can't really help people who run it behind a webserver like this, but the template files in my repo can be freely modified, so you're welcome to hack at my script any way you like to get it working!

[–] rglullis@communick.news 1 points 1 year ago

A bit OT, but worth the shot: can anyone confirm whether instances deployed with this script can be found on Mastodon?

I have tried both the ansible script provided by the developers and I've adapted the docker-compose files to get things running on Docker Swarm. Everything seems to be working well, object storage, federation... except that I can not find any user or community from my instance if I search from Mastodon.

[–] ChaosAD@lemmy.world 1 points 1 year ago (1 children)

What adjustments I need to do to run this locally (in my LAN) just for testing?

[–] ubergeek77@lemmy.ubergeek77.chat 1 points 1 year ago (7 children)

I haven't tested a local only use case, but you can probably set these options in config.env

  • Set LEMMY_HOSTNAME to localhost
  • Set CADDY_DISABLE_TLS to true
  • Set TLS_ENABLED to false

This will disable any HTTPS certificate generation and only run Lemmy on port 80. I don't know if Caddy or Lemmy will act weird if the hostname is localhost, but this should work for you. Let me know if it doesn't.

load more comments (7 replies)
[–] sideone@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (3 children)

Hey @ubergeek77@lemmy.ubergeek77.chat, I'm trying this on an Aarm64 instance and the script says it only works on v0.17.4. Is there a plan to update to 0.18?

EDIT: the script fails for 0.17.4 here:

=> ERROR [lemmy builder 6/7] RUN cargo build --release 1183.5s

Build timer continues but CPU usage drops off. Any ideas where I've gone wrong?

load more comments (3 replies)
[–] Illecors@lemmy.cafe 0 points 1 year ago

I appreciate the effort, but for software as experimental as Lemmy I would argue making things 1-click "simple" will inevitably lead to people breaking their instances in the future, when some migration will be required.

I would strongly suggest people figure things on their own.

load more comments
view more: ‹ prev next ›