Selfhosted

61647 readers

264 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. Tags [CBH] or [AIP] are required, see the links in Rule 8 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, and find example disclosures here.

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

You're overcomplicating production (paravoce.bearblog.dev)

submitted 2 years ago* (last edited 2 years ago) by something_random_tho@lemmy.world to c/selfhosted@lemmy.world

16 comments fedilink hide all child comments

cross-posted from: https://lemmy.world/post/21023181

Sharing some lessons I learned from 10 years/millions of users in production. I’ll be in the comments if anyone has any questions!

I hope this series will be useful to the self-hosted and small web crowds—tips for tools to pick and the basics of server management.

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

[–] just_another_person@lemmy.world 15 points 2 years ago (1 children)

Well, apologies for being bluntly critical. I can offer a few constructive tips to help with writing about technical topics:

Try starting with a simple topic flow: topic -> synopsis/purpose of why you're writing -> background -> observations -> point<>counterpoint loop to elaborate on purpose -> closing
Stay away from asserting your point in the title unless you're showing definitive proof of something
Find ways to speak to who may find your writing useful towards the beginning. "If you have a similar problem like X...", "People who use X may find...", or "Anyone having similar X experience may find...". Something like that.

[–] 1984@lemmy.today 15 points 2 years ago (1 children)

I can offer some constructive tips to you as well: dont speak for all of us.

I liked the article. I didn't interpret it as "everyone must do what I say". It was simply a viewpoint from a person on the internet. That is what a blog is.

The complexity of tech stacks have increased enormously in the last 10 years, and it's only sane to see what tradeoffs we are making to be able to scale easily. Perhaps it's not worth the trouble for 90% of us. If we follow best practice from cloud providers without thinking for ourselves, we will not learn to think for ourselves either.

So let's do that. Let's think, wrote blogs, discuss, and allow for discussions. Don't shut people down.