From d264bd767d5396de5255d1e0da3ad05bb3b889ae Mon Sep 17 00:00:00 2001 From: Landry Breuil Date: Tue, 12 Nov 2024 14:47:23 +0000 Subject: [PATCH] document how to run a local backend using an h2 database (#712, #713) --- docs/source/developer/index.rst | 41 ++++++++++++++++++++++++++++++++- 1 file changed, 40 insertions(+), 1 deletion(-) diff --git a/docs/source/developer/index.rst b/docs/source/developer/index.rst index 3690a6de2..ccd6096a2 100644 --- a/docs/source/developer/index.rst +++ b/docs/source/developer/index.rst @@ -66,9 +66,48 @@ To deploy your local backend you will need to: * properly change the configuration files, in particular to set the database and LDAP repository connection settings -If you don't have a local database and LDAP repository properly configured for geOrchestra you can use remote ones. +If you don't have a local database and LDAP repository properly configured for geOrchestra you can use remote ones, +by configuring their access in ``web/src/main/resources/mapstore.properties`` + Remember: to use a local backend both a PostgreSQL database and LDAP repository needs to be available and properly populated. +If you dont want to have a PostgreSQL database, you can fallback to h2 using this diff: + +.. code-block:: diff + :caption: web/src/main/resources/applicationContext.xml.diff + @@ -127,15 +127,8 @@ + + + + - + - + - + - + - + - + - + - + - + + + + + + + @@ -155,7 +148,7 @@ + + + + - + + + + + + +running the local backend with ``npm run backend:dev`` will create a new ``test.h2.db`` database in the tomcat root. + +if you start the local backend outside of an existing tomcat instance, you should also set the ``georchestra.datadir`` +property in the ``properties`` `section of web/pom.xml `_, pointing at the full path of your local datadir. + Developing the frontend -----------------------