Selfhosted

38832 readers

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

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

140

If you had to redo your self hosting setup, what would you do differently this time around? (lemmy.world)

submitted 1 year ago by hogofwar@lemmy.world to c/selfhosted@lemmy.world

103 comments fedilink hide all child comments

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

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

I’d encrypt all disks. Nevertheless, it covers my ass when they retire the server after I used it.

Good point. How do you unlock the disk at boot time? dropbear-initramfs and enter the passphrase manually every time it boots? Unencrypted /boot/ and store the decryption key in plaintext there?

[–] wgs@lemmy.sdf.org 2 points 1 year ago

I run openbsd on all my servers so I would be entering the passphrase manually at boot time. Saving the key on unencrypted /boot is basically locking your door and leaving the key on it :)