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:

  1. Got a raspberypi (Raspberry Pi 2 Zero W) and raspberrypi OS installed with fail2ban ready.
  2. Installed nginx (I have not configured anything there).
  3. Written the HTML and CSS files for the website.
  4. 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.

  • starshipwinepineapple@programming.devEnglish
    4·
    7 hours ago

    This is something that doesn’t really need to be self hosted unless you’re wanting the experience. You just need:

    1. Static website builder. I use hugo but there’s a few others like jekyll, astro
    2. Use a git forge (github, gitlab, codeberg).
    3. Use your forges Pages feature, there’s also cloudflare pages. Stay away from netlify imo. Each of these you can set up to use your own domain

    So for my website i just write new content, push to my forge, and then a pipeline builds and releases the update on my website.

    Where self hosting comes into play is that it could make some things with static websites easier, like some comment systems, contact forms, etc. But you can still do all of this without self hosting. Comments can be handled through git issues (utteranc.es) and for a contact form i use ‘hero tofu’ free tier. In the end i don’t have to worry about opening access to my ports and can still have a static website with a contact form. All for free outside of cost of domain.

    • sugar_in_your_tea@sh.itjust.worksEnglish
      1·
      6 hours ago

      But if you want to self host, you just need a webserver to serve static files. If you already have other stuff hosted, you probably already have one, so just point it to your HTML files (and potentially generate them with a tool).