3 ms·
Just to expand on why you should use .test for this, it's a reserved TLD according to RFC 2606 [0] and should therefore be guaranteed never to be issued by any
by chatmasta 4y ago
Just to expand on why you should use .test for this, it's a reserved TLD according to RFC 2606 [0] and should therefore be guaranteed never to be issued by any registrar. Alternatively, you could use any of the other 11 reserved TLDs: .测试, .परीक्षा, .испытание, .테스트, .טעסט, .測試, .آزمایشی, .பரிட்சை, .δοκιμή, .إختبار, .テスト
e.g. we use `https://www.splitgraph.test https://www.splitgraph.test` for local development, which is nice because we avoid a whole class of "works in dev" bugs that you get with `http://localhost:3001 http://localhost:3001`
For the certificate, we use a self-signed certificate signed by a root cert generated by mkcert [1] locally on each developer's machine (to avoid sharing a root cert that could be used to MITM each other).
[0] https://en.wikipedia.org/wiki/.test https://en.wikipedia.org/wiki/.test
[1] https://github.com/FiloSottile/mkcert https://github.com/FiloSottile/mkcert
- RulerOf 4y agoI created a subdomain like local.example.com and pointed it at 127.0.0.1 in the DNS. I wanted to suggest using a .test domain but managing the hosts file is always really clunky, even with a slick tool like hostess[1]. 1: https://github.com/cbednarski/hostess https://github.com/cbednarski/hostess