Learn how to install Cachet on your server.
Cachet requires a few things to run. You’ll need:
ext-gd
, ext-simplexml
, mcrypt
and ext-xml
installed.You should install Composer globally. This is a dependency manager for PHP and is used to install Cachet’s dependencies. We recommend following Composer’s own installation guide.
Once Composer is installed, you can install the dependencies.
The tags below are examples of what will be shown. You should always run git checkout
on the latest tag.
By default, Cachet comes with a .env.example
file. You’ll need to rename this file to just .env
regardless of what environment you’re working on.
It’s now just a case of editing this new .env
file and setting the values of your setup.
Any values with spaces in them should be contained within double quotes.
If you’re using SQLite then your .env
file should not contain a DB_HOST
key. You’ll also need to touch ./database/database.sqlite
and give it the required permissions.
Before going any further, we need to set the APP_KEY
config. This is used for all encryption used in Cachet.
Be sure that you have the right permissions to the .env
file before running this command.
Cachet comes with an installation command that will do the following for you:
Never change the APP_KEY
after installation on production environment. This will result in all encrypted/hashed data being lost.
If you see a 500 error when visiting your status page, you may need to run chmod -R 777 storage
for it to work or rm -rf bootstrap/cache/*
You can also try to give permissions to cache chmod -R 777 bootstrap/
Learn how to install Cachet on your server.
Cachet requires a few things to run. You’ll need:
ext-gd
, ext-simplexml
, mcrypt
and ext-xml
installed.You should install Composer globally. This is a dependency manager for PHP and is used to install Cachet’s dependencies. We recommend following Composer’s own installation guide.
Once Composer is installed, you can install the dependencies.
The tags below are examples of what will be shown. You should always run git checkout
on the latest tag.
By default, Cachet comes with a .env.example
file. You’ll need to rename this file to just .env
regardless of what environment you’re working on.
It’s now just a case of editing this new .env
file and setting the values of your setup.
Any values with spaces in them should be contained within double quotes.
If you’re using SQLite then your .env
file should not contain a DB_HOST
key. You’ll also need to touch ./database/database.sqlite
and give it the required permissions.
Before going any further, we need to set the APP_KEY
config. This is used for all encryption used in Cachet.
Be sure that you have the right permissions to the .env
file before running this command.
Cachet comes with an installation command that will do the following for you:
Never change the APP_KEY
after installation on production environment. This will result in all encrypted/hashed data being lost.
If you see a 500 error when visiting your status page, you may need to run chmod -R 777 storage
for it to work or rm -rf bootstrap/cache/*
You can also try to give permissions to cache chmod -R 777 bootstrap/