Selfhosted
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!
view the rest of the comments
Is there a way to specify latest in the yml file or should I manually enter the latest version?
Edit: don't foolishly try asking questions from your Lemmy instance after running docker-compose down...
Yes there is. To do so look for the line with
image:
statement and do something likeimage: dessalines/lemmy-ui:latest
Try this. You may not even have to do that. First try the plain old docker-compose pull. Since now enough time has elapsed, I am guessing that it should pull the latest image without having to edit the docker-compose.yml file.Last silly question, what's the easiest way to verify my version post-upgrade?
The only unasked question is the silly one. If you scroll down to the bottom of your Lemmy instance in the web browser, you should see the current one you're on. It should like something like this: