Release pipeline: every update on test first, then live

An update of your website should be exciting for you, not for your visitors. At Daylit every new version can go through a release pipeline: first to its own test environment, checked automatically there, and only when everything is right to your live site. If live still goes wrong, Daylit puts the previous version back within minutes. Your data stays.

How it works

1. You deliver a new version as a package (a zip with your code and a short install script). Daylit notices it within a few minutes.
2. Test. The new version goes to a separate test environment: its own server with made-up demo data and its own address. Your live site notices nothing.
3. Smoke test. Daylit checks automatically that the site answers, that the version is right, that key pages work and that there are no new PHP errors in the log.
4. Live. When the smoke test passes, exactly the same package goes to your live site: by itself, or only when you press To production in My Daylit. You choose.
5. Check on live. After the update the same smoke test runs on your live site. If it fails, Daylit puts the previous version back at once and sends you an e-mail.

Always back, without losing data

Daylit keeps the last three versions of your site. One button puts an earlier version back. Only the code goes back; orders, customers and appointments made after the update stay. For emergencies Daylit also takes a snapshot of the whole server before every update.

TP, TAP or DTAP: your choice

• TP (Test → Production): the default. One test environment, then live. Enough for most websites and web shops.
• TAP (Test → Acceptance → Production): with an extra acceptance environment where you or your client look at the new version first. Only after Approve (with a code from your authenticator app) does it go live; never by itself.
• DTAP (Development → Test → Acceptance → Production): the full pipeline, with a development environment for your developer or agency, on its own address. On request: we arrange access for your developer with you.

DTAP + D: a demo environment of its own, safe to share

Next to the pipeline you can have a separate demo environment (D). It gets every version that goes live automatically and runs on made-up data, so you can show it to clients, sales people or technicians, also while work goes on in test. Without a separate demo, the test environment is used. From My Daylit you make an invitation with an end date and the role the recipient gets (for example sales, technician or demo customer) (24 hours, 3 days or a week) and send it by WhatsApp or e-mail. The link works only until the end date and you can revoke it at any time. Search engines do not see the test environment.

Who is it for?

For anyone who keeps their site up to date seriously: web shops, sites with an appointment planner or customer portal, and developers and agencies building for clients. You do not maintain servers, pipelines or scripts: Daylit runs the pipeline, the test server, the certificates and the checks.

See the plans or ask for a release pipeline for your site in My Daylit.