Is there a good alternative to github pages? I need just a static website up.
- I have a domain.
- I have my site (local machine)
- And that’s all I have.
- I have a machine that could be running 24/7 too.
You must log in or # to comment.
Codeberg pages
If it’s purely static without the need to generate generate easily new page, simply use a web server.
You need to qualify this statement, GotHib Pages can mean like two or maybe more things. Do you mean free static site hosting? Do you mean easy static site generation from Markdown files?
Edit: GotHib 😭 what a typo
Hi, I have means to generate the html/css/js myself. I am indeed, serving them in my LAN (
python -m http.server)I need help learning how to make it accessible from the web.
I don’t mind hosting somewhere else, but I really wouldn’t like my work being an easy snack for some AI. That’s why I’m not inclined to use GotHib 😁
So long as your content is FLOSS, Codeberg Pages is a good choice perhaps. https://docs.codeberg.org/codeberg-pages/
Sorry to say, but if you put it on the internet the AI bots are going to gobble it down.
Only way to protect it is to not put it on the public net. If you add a challenge (login or something) it might stay unmolested, but that’s no longer a static site.
I recently used Jekyll (https://jekyllrb.com/) as a static site generator. I found it easy to use. I personally used Gitlab pages, because I didn’t feel confident hosting on my home internet (didn’t want to inadvertently cause issues for my housemates when I’m still learning this stuff).
The nice thing about static sites is that it’s pretty easy to find free or extremely cheap hosting for them.
If you don’t care about uptime, self host it on the local machine you have and expose it through free cloudflare tunnels.
Your DNS provider may offer static hosting as a paid service. I’m using porkbun and their static hosting is pretty cheap, plus they handle SSL and whatnot for me.
I use nginx you can have configs for different sites and have the server_name have the domain for each server block (I use a file per site) and you can either do static via a root folder, or proxy_pass for active running servers, and nginx will map the domains to the server blocks you should also have a default, and you can then have multiple domains point to the same ip address, but keep in mind that home internet often has a dynamic ip, so you may need to update it every so often. There is a service to help with the dynamic ip I think noip.com has a solution available, but feel free to look around.
- Any of https://staticsitegenerators.bevry.me/
- Any webserver + virtualhost config that serves plain HTML pages
- a build/upload script
GitLab has their own version of Pages
Ok, so I must’ve misunderstood the question, because to me it seems OP already has all the necessary ingredients to bake this dish. And yet, the vast majority of comments recommend various 3rd party services which is the complete opposite of selhosting.
Fire up nginx/apache2, and all good, no? What am I missing?Hi, thanks for the comment. I have the page. But I don’t know how to make the page accessible from the web.
I have a router at home that my ISP provided (I cannot even login to it) which provides WiFi and have a couple of Ethernet ports.
I don’t know if it is possible to make my page available to the world from behind this soho
Are you able to ask your ISP customer service to set up port forwarding for you?
At minimal you want HTTP (Port 80) but you probably want HTTPS (443) as well. If you’re hosting DNS as well you will need port 53 too.
Have those ports routed to the “inside” IP of the machine you want to use, and the rest of it is basically just setting up the webserver (and possibly DNS) to serve your domain.
NB: While on the phone with your ISP, ask them what the DHCP lease time is. Ideally you want a static IP for your setup.
I honestly wouldn’t recommend it if you don’t have a minimum of security knowledge. The moment your home server pops up with a domain name it will get scanned by shady actors and possibly exploited.
A reverse proxy from somewhere like Cloudflare would allow you to host without any router config. Plus, it’d give a little more protection against bots, but it’s not going to block 100% of them.
I think the missing piece is the website itself? The static HTML page generator?
Something like Hugo
I was confused when I read it as well, at least I know now that I wasn’t alone. I think the next step is just opening a text editor and starting with <html></html> Forward a couple ports, maybe use caddy to route the port internally but it isn’t needed. Although if you use NOIP with Caddy getting the https cert setup seems to be pretty easy.
There’s actually a surprising amount of free static website hosting out there. Besides GitHub, GitLab, Cloudflare, and Netlify come to mind offhand.
Codeberg does too
Codeberg is not just for static websites. It’s for FOSS projects. Their FAQ addresses this.
Codeberg Pages. Neocities.
deleted by creator
HTTP 1.1 is more than good enough for serving a static website.
deleted by creator
There is zero question about it. It will be absolutely fine for some dude’s static website over a residential internet connection.
deleted by creator
Same? HTTP/1.1 ran the entire internet for 20 years and is used by a ton of sites. It’s fine for a personal website.
Although I agree with the implied sentiment that “the Perfect is the enemy of the Good Enough” (especially for low-profile personal web-presence) and that naval-gazing about protocols can become a counterproductive rabbit-hole, sometimes it can also be risky to oversimplify in the other direction without at least parenthesizing the caveats too. For example this “HTTP/1.1 must die” site points out how desync attacks make HTTP/1.1 robustness a bit of a game of Whack-a-Mole. For certain sites (even some personal sites) this can occasionally matter.
Obviously someone who has never actually tested 1.1 vs 2 vs 3 lmao
deleted by creator
