X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2FINSTALL.mir;h=4f77dd9bc4e187cfe0703f6d8515b45e6a43fc9c;hb=d0e2badee53d1a09fe1ca790a086ca04122f06c0;hp=9906139f5b4c87976d9456ee5a2e80613aa0f6a7;hpb=57f0a98600101c3eb8652aaa7e1643fc7e17297b;p=mir.git diff --git a/doc/INSTALL.mir b/doc/INSTALL.mir index 9906139f..4f77dd9b 100755 --- a/doc/INSTALL.mir +++ b/doc/INSTALL.mir @@ -34,31 +34,104 @@ now customize config.properties for your needs. chmod 755 build.sh -4. copy the mir/template-dist-directory to mir/template +4. copy the mir/templates-dist-directory to mir/templates 5. compile sh build.sh -6. Link in the webapps directory of tomcat to the install directory (the directory is called Mir). +6. Link in the webapps directory of tomcat to the install directory (the +directory is called "Mir" and is located in the same directory in which +you installed the "mir" directory). + cd /usr/share/tomcat/webapps + ln -s Mir-install-dir Mir +7. Modify your tomcat startup script and add an LD_LIBRARY_PATH variable +that points to the WEB-INF/lib directory of your Mir install dir. (called +"Mir"). Add something like the following at the top of tomcat.sh (tomcat.sh +is found in the "bin/" dir. under $TOMCAT_HOME): + LD_LIBRARY_PATH=/path/to/Mir-install-dir/WEB-INF/lib -7. create a new database +An alternaive way to avoid this is to copy any dynamic library files +ending with ".so" in WEB-INF/lib to your jre/jdk lib directory (where the +other ".so" files live). Or, you can skip the whole thing and live without +"native" acceleration for image manipulation + + +8. create a new database the database name should be the same as in config.properties as user postgres: createdb dbname -8. create base table +9. create base table psql -Upostgres dbname < dbscripts/create_pg.sql - cat dbscript/help*.sql | psql -Upostgres dbname + 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 + We provide a script that sets all files' and direcories' permissions to + a quite reasonable state. + + cp perms.sh-dist perms.sh + # Now, change the install directory and group in perms.sh + edit perms.sh + ./perms.sh + + +12. restart tomcat + +13. configure mod_jk + +insert the following patch into /etc/apache/httpd.conf. Edit the directories +to suit your needs. + + +JkWorkersFile /usr/share/tomcat/conf/workers.properties +Include /usr/share/tomcat/conf/mod_jk.conf-auto + + +Do not put any JkMount lines into your httpd.conf! + +If mod_jk.conf-auto doesn't get written or is 0 bytes in size, check your +system for file ownership/permissions problems. + + +14. Add a password to your PostgreSQL user and link it to Mir (optional) + +Add a hard to guess password to the PostgreSQL user database: + +# psql -U postgres Mir +alter user postgres with password 'yourpassword'; + + +Then, in /etc/postgresql/pg_hba.conf you should make sure that nobody can +use the database without a password: + +local all password +host all 127.0.0.1 255.0.0.0 password +host all 0.0.0.0 0.0.0.0 reject + + +Then, change the database password line in config.properties: -9. chmod 777 Mir/log +Database.Username=postgres +Database.Password=yourpassword -10. restart tomcat +You should make sure that no copy of config.properties (neither in mir nor +in Mir/src nor in Mir/WEB-INF/classes) is world-readable. Else you wouldn't +have to install a password, anyway. -11. configure mod_jk +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 +any authentication method and make the database accessible again. that's it :) @@ -70,4 +143,4 @@ and the openposting-servlet via http://host/OpenMir -standard login is redaktion/indymedia \ No newline at end of file +standard login is redaktion/indymedia