Selfhosted

43108 readers

825 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Any nice playbook or tutorial to host a static website from home? (mander.xyz)

submitted 5 days ago by tomandjerryco@mander.xyz to c/selfhosted@lemmy.world

18 comments fedilink hide all child comments

I wanted to know if there was a neat playbook or tutorial set that one can refer to if they're trying to set up their own static website from home?

So far I have done the following:

Got a raspberypi (Raspberry Pi 2 Zero W) and raspberrypi OS installed with fail2ban ready.
Installed nginx (I have not configured anything there).
Written the HTML and CSS files for the website.
Purchased a domain.

How do I complete the remain pieces of this puzzle?

My purpose: I want an online profile that I can share with my colleagues and clients instead of relying on LinkedIn as a way to connect. Eventually, I will stop posting on LinkedIn and make this my main method of relaying information and disseminating my works and services.

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

[–] traches@sh.itjust.works 15 points 5 days ago* (last edited 5 days ago) (1 children)

The trickier part here his connecting your domain to your raspberry pi and allowing the big internet to access it. You have a few options:

Set up dynamic DNS to direct your domain name to your (presumably dynamic) home IP address. Assign the rpi a static IP address on your home network. Forward ports 80 and 443 to that address. The world knows your home IP address, and you're dependent on your router for security. No spam or DDOS protection.
Use a service such as cloudflare tunnel. You're dependent on cloudflare or whoever, but it's an easier config, you don't need to open ports in your firewall, and your home IP address is not public. (I recommend this option.)

Either way, don't forget to set up HTTPS. If you aren't dead-set on using nginx, caddyserver does this entirely automatically.

[–] activ8r@sh.itjust.works 3 points 4 days ago

To add on, if you are set on using nginx then it's easy to set up https with certbot