this post was submitted on 29 Dec 2023
111 points (96.6% liked)

Selfhosted

40296 readers
265 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I work in tech and am constantly finding solutions to problems, often on other people's tech blogs, that I think "I should write that down somewhere" and, well, I want to actually start doing that, but I don't want to pay someone else to host it.

I have a Synology NAS, a sweet domain name, and familiarity with both Docker and Cloudflare tunnels. Would I be opening myself up to a world of hurt if I hosted a publicly available website on my NAS using [insert simple blogging platform], in a Docker container and behind some sort of Cloudflare protection?

In theory that's enough levels of protection and isolation but I don't know enough about it to not be paranoid about everything getting popped and providing access to the wider NAS as a whole.

Update: Thanks for the replies, everyone, they've been really helpful and somewhat reassuring. I think I'm going to have a look at Github and Cloudflare's pages as my first port of call for my needs.

you are viewing a single comment's thread
view the rest of the comments
[–] jgkawell@lemmy.world 58 points 10 months ago* (last edited 10 months ago) (1 children)

I'll let folks with more security experience dive into your specific question, but another option is to host your website on something like Github pages (using a static website generator like Jekyll) and point Cloudflare at it. That way you don't need anything pointed at your local network, get the uptime of Github, and still benefit from your own domain name.

That's what I'm doing with my own blog and it's been great. Github provides the service for free but if they ever charge for it I'll just start hosting it locally.

[–] TedZanzibar 16 points 10 months ago (4 children)

OK that's genius, I will definitely look into that!

[–] 7Sea_Sailor@lemmy.dbzer0.com 29 points 10 months ago (1 children)

Or take github out of the equation and directly use cloudflare pages. It has its own pros and cons, but for a simple static blog it'll be more than enough, and takes out the CNAME hassle.

[–] DetachablePianist@lemmy.ml 2 points 10 months ago

Came here to say this^

[–] jgkawell@lemmy.world 4 points 10 months ago

If you have any issues or questions feel free to DM me here. I'd be happy to help out :)

[–] ducking_donuts@lemm.ee 2 points 10 months ago (1 children)

Speaking of Cloudflare, if you’re okay with not self hosting, then there’s Cloudflare Pages which is good for hosting static websites.

[–] CraigeryTheKid@lemm.ee 1 points 10 months ago

That's what I'm doing! I used it to make a "blog" of all the things I had to learn to switch to Linux for my home drives and daily gaming rig. Complete with copy buttons on the code blocks so I can do a complete reformat in minutes!

[–] AbsorbsQuickly@lemmy.world 1 points 10 months ago

I do this via AWS amplify and it costs me a few cents a month as another option.