Mathis/allianceauth
1
0
Fork 0
mirror of https://gitlab.com/allianceauth/allianceauth.git synced 2026-02-07 07:36:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Remove sudo from docs.

Browse Source 
Include section on logging DEBUG messages.
Cleanup some formatting.
This commit is contained in:
Adarnof
2018-04-21 17:00:18 -04:00
parent 98230d0ee3
commit 5d5cf92a19
11 changed files with 70 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/installation/auth/allianceauth.md
View File

@@ -2,7 +2,7 @@
```eval_rst
.. tip::
If you are uncomfortable with Linux permissions follow the steps below as the root user. Some commands do not behave the same when run with sudo.
If you are uncomfortable with Linux permissions follow the steps below as the root user.
```
## Dependencies

4
docs/installation/auth/gunicorn.md
View File

@@ -65,7 +65,7 @@ e.g. `command=/path/to/venv/bin/gunicorn myauth.wsgi`
### Starting via Supervisor
Once you have your configuration all sorted, you will need to reload your supervisor config `sudo service supervisor reload` and then you can start the Gunicorn server via `sudo supervisorctl start aauth-gunicorn` (or whatever you renamed it to). You should see something like the following `aauth-gunicorn: started`. If you get some other message, you'll need to consult the Supervisor log files, usually found in `/var/log/supervisor/`.
Once you have your configuration all sorted, you will need to reload your supervisor config `service supervisor reload` and then you can start the Gunicorn server via `supervisorctl start aauth-gunicorn` (or whatever you renamed it to). You should see something like the following `aauth-gunicorn: started`. If you get some other message, you'll need to consult the Supervisor log files, usually found in `/var/log/supervisor/`.
## Configuring your webserver
@@ -76,4 +76,4 @@ Any web server capable of proxy passing should be able to sit in front of Gunico
## Restarting Gunicorn
In the past when you made changes you restarted the entire Apache server. This is no longer required. When you update or make configuration changes that ask you to restart Apache, instead you can just restart Gunicorn:
`sudo supervisorctl restart myauth-gunicorn`, or the service name you chose for it.
`supervisorctl restart myauth-gunicorn`, or the service name you chose for it.

7
docs/installation/auth/upgradev1.md
View File

@@ -60,10 +60,13 @@ If you used member/blue group names other than the standard "Member" and "Blue"
Any permissions assigned to these groups will be copied to the state replacing them. Because these groups are no longer managed they pose a security risk and so are deleted at the end of the migration automatically.
### Run Migrations
Once you've configured any optional settings it is now safe to run the included migrations.
## Validating Upgrade
Before starting the Celery workers it's a good idea to validate the states were created and assigned correctly. Any mistakes now will trigger deletion of service accounts: if celery workers aren't running these tasks aren't yet processed. States can be checked through the admin site.
Before starting the Celery workers it's a good idea to validate the states were created and assigned correctly. Any mistakes now will trigger deletion of service accounts: if Celery workers aren't running these tasks aren't yet processed. States can be checked through the admin site.
The site (and not Celery) can be started with `supervisorctl start myauth:gunicorn`. Then navigate to the admin site and log in with your v1 username and password. States and User Profiles can be found under the Authentication app.