Installing on server

There are many ways to install Zero One on your server, you can see how it generally works with Kirby

Friendly suggestion: The right way of developing a website is to develop, craft, and design it in localhost/staging, and just when the work is done, or almost done, to upload/push the website to the server. There are numerous benefits to that approach.

Panel install

You don't add a panel install option on the localhost server, only on the public.

To be able to use the panel dashboard on the server with the domain you must add

'panel' =>[
    'install' => true

In your site/config.php or renamed site/ (see Multi-environment setup if not sure), just below the following statement (for example)

'languages' => true,

You can learn more about config panel options at

Now, let's add it to the server. We will give you here two options, the simplest one, and our workflow with Git version control.

Just upload it and it's on

The simplest solution is just to upload all files from zero-one folder to your desired folder (domain root etc) on the server and it will work. That's it. 🙂

Git deploy

PLEASE NOTE: This is our opinionated way of doing it. You can of course do it differently.

Zero One is Git-ready, actually, the demo is pushed through Git.

We are one of those Bitbucket guys, we like their tools and Git workflow. Our workflow is simple, Push to the Bitbucket repository, and then Pull to the server through a secure connection. We have our custom-setup VPS server with Plesk, which is a very Git-friendly system.

There is a .gitignore file you should check out, in the website root.

Stop tracking the content folder

When you do work for a client and you want the content to be updated on the server, but to keep control over code updates through Git, then after installing on the server you should add this line in the theme root .gitignore file

# Ignore content

Run the next command in your terminal

git rm -r --cached path_to_your_content_folder/

And push changes. It will delete content folder on the server, but your local content folder will remain. After that upload manually content folder to the website root.

After this, your local content changes will not be tracked by Git.

Last updated