Will self-hosting Lenny have the limitation that you’ll be missing a lot of comments when subscribing to magazines from other instances? I am considering it tough
this post was submitted on 22 Jun 2023
1 points (100.0% liked)
Selfhosted
40113 readers
838 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
You are using two technologies that have a bad of working like shit, together; Ubuntu/snap and docker. You can try podman if you want, or a different distro. Or, at least, install the official docker way.
I've been trying for more than a week. LemmyEasyDeploy worked. But now i'm stuck with ssl certificate.
Lemmy Easy Deploy handles the SSL certificates for you. You don't need to buy them
I get ssl errors when i try to access the site.
Maybe start from scratch? Maybe you could ask the developer. I bought SSL tickets but ended up not needing them
I've started from scratch several times. Never get further than the build command. :) But i will try again later today.
If your using docker I recommend getting a docker-compose file that does 98% of the config work for you. Pretty sure there's one in the install docs.
I've been having trouble understanding how the docker-compose thing works, and the whole... impermanence of docker containers. Got any tutorials you'd recommend? Note I'm on Windows.
Are you planning to host it on a Windows machine?
If you don't have experience with docker, don't jump straight to docker compose. Start simpler.
If you want to have data persist after a container is killed, have a look at the -v option of "docker run". It allows you to mount a volume.