1 Here is a short installation-howto of Mir.
7 - apache with mod_jk.so
9 - ant (a java-based make)
10 - jaxp-1.1 (a SAX 2.0 compliant XML parser, comes with ant >= 1.4)
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/templates-dist-directory to mir/templates
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
50 7. Modify your tomcat startup script and add an LD_LIBRARY_PATH variable
51 that points to the WEB-INF/lib directory of your Mir install dir. (called
52 "Mir"). Add something like the following at the top of tomcat.sh (tomcat.sh
53 is found in the "bin/" dir. under $TOMCAT_HOME):
54 LD_LIBRARY_PATH=/path/to/Mir-install-dir/WEB-INF/lib
56 An alternaive way to avoid this is to copy any dynamic library files
57 ending with ".so" in WEB-INF/lib to your jre/jdk lib directory (where the
58 other ".so" files live). Or, you can skip the whole thing and live without
59 "native" acceleration for image manipulation
62 8. create a new database
63 the database name should be the same as in config.properties
69 psql -Upostgres dbname < dbscripts/create_pg.sql
70 cat dbscripts/help*.sql | psql -Upostgres dbname
71 cat dbscripts/populate*.sql | psql -Upostgres dbname
73 10. Add the dupe prevention trigger to the database:
74 cd dbscripts/dupetrigger
76 There, read INSTALL and follow the instructions.
80 We provide a script that sets all files' and direcories' permissions to
81 a quite reasonable state. The most important thing you have to do after
82 the invokation of this script is to ensure that the log files --
83 especially dbentity.log -- are not readable by users that could
84 compromise system security, because all passwords and the like will
87 cp perms.sh-dist perms.sh
88 # Now, change the install directory and group in perms.sh
99 insert the following patch into /etc/apache/httpd.conf. Edit the directories
103 JkWorkersFile /usr/share/tomcat/conf/workers.properties
104 Include /usr/share/tomcat/conf/mod_jk.conf-auto
107 Do not put any JkMount lines into your httpd.conf!
109 If mod_jk.conf-auto doesn't get written or is 0 bytes in size, check your
110 system for file ownership/permissions problems.
113 14. Add a password to your PostgreSQL user and link it to Mir (optional)
115 Add a hard to guess password to the PostgreSQL user database:
117 # psql -U postgres Mir
118 alter user postgres with password 'yourpassword';
121 Then, in /etc/postgresql/pg_hba.conf you should make sure that nobody can
122 use the database without a password:
125 host all 127.0.0.1 255.0.0.0 password
126 host all 0.0.0.0 0.0.0.0 reject
129 Then, change the database password line in config.properties:
131 Database.Username=postgres
132 Database.Password=yourpassword
134 You should make sure that no copy of config.properties (neither in mir nor
135 in Mir/src nor in Mir/WEB-INF/classes) is world-readable. Else you wouldn't
136 have to install a password, anyway.
138 If you can't access PostgreSQL after this for any reason, try to change
139 "password" in /etc/postgresql/pg_hba.conf into "trust". This should disable
140 any authentication method and make the database accessible again.
144 now the admin-application is accesable via:
148 and the openposting-servlet via
152 standard login is redaktion/indymedia