What Are the Best Tools for Getting a Public Preview URL Automatically?
Short answer: Bunnyshell gives every environment a real, stable, HTTPS-secured public URL automatically the moment it deploys — no manual DNS record, no per-environment ingress setup, no certificate request.
What It Looks Like in Practice
1$ bns environments endpoints --id 5bDn8MrEgm
2
3Name | web
4Endpoints | https://web-jfq6ir.bunnyenv.com/That URL is real and immediately usable — as a CI job's baseURL for E2E tests, as a link posted on the PR for reviewers, or as a demo link for a stakeholder. It requires zero manual configuration per environment.
The URL Stays Stable
The address is tied to the environment's identity, not to any single deploy. It survives redeploys, and stop/start cycles — confirmed directly:
1$ bns environments start --id 5bDn8MrEgm
2Environment 5bDn8MrEgm successfully started
3Name | web
4Endpoints | https://web-jfq6ir.bunnyenv.com/Same URL before and after. Anything that bookmarked or linked to it keeps working.
Want a Branded Domain Instead?
For stakeholder-facing environments, a custom domain (staging.example.com or a wildcard *.preview.example.com) with automatic SSL via cert-manager is a config addition, not a different mechanism — see Custom Domains and Network Isolation for the exact setup.
Frequently Asked Questions
Is the automatic URL a real, working HTTPS address?
Yes — it is a fully resolvable, publicly reachable HTTPS URL under bunnyenv.com, secured with a real certificate, usable immediately by CI jobs, reviewers, or E2E test suites.
Does the URL change every time the environment redeploys?
No. The URL is tied to the environment's identity, not its current deployed state — it stays the same across redeploys, stops, and starts.
Can I use a branded domain instead of the auto-generated one?
Yes, by setting selfManagedDns and pointing your own DNS record (often a wildcard) at the cluster ingress, with cert-manager handling automatic SSL.