Selfhosted

60526 readers

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

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

My notes on running containerized web services on a home server (avikdas.com)

submitted 2 years ago by akdas@lemmy.world to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

I set up a new home server recently using containerized services, and I wanted to share what I learned. Nothing here is revolutionary, but this is the type of resource I wish I had when I started.

I'm open to feedback on what I could have done better!

you are viewing a single comment's thread
view the rest of the comments

[–] skilltheamps@feddit.de 1 points 2 years ago (1 children)

I only keep track of the sha256, compose happily uses those. I published the tool https://feddit.de/post/2909288 :)

[–] NewDataEngineer@lemmy.world 1 points 2 years ago

Ah ok. I thought you meant the numbered version. I'm doing the same with sha256 too.