1 Here is a short installation-howto of Mir.
7 - apache with mod_jk.so
9 - ant (a java-based make)
16 cvs -d :pserver: cvsanon@brazil.indymedia.de:/var/cvs login
21 cvs -d :pserver: cvsanon@brazil.indymedia.de:/var/cvs co mir
24 2. customize the config:
27 cp config.properties-dist config.properties
29 now customize config.properties for your needs.
32 3. configure the build.sh file with java_home
33 cp build.sh-dist build.sh
37 4. copy the mir/template-dist-directory to mir/template
44 6. Link in the webapps directory of tomcat to the install directory (the
45 directory is called "Mir" and is located in the same directory in which
46 you installed the "mir" directory).
47 cd /usr/share/tomcat/webapps
48 ln -s Mir-install-dir Mir
51 7. create a new database
52 the database name should be the same as in config.properties
58 psql -Upostgres dbname < dbscripts/create_pg.sql
59 cat dbscript/help*.sql | psql -Upostgres dbname
60 cat dbscript/populate*.sql | psql -Upostgres dbname
62 9. Add the dupe prevention trigger to the database:
63 cd dbscripts/dupetrigger
65 There, read INSTALL and follow the instructions.
74 insert the following patch into /etc/apache/httpd.conf. Edit the directories
78 JkWorkersFile /usr/share/tomcat/conf/workers.properties
79 Include /usr/share/tomcat/conf/mod_jk.conf-auto
82 Do not put any JkMount lines into your httpd.conf!
84 If mod_jk.conf-auto doesn't get written or is 0 bytes in size, check your
85 system for file ownership/permissions problems.
88 13. Add a password to your PostgreSQL user and link it to Mir (optional)
90 Add a hard to guess password to the PostgreSQL user database:
92 # psql -U postgres Mir
93 alter user postgres with password 'yourpassword';
96 Then, in /etc/postgresql/pg_hba.conf you should make sure that nobody can
97 use the database without a password:
100 host all 127.0.0.1 255.0.0.0 password
101 host all 0.0.0.0 0.0.0.0 reject
104 Then, change the database password line in config.properties:
106 Database.Username=postgres
107 Database.Password=yourpassword
109 You should make sure that no copy of config.properties (neither in mir nor
110 in Mir/src nor in Mir/WEB-INF/classes) is world-readable. Else you wouldn't
111 have to install a password, anyway.
113 If you can't access PostgreSQL after this for any reason, try to change
114 "password" in /etc/postgresql/pg_hba.conf into "trust". This should disable
115 any authentication method and make the database accessible again.
119 now the admin-application is accesable via:
123 and the openposting-servlet via
127 standard login is redaktion/indymedia