Skip to content

Commit

Permalink
Update install instructions.
Browse files Browse the repository at this point in the history
  • Loading branch information
klaussilveira committed Jan 15, 2022
1 parent 8202e01 commit 746311f
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,8 @@ In order to run GitList on your server, you'll need:
* Webserver (Apache, nginx)

## Installation
* Download GitList from [gitlist.org](http://gitlist.org/) and decompress to your `/var/www/gitlist` folder, or anywhere else you want to place GitList.
* Do not download a branch or tag from GitHub, unless you want to use the development version. The version available for download at the website already has all dependencies bundled, so you don't have to use composer or any other tool
* Download the [latest release](https://github.com/klaussilveira/gitlist/releases) or the [nightly build](https://github.com/klaussilveira/gitlist/releases/download/nightly/gitlist-nightly.zip) and decompress to your `/var/www/gitlist` folder, or anywhere else you want to place GitList.
* Do not use the source release, or download a branch or tag from GitHub. It is not suited for end-users, only development.
* Open up the `config/config.yml` and configure your installation. You'll have to provide where your repositories are located.
* Alternatively, you can export the environment variable `DEFAULT_REPOSITORY_DIR` with the directory containing your repositories
* Create the cache and log folder and give it read/write permissions to your web server user:
Expand All @@ -42,6 +42,8 @@ mkdir -p var/log
chmod 777 var/log
```

* Point your webserver to the `/var/www/gitlist/public` folder, where `index.php` is.

That's it, installation complete! If you're having problems, check the [Troubleshooting](https://github.com/klaussilveira/gitlist/wiki/Troubleshooting) page.

## Development
Expand Down

0 comments on commit 746311f

Please sign in to comment.