heckyel/mediagoblin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Removed chkconfig cmd. Made 'exit' more explicit.

Browse Source 
The chkconfig command is only needed on CentOS 6, which isn't really
a supported multimedia platform. CentOS 7 and Fedora 21+
wouldn't require this command.

Also made the "exit" command (used after setting up the postgres
mediagoblin account and database) more explicit. This will help prevent
user errors for users who may skim through the documentation.
This commit is contained in:
Jim Campbell 2015-05-11 20:15:08 -05:00
parent ec255f63be
commit 7bba6d2e9c
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/source/siteadmin/deploying.rst
View File

@ -130,15 +130,12 @@ Then we'll create the database where all of our MediaGoblin data will be stored:
where the first ``mediagoblin`` is the database owner and the second where the first ``mediagoblin`` is the database owner and the second
``mediagoblin`` is the database name. ``mediagoblin`` is the database name.
Type ``exit`` to exit from the 'postgres' user account. Type ``exit`` to exit from the 'postgres' user account.::
exit
From here we just need to set the Postgres database to start on boot, and also From here we just need to set the Postgres database to start on boot, and also
start it up for this particular session. If you're on a platform that does not start it up for this particular session.::
use *systemd*, you can enter::
sudo chkconfig postgresql on && service postgresql start
Whereas users of *systemd*-based systems will need to enter::
sudo systemctl enable postgresql && systemctl start postgresql sudo systemctl enable postgresql && systemctl start postgresql