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.
69 We provide a script that sets all files' and direcories' permissions to
70 a quite reasonable state.
72 cp perms.sh-dist perms.sh
73 # Now, change the install directory and group in perms.sh
82 insert the following patch into /etc/apache/httpd.conf. Edit the directories
86 JkWorkersFile /usr/share/tomcat/conf/workers.properties
87 Include /usr/share/tomcat/conf/mod_jk.conf-auto
90 Do not put any JkMount lines into your httpd.conf!
92 If mod_jk.conf-auto doesn't get written or is 0 bytes in size, check your
93 system for file ownership/permissions problems.
96 13. Add a password to your PostgreSQL user and link it to Mir (optional)
98 Add a hard to guess password to the PostgreSQL user database:
100 # psql -U postgres Mir
101 alter user postgres with password 'yourpassword';
104 Then, in /etc/postgresql/pg_hba.conf you should make sure that nobody can
105 use the database without a password:
108 host all 127.0.0.1 255.0.0.0 password
109 host all 0.0.0.0 0.0.0.0 reject
112 Then, change the database password line in config.properties:
114 Database.Username=postgres
115 Database.Password=yourpassword
117 You should make sure that no copy of config.properties (neither in mir nor
118 in Mir/src nor in Mir/WEB-INF/classes) is world-readable. Else you wouldn't
119 have to install a password, anyway.
121 If you can't access PostgreSQL after this for any reason, try to change
122 "password" in /etc/postgresql/pg_hba.conf into "trust". This should disable
123 any authentication method and make the database accessible again.
127 now the admin-application is accesable via:
131 and the openposting-servlet via
135 standard login is redaktion/indymedia