Losing configuration on startup

[Dominik Jednoralski (via Magnolia Forums)]

Magnolians,

I'm building a Magnolia CE based webproject and am working on setting things up. As I'm currently not building a productive website, I'd be happy with the shipped Derby database for the moment.

I'm deploying two Magnolia instances (v5.2.8) in JBoss 7.1.1 AS. To my understanding, Derby table data is stored in the <JBOSS_HOME>/standalone/tmp/vfs folder which is cleaned by JBoss on every startup / redeployment. Sadly, this takes my configuration and content with it.

What would be a handy solution to this? Can I configure Derby to store on the local filesystem (outside of JBoss)? Better switch to some other DBS such as MySQL?

Thanks in advance,

Dominik

[Antti Hietala (via Magnolia Forums)]

Dominik,

Here are some tips for working outside the JBoss tmp directory.
http://documentation.magnolia-cms.com/display/DOCS/Deploying+a+WAR+on+JBoss+AS

Let us know if they solve your issue.

--Antti

[Dominik Jednoralski (via Magnolia Forums)]

Antti,

many thanks for your patience. How can I reference a windows-path, e.g. D:\MagnoliaRepo, when configuring magnolia.home?

[code]magnolia.home=/somewhere/outside/of/jboss/tmp/folder[/code]

Many thanks,

Dominik

[Antti Hietala (via Magnolia Forums)]

There's a tip at the start of the magnolia.properties file:

[code]#--------------------------------------------
# Here we define some properties not
# configured in the config repository.
# They are used in common before the initialization
# of the repositories.
#
# WARNING: on Windows systems, either use the /
# to separate path elements, or escape the \ with
# another \, i.e C:\\magnolia\\data\\repositories
# or c:/magnolia/data/repositories
#--------------------------------------------
[/code]

http://git.magnolia-cms.com/gitweb/?p=ce-bundle.pub.git;a=blob;f=magnolia-empty-webapp/src/main/webapp/WEB-INF/config/default/magnolia.properties

I'm not on a Windows system so can't verify. But try magnolia.home=D:\\MagnoliaRepo in your case.

--Antti

[Dominik Jednoralski (via Magnolia Forums)]

Antti,

many thanks, problem solved. Turned out I was editing the wrong magnolia.properties files and my path definition was overwritten further down the chain. So not a problem of path formatting.

Kind regards,

Dominik