mirror_php/Cachet
1
0
Fork 0
mirror of https://github.com/CachetHQ/Cachet.git synced 2025-01-17 13:38:20 +01:00
Code Issues Projects Releases Wiki Activity

Reorganise the install document

Browse Source
This commit is contained in:
James Brooks 2015-01-05 21:43:43 +00:00
parent 2db59fb54d
commit 278d71cb27
1 changed files with 12 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/setup/install.md
View File

@ -34,7 +34,6 @@ The easiest way is to use Git to pull down the code. You'll need to put it into
$ cd /var/www
$ git clone https://github.com/cachethq/Cachet.git
$ cd Cachet
$ composer install --no-dev -o
```
You will also need to build the assets.
@ -45,10 +44,6 @@ $ bower install
$ gulp
```
# Deploy to Heroku
When using the **Deploy to Heroku** button you needn't worry about using a database as the install will setup a free instance of ClearDB. Once installed Heroku can direct you to the setup page where you'll configure the site/application information and create an administrator account.
# Configuring a database without Heroku
Cachet relies on a database to store the components and incidents, however it needs to be configured for your [environment](https://github.com/cachethq/Cachet/blob/master/docs/setup/install.md#environment-detection).
@ -88,6 +83,18 @@ return [
> Even though SQLite doesn't require a host, username or password, these still must be set (an empty string will suffice).
# Install dependencies
Now we need to install of the dependencies that Cachet requires:
```bash
$ composer install --no-dev -o
```
# Deploy to Heroku
When using the **Deploy to Heroku** button you needn't worry about using a database as the install will setup a free instance of ClearDB. Once installed Heroku can direct you to the setup page where you'll configure the site/application information and create an administrator account.
### Running database migrations
Once we've decided on our database, we now need to run the migrations to create the tables. In our command line we need to run the migrations, from within the root directory: