that user's default group instead. As a last resort, you can create
a new group like "gnusocial" and add the Web server's user to the group.
-4. You should also take this moment to make your 'avatar' and 'file' sub-
- directories writeable by the Web server. The _insecure_ way to do
- this is:
-
- chmod a+w /var/www/gnusocial/avatar
- chmod a+w /var/www/gnusocial/file
-
- You can also make the avatar, and file directories just writable by
- the Web server group, as noted above.
-
-5. Create a database to hold your site data. Something like this
+4. Create a database to hold your site data. Something like this
should work (you will be prompted for your database password):
mysqladmin -u "root" -p create social
a tool like phpMyAdmin to create a database. Check your hosting
service's documentation for how to create a new MariaDB database.)
-6. Create a new database account that GNU Social will use to access the
+5. Create a new database account that GNU Social will use to access the
database. If you have shell access, this will probably work from the
MariaDB shell:
to your preferred new database username and password. You may want to
test logging in to MariaDB as this new user.
-7. In a browser, navigate to the GNU Social install script; something like:
+6. In a browser, navigate to the GNU Social install script; something like:
https://social.example.net/install.php
install program will configure your site and install the initial,
almost-empty database.
-8. You should now be able to navigate to your social site's main directory
+7. You should now be able to navigate to your social site's main directory
and see the "Public Timeline", which will probably be empty. You can
now register new user, post some notices, edit your profile, etc.