Selfhosted

40201 readers

920 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

226

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

submitted 1 year ago* (last edited 1 year ago) by ubergeek77@lemmy.ubergeek77.chat to c/selfhosted@lemmy.world

128 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

[–] ubergeek77@lemmy.ubergeek77.chat 0 points 1 year ago* (last edited 1 year ago) (4 children)

Ok nevermind to everything I just said before this edit.

Go into your instance settings and upload an icon. A favicon will be made for it automatically.

[–] Linuturk@lemmy.onitato.com 0 points 1 year ago (3 children)

Quick update, it seems the favicon works in Chrome but not Firefox.

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

I use my own deployment and I've never had an issue with my favicon on Firefox, on both desktop and mobile. Maybe it's a weird browser caching thing?

[–] Linuturk@lemmy.onitato.com 0 points 1 year ago (1 children)

Do you see a favicon at lemmy.onitato.com ?

[–] ubergeek77@lemmy.ubergeek77.chat 1 points 1 year ago

No, but I can see in your HTML the favicon is being server side rendered. It's probably not working on Firefox because the icon is very large. Here is the URL it uses:

https://lemmy.onitato.com/pictrs/image/1ffe4c8b-3751-4ebb-aa17-ff0e21a0468b.png

Try scaling it down and uploading it again? If it's small enough it should work immediately. I wouldn't know how large, though. My icon is pretty tiny.