Making In-Browser Coding Safe
Coding and saving directly in your browser sounds incredibly convenient. But for developers, the word "directly" can sometimes send shivers down your spine.
"Wait, so the moment I hit Ctrl+S or Cmd+S, my half-written, broken code is instantly deployed to the live production site?"
It’s a terrifying thought. If your live site breaks every time you hit save, that’s not a development tool—that’s a ticking time bomb for user complaints.
To prevent this, Essepage utilizes The Apply Model, strictly separating your 'Development Environment' from your 'Production Environment'.
Two Completely Isolated Environments: Dev vs. Prod
In Essepage, the URL you use for development (Dev) and the URL your end-users access (Prod) are entirely different.
When you are coding in the editor and checking the live preview, your Development URL looks like this:
https://espg.dev/mysite:xxxxxyyyyy-zzzzz/aboutThat :xxxxxyyyyy-zzzzz is a temporary security token that refreshes at regular intervals. This URL acts as your private, secure sandbox—valid only for your active development session.
On the other hand, once everything is polished, your visitors will access the clean Production URL:
https://espg.dev/mysite/aboutSave vs. Apply
Because these two environments are isolated, deploying your code naturally happens in two steps:
- Save: When you write code and hit save, it only updates the 'Development Environment'. You can test your code freely in the preview window with zero fear of breaking the live site.
- Apply: Once your testing is complete, it’s time to deploy your changes to the 'Production Environment'. This action is called Apply.
💡 Publish vs. Apply
If you look closely at the Essepage editor menu, you'll notice a distinct UI detail.
If you've just created a new file and it has never been deployed to production, the menu will sayPublish.
Once the initial publish is done, any subsequent updates will change the menu toApply.
If you've ever used a CMS, you already know this concept. Save is saving a 'Draft', and Publish/Apply is pushing it live.
Essepage also offers an incredibly useful feature: Apply All. If you edit multiple files—say, updating common component files like a Header or Footer—you can deploy all those changes to the production environment simultaneously with a single click, ensuring consistency across your site.
Instant Deploy: Zero Build Time
Most modern web development workflows require a build step before your changes can be viewed or deployed.
Essepage eliminates the build step entirely. The moment you hit Apply, your code is immediately reflected on the live page.
The Apply function essentially combines the build and deploy processes into a single, instant action.
⚠️ A quick heads-up: Cache Propagation takes up to 1 minute
To ensure your web pages load blazingly fast globally, Essepage utilizes a powerful CDN caching system. Even though your origin updates the second you hit Apply, it can take up to 1 minute for the global CDN cache to fully invalidate and refresh with your new code.
So, if you click Apply, check your live site, and don't see the changes immediately—don't panic. Take a sip of your coffee, hit refresh, and your updated page will be right there waiting for you.