You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@marmotta.apache.org by wi...@apache.org on 2014/05/23 14:16:52 UTC
svn commit: r1597073 - in /marmotta/site/trunk:
content/markdown/configuration.md pom.xml
Author: wikier
Date: Fri May 23 12:16:52 2014
New Revision: 1597073
URL: http://svn.apache.org/r1597073
Log:
improved some details about the configuration
Modified:
marmotta/site/trunk/content/markdown/configuration.md
marmotta/site/trunk/pom.xml
Modified: marmotta/site/trunk/content/markdown/configuration.md
URL: http://svn.apache.org/viewvc/marmotta/site/trunk/content/markdown/configuration.md?rev=1597073&r1=1597072&r2=1597073&view=diff
==============================================================================
--- marmotta/site/trunk/content/markdown/configuration.md (original)
+++ marmotta/site/trunk/content/markdown/configuration.md Fri May 23 12:16:52 2014
@@ -2,17 +2,31 @@
# Configuring Apache Marmotta
-## Access Admin Interface
-
-You can now access the Apache Marmotta Web Application through your browser,
+You can now access the Apache Marmotta Web Admin Interface through your browser,
e.g. by accessing the URL:
-[http://localhost:8080/marmotta](http://localhost:8080/marmotta)
+[http://localhost:8080/marmotta](http://localhost:8080/marmotta). There you can
+configure quite some aspects of Marmotta.
+
+Marmotta uses a home directory to save some data. By default launchers will use
+`${java.io.tmpdir}${file.separator}marmotta` (`/tmp/marmotta` in Unix systems,
+`C:\Users\User Name\AppData\Local\Temp\marmotta` on Windows), but you can customize
+the path to that directory by using the `marmotta.home` system property or the
+`MARMOTTA_HOME` environment variable. In that directory, Marmotta uses the
+`system-config.properties` to store all system configuration.
-Note that the host name and port you are using for the first access of your
+Note that the host name and port you are using for the first access to your
installation is **important** since decides on how Linked Data resources will
be handled later. If you plan a production deployment, you should therefore
directly deploy on the server you are going to use and access it via the host
-name it will have in the future.
+name it will have in the future, or manually set the following settings:
+
+ kiwi.context = http://marmotta.example.org/
+ kiwi.host = http://marmotta.example.org/
+ kiwi.setup.host = true
+
+where `kiwi.context` indicates the base URI that Marmotta will consider for local
+resources, `kiwi.host` is the base URL to access the admin interface, and
+`kiwi.setup.host = true` avoids getting the host configuration overwritten.
<h2 id="db">Change Database Configuration</h2>
Modified: marmotta/site/trunk/pom.xml
URL: http://svn.apache.org/viewvc/marmotta/site/trunk/pom.xml?rev=1597073&r1=1597072&r2=1597073&view=diff
==============================================================================
--- marmotta/site/trunk/pom.xml (original)
+++ marmotta/site/trunk/pom.xml Fri May 23 12:16:52 2014
@@ -65,22 +65,6 @@
</snapshots>
</repository>
<repository>
- <!-- this repo needs to be removed one the release has been published -->
- <id>orgapachemarmotta-1008</id>
- <name>Apache Staging Repository for 3.2.0</name>
- <url>https://repository.apache.org/content/repositories/orgapachemarmotta-1008</url>
- <releases>
- <enabled>true</enabled>
- <updatePolicy>always</updatePolicy>
- <checksumPolicy>warn</checksumPolicy>
- </releases>
- <snapshots>
- <enabled>false</enabled>
- <updatePolicy>never</updatePolicy>
- <checksumPolicy>fail</checksumPolicy>
- </snapshots>
- </repository>
- <repository>
<id>apache.snapshots</id>
<name>Apache Snapshots Repository</name>
<url>https://repository.apache.org/content/repositories/snapshots/</url>