How hosting works
Understand what a Tilizy Hosting plan gives you: one server for one project, its environments, and how a push becomes a live release.
On this page
Tilizy Hosting gives one project a server of its own and deploys it from your Git repository. This page explains the pieces you will meet in the rest of the documentation: the server, the environments on it, what every plan includes, and what happens between a push and a live release. It applies to websites built with Drupal, WordPress, PrestaShop or Laravel.
One server, one project
A hosting plan is one server. A server runs one project, with as many environments of that website as fit in its processor, memory and disk. Your website does not share processor, memory or disk with any other project. A second project gets a server of its own.
The plan sets the size of the server: processor cores, memory, disk and backup storage. On the Ultra, Hyper and Apex plans the processor cores are reserved for you alone. On the other plans the cores are shared with other servers in the data centre, which suits most websites.
Environments
An environment is a complete running copy of your website: the code of one branch, its own database, its own files and its own address.
- Live is the environment your visitors use. Your domain points to it.
- Staging is a copy where you check a release before it goes live.
- A copy from a branch shows one feature on its own, for you or for someone who has to approve it.
There is no charge per environment. All environments share the processor and memory of your plan, and each one uses disk for its own copy of the site. Every environment runs the same software as live, so what works on staging is likely to work on live.
What every plan includes
- As many environments as fit on the server.
- Every user of your team, at no extra cost.
- Deploys from Git, and rollback to the previous release.
- Backups, every day unless you choose another rhythm, kept away from your server in the backup storage of your plan.
- A managed firewall in front of your website. See the firewall documentation.
- The Tilizy CLI, a command-line tool for local development, data, deploys and rollbacks.
From a push to a live release
Your code stays in your repository. Tilizy reads it from there and builds your website from it. A deploy never changes files under the running website. It prepares a new release beside the old one and then switches.
- Something triggers a deploy. Each environment has its own rule: every push to a branch, a release tag, or only when you ask.
- Build. Tilizy fetches that commit and runs your build steps in a separate build container. The running website is not touched.
- Database changes. If the release changes the structure of your database, visitors see a maintenance page for a few seconds while those changes run. A release that changes only code or content shows no maintenance page.
- Check. Tilizy confirms that the new release starts against the database.
- Switch. Visitors move to the new release in one step.
- Keep. The previous release stays on the server, so you can roll back with one command or one click.
If the build or the check fails, nothing changes: the previous release keeps serving.
One set of files describes your hosting
How your website is built and run is written in a small folder in your repository, .tilizy/. The file .tilizy/app.yaml holds the PHP version, the build steps, the scheduled jobs and the folders that must survive a deploy. The file .tilizy/services.yaml lists the database, the cache and the search engine. You change your hosting with a commit and review it like any other change. The same files drive live, staging and the copy on your own computer.
Where you work
You manage your hosting in the portal at app.tilizy.com and, if you want, from your terminal with the Tilizy CLI. You do not have to use the command line: deploys happen when you push to Git.
Next: Connect a Git repository, then write the project file.