Mostly a thorough test and cleanup. The significant change is moving the systemd
config into the deployment docs an the registration/security considerations to
production considerations docs.
flup is not supported on Python3, so MediaGoblin doesn't have a supported way to enable FastCGI support.
This change removes all references to flup and FastCGI and updates deployment instructions to use simple HTTP forwarding with nginx to access mediagoblin's non-static resources.
The user_dev directory gets created when users get established
and they start uploading media. However, the permissions aren't
correct on the directory as it gets created.
As a workaround, we create the directory at this stage, and then
set the proper permissions.
See this mailing list post for more information:
http://lists.mediagoblin.org/pipermail/devel/2015-May/001201.html
Added nginx to installation packages. We say that our install uses
nginx, so users should skip nginx if they want to use apache. Also,
our group permissions depend on a web server being installed.
Changed install directory for mediagoblin acct to /var/lib/mediagoblin
It works better if we need to back up data.
Assigned mediagoblin user to the same group as the web server. This
is needed so that the server can access uploaded media.
Created mediagoblin group for non-web-server things such as logs.
Debian-based platforms start the postgres server by default after
installation. For RPM-based distros, we've already issued these
commands prior to configuring the postgres server.
Need to enable / start postgres database on rpm-based distros
before you create the postgres mediagoblin user and database.
If you don't start the database server, you can't create a
database user or database.
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.
Some scripts on the internet have referenced paste_local.ini, so
it is safer to have a copy on the filesystem by default, even if
the user doesn't need to change any of the values for a regular
setup.
- Use sudo instead of root user but give info on how to configure sudo.
- Changed docs to reference Jessie as the stable version of Debian
- Corrected the command to create the 'mediagoblin' system account
- Fixes https://issues.mediagoblin.org/ticket/5083
There was a note informing the user that they should be aware that we
encourage them to install from the *master* branch, but we no longer
do that. If they follow our deployment docs, they will pull in &
use the *stable* branch.
Also clarified some root / non-root system usage by either specifying
a leading *hash* symbol to indicate a root-based command, or a
dollar sign to indicate a non-root command.
Added information about needed packages for RPM-based systems,
and simplified instructions to rely on the root account rather than
sudo-based instructions.
If a user has sudo access, they can easily add "sudo" to the needed
commands.
Also added information about enabling postgres to start on boot
and how to start it for the current session.
'adduser' is installed on Debian-based systems by default, but is
not installed by default on Fedora-based systems. 'useradd' is
installed by default on Debian-based systems, as well. The
'useradd'-based command provides the same functionality as
'adduser' in this case, though setting up a 'system' user with
no password.
Per bug 886, I've added the '--user-group' flag, which creates a
mediagoblin group, and assigns the mediagoblin user to this
group, too.
Some distributions (ubuntu 14.04 maybe?) don't create a
group for a new user. So change the "chown" to use the
primary group of the user instead of forcing the group.
This should do the right thing in more cases.
Old: chown mediagoblin:mediagoblin
New: chown mediagoblin:
