- apache with mod_jk.so
- postgres 7.1.x
- ant (a java-based make)
-
+- jaxp-1.1 (a SAX 2.0 compliant XML parser, comes with ant >= 1.4)
1. checkout the cvs
4. copy the mir/templates-dist-directory to mir/templates
-5. compile
+5. compile (do this as root so the permissions script is able to set
+the permissions and owners correctly).
+
sh build.sh
cat dbscripts/help*.sql | psql -Upostgres dbname
cat dbscripts/populate*.sql | psql -Upostgres dbname
+
10. Add the dupe prevention trigger to the database:
cd dbscripts/dupetrigger
There, read INSTALL and follow the instructions.
-11. Set permissions
+11. Set permissions -- IMPORTANT! READ THIS!
We provide a script that sets all files' and direcories' permissions to
- a quite reasonable state.
+ a quite reasonable state. The most important thing you have to do after
+ the invokation of this script is to ensure that the log files --
+ especially dbentity.log -- are not readable by users that could
+ compromise system security, because all passwords and the like will
+ be logged here.
cp perms.sh-dist perms.sh
# Now, change the install directory and group in perms.sh
./perms.sh
+
+
12. restart tomcat
13. configure mod_jk
in Mir/src nor in Mir/WEB-INF/classes) is world-readable. Else you wouldn't
have to install a password, anyway.
-If you can't access PostgreSQL after this for any reason, try to change
-"password" in /etc/postgresql/pg_hba.conf into "trust". This should disable
+If you can't access PostgreSQL after this for any reason, try and change
+"password" in /etc/postgresql/pg_hba.conf to "trust". This should disable
any authentication method and make the database accessible again.
that's it :)
http://host/OpenMir
standard login is redaktion/indymedia
+
+
+
+TROUBLESHOOTING
+
+You can give these a try if anything goes wrong:
+
++ Restart Tomcat. Especially after compiling the sources Tomcat has to be
+ restarted.
+
++ Check file permissions and ownership. Try and run perms.sh.
\ No newline at end of file