This is an old revision of the document!
Table of Contents
So you want to host a website. On the web!
You have a few questions that need to be answered:
- what domain do you want it to be accessed on
- how do you want it to be deployed. static html? pre-rendered? a dynamic server-side application?
- what auxiliary features do you want to pull in?
What domain do you want
We have so many domains. a lot of them can be found on the core-infra dns list https://git.devhack.net/devhack/tf-external-dns/ and a few more can be found on our own powerdns server http://pdns.devhack.internal/dashboard/
because of how web proxy forwarding works, you need to configure the DNS to point to one of our existing web forward proxies (probably) and then configure the proxy to point to the final location of your website.
How are we deploying this site?
static html
if you're merely deploying static html, chucking it in a git repo with something to get it working with git-pages or our nix mothership deployment scheme would be the best way to go about it. or if you're fine with a tilde dir, throwing your files on aleph works great and has the added benefit of gopher and gemini hosting, too!
pre-rendered
If you want to pre-render with some sort of templating system like hugo, deploying to our git with runners running the pre-render and then leaning on git-pages is definitely the way to go
server side app
If you need to do complicated things with your webapp, you're going to need to run code consistently somewhere. Now you need to figure out how you want to go about that
proxmox
docker
kubernetes
auxillary features
- single sign on
- metrics