11–20 of 40 posts
How: github pages. How, you ask? I don’t know. I set it up once, and now when I log in to github it tells me I set it up wrong and I should set it up again correct. I don’t know what I did or how to do it correctly - but visiting my domain works, so I don’t dare to fix what isn’t really broken.
So I guess you don’t need to know what you’re doing to host a static site on your own domain :)
That’s a great question! How: github pages. How, you ask? I don’t know. I set it up once, and now when I log in to github it tells me I set it up wrong and I should set it up again correct. I don’t know what I did or how to do it correctly - but visiting my domain works, so I don’t dare to fix what isn’t really broken. So I guess you don’t need to know what you’re doing to host a static site on your own domain :)
Short is create a CNAME file in your site repo with your custom DNS in it, then add a CNAME in your DNS pointing to the GitHub pages DNS.
Version control: GitHub
Editing: Netlify CMS or nano+git
I started setting this up from scratch using Gatsby, but then realized it would be much better and also easier to use this starter:
https://www.gatsbyjs.org/starters/alxshelepenok/gatsby-start...
It is as easy to set this up, as it is to install LAMP+WordPress on a VPS.
I don't have much traffic; the blog and email/etc runs less than $10/mo.
It's possible to lease a bare IP range and set up your own DNS servers, etc. For small amounts of traffic theres no reason you couldn't use a RasPi to serve a blog that way. There's also drawbacks and headaches that make renting someone else's stuff attractive.
1. Namecheap DNS registration.
2. Server is an old PC in my basement.
3. Dynamic DNS client running on my OpenWRT router.
4. Code is a homemade blog system. Linux, Java (Servlets + JSP + EJB), Payara, PostgreSQL.
5. Uses a Let's Encrypt certificate.
It's totally old school, but fun to play with, and it serves pages fast.
I run a Ghost installation on a Debian VM, reverse proxied through Nginx and set up with Let's Encrypt.
Ansible is used to build and maintain both servers, and the actual web content is in Git.
I use `receive.denyCurrentBranch=updateInstead` in the repo config on the servers, so I just do a push to each and the new content goes live instantly.
The reason for doing it this way is that I want to fully own my platform. I have fine-grain control over all of the web server headers, PHP configuration, etc.
Generated by Hugo, hosted on smallest AWS LightSail, own domain. Uses nginx, Lets Encrypt, FBSD. Auto-updates everything and if something breaks it breaks. 1000 days and zero maintenance. https://blog.eutopian.io/the-stack/
This way you don't have to risk it may break and if it is a low traffic site it might be cheaper.