how_to_host_a_website
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| how_to_host_a_website [2026/10/15 03:46] – m | how_to_host_a_website [2026/10/15 03:51] (current) – m | ||
|---|---|---|---|
| Line 12: | Line 12: | ||
| We have so many domains. a lot of them can be found on the core-infra dns list https:// | We have so many domains. a lot of them can be found on the core-infra dns list https:// | ||
| - | because of how web proxy forwarding works, you need to configure the DNS to point to one of our [existing web forward proxies](:web_forward_proxies) (probably) and then configure the proxy to point to the final location of your website. | + | because of how web proxy forwarding works, you need to configure the DNS to point to one of our [existing web forward proxies](:web-forward-proxies) (probably) and then configure the proxy to point to the final location of your website. |
| ## How are we deploying this site? | ## How are we deploying this site? | ||
| Line 18: | Line 18: | ||
| ### static html | ### 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](: | + | 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](: |
| ### pre-rendered | ### pre-rendered | ||
| Line 29: | Line 29: | ||
| #### proxmox | #### proxmox | ||
| + | |||
| + | https:// | ||
| #### docker | #### docker | ||
| + | |||
| + | https:// | ||
| #### kubernetes | #### kubernetes | ||
how_to_host_a_website.1792061214.txt.gz · Last modified: by m
