#Hosting this documentation
#Why not https://doc.nip.io
nip.io is a wildcard DNS service: a name resolves only if it contains an IP address (doc.23-172-120-79.nip.io → 23.172.120.79). The bare name doc.nip.io has no DNS record (checked: no answer). It can't point to any of our servers, so a certificate for it can't be issued either. Nothing on our side can change that, because we don't control the nip.io domain.
#Where it runs now
https://doc.23-172-120-79.nip.io: Apache virtual host on Bhavik's test server 23.172.120.79 (the same box that serves the OSS bug list), Let's Encrypt certificate, static files only.
| Item | Value |
|---|---|
| Files | /var/www/v8docs (static HTML/CSS/JS, no server code) |
| Vhost | /etc/apache2/sites-available/v8docs.conf (+ -le-ssl.conf from certbot) |
| Source | refs/v8-docs/ in the central-app-2 workspace: content/*.md, nav.json, build.mjs, assets/ |
| Build | node build.mjs → dist/ (uses the marked already on the machine, no new packages) |
| Deploy | copy dist/ to /var/www/v8docs |
#Options for a permanent address
| Option | What's needed |
|---|---|
Keep doc.<ip>.nip.io | Nothing more. Works now, but the IP is in the name |
A real domain, e.g. docs.central.serveravatar.com | A DNS A record → the hosting server's IP, then certbot --apache -d <name> (or the nginx equivalent). The site is static and can be moved as-is |
On this VPS (167.233.229.184) as doc.167-233-229-184.nip.io | An nginx server block + certificate on the agents' VPS. That's server infrastructure, so the operator (Adarsh) has to do it, not this agent |
Inside the Next.js app (/docs) | Possible later, but the spec would then ship with product code. Not recommended during the documentation phase |