Gallery2 (G2) requires a database backend to function properly. Currently, G2 supports Oracle, MySQL, PostgreSQL, DB2, and MS SQL Server databases; the choice of which to use is completely up to you. To run thorugh the setup, you must have an empty database available that you plan to use with G2. The instructions below should help with getting the database established and available to the application. MySQL ----- # mysql mysql> create database gallery2; Query OK, 1 row affected (0.00 sec) mysql> PostgreSQL ---------- # su - postgres -bash-3.1$ createdb gallery2 CREATE DATABASE -bash-3.1$ We don't include instructions for creating databases in other RDBMS's here. That's it. You may wish to consult the upstream database documentation at http://dev.mysql.com/doc/ for MySQL or http://www.postgresql.org/docs/ for PostgreSQL for specifics on setting up TCP/IP connections or more advanced database tasks. Installation/setup ------------------ There are a few differences, mostly cosmetic between this package and the upstream distribution. First, upstream normally puts the login.txt auth token and config.php file in the install directory. This package moves those files to /etc/gallery2 and creates symlinks to them in /usr/share/gallery2. This is done to accomodate a read-only /usr environment. During the actual installation process, the following differences between the instructions displayed and the actual installation environment will have to be observed: Step 1 (Authentication): You will be asked to place the login.txt file in the gallery2 directory on your web server. This file should be placed in the /etc/gallery2/ directory instead. Step 3 (Installation type): The "Standard installation" option will initally refer to /usr/share/gallery2 as the destination for the new gallery. Please disregard this notice and refer to the note on step 4 below. Step 4 (Storage setup): The default selection for the image storage directory in this package is /srv/gallery2. You must chose a directory that the web server can write to - if you have a read-only /usr directory tree, the storage directory must be outside that tree. If you use the default seletion, you must create this directory yourself and ensure that it is writable by the user that your web server runs as (usually 'apache'). Step 7 (Create config file): This step will tell you that the config file, config.php, has been written to the gallery2 directory. It was actually written to /etc/gallery2. Update from older package ------------------------- If you are updating Gallery2 from a 2.1 series Fedora package, you will have to do some manual jockeying of the config.php file before pointing a web browser at the upgrade page. Your old config file will be in /usr/share/gallery2/config.php, the new config file's location is /etc/gallery2/config.php with a symlink to it from /usr/share/gallery2/config.php. This symlink will initially be named config.php.rpmnew; the old config file should be moved to /etc/gallery2, overwriting the newly created config.php, and the symlink renamed from config.php.rpmnew to config.php. KNOWN ISSUES ------------ Gallery2 has a feature available in it's admin console whereby a user can download and install new themes and modules from within the web interface. Because Fedora requires that web applications be in /usr/share/<pkgname> and that /usr be able to be read-only, this feature may not work in some environments. If you have a read-only /usr, you will not be able to use this feature and you will have to install new themes and modules by remounting /usr rw and using the yum/rpm commands to install the sub-packages. If this feature does work in your environment, please be advised that using it will result in the modules and themes you download not being present in the RPM database and not being managed by the system. Because of this second caveat, there are no plans to request an exception to the packaging guidelines to explicitly enable this feature.
