Selfhosted

40347 readers

305 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

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

submitted 1 month ago* (last edited 1 month 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

[–] something_random_tho@lemmy.world 18 points 1 month ago* (last edited 1 month ago) (1 children)

Hi friend, this was just meant to be an introduction, as I get started blogging and sharing back some knowledge and lessons I learned along the way. I've never written a blog before (or much of anything!), and I'm sorry you didn't find value in this.

I wasn't intending to boast, but I can see how it came across. I just meant to say, "companies are trying to tell you that you need 'XYZ' to scale," and at least at the size of business I ran, you didn't need any fancy tech at all -- we could have made do with a dead-simple setup: a single server running Go and SQLite. It's something I wish I had known when I started.

I'll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.

[–] just_another_person@lemmy.world 15 points 1 month 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 1 month 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.