Files

Christophe Sauthier 552372398a Update the documentation layout and content

Update the documentation layout and content to reflect the admin, installation
and config sections.

Change-Id: Ia4ce25cf18d3cff64eef7eec01c8abe079f1b72a
Closes-Bug: #1706157

2017-07-26 12:31:46 +02:00

1.8 KiB

Raw Blame History

Installing the API behind mod_wsgi

Cloudkitty comes with a few example files for configuring the API service to run behind Apache with mod_wsgi.

app.wsgi

The file cloudkitty/api/app.wsgi sets up the V1 API WSGI application. The file needs to be copied to /var/www/cloudkitty/, and should not need to be modified.

etc/apache2/cloudkitty

The etc/apache2/cloudkitty file contains example settings that work with a copy of cloudkitty installed via devstack.

../../../etc/apache2/cloudkitty

On deb-based systems copy or symlink the file to /etc/apache2/sites-available. For rpm-based systems the file will go in /etc/httpd/conf.d.
Modify the WSGIDaemonProcess directive to set the user and group values to an appropriate user on your server. In many installations cloudkitty will be correct.
Enable the cloudkitty site. On deb-based systems:
```
# a2ensite cloudkitty
# service apache2 reload
```
On rpm-based systems:
```
# service httpd reload
```

1.8 KiB Raw Blame History

Installing the API behind mod_wsgi

app.wsgi

etc/apache2/cloudkitty

1.8 KiB

Raw Blame History