RAMADDA gets its content from 2 places - a database and the file system. You need to have RAMADDA running on some external database server (e.g., mysql, postgres). You configure your internal and external RAMADDA instances to use the same database.
For the file system you could have both RAMADDA's use the same RAMADDA home directory. But, there are some things in there that shouldn't be shared (e.g., properties files, plugins, log files, etc). So, its best to configure the RAMADDAs so each have their own home directory but configure the shared content directories to be the same.
To configure this add the following property to one of the local property files on your read-only server.
ramadda.readonly=trueSet the following properties to define any alternate storage directories:
ramadda.storage.storagedir=/some/dir/storage ramadda.storage.entriesdir=/some/dir/entries ramadda.storage.uploaddir=/some/dir/uploadsThese are the default settings. I know, I know, there should be one main storage directory property that can be set once but there isn't. Sorry.
Note: you can refer to the RAMADDA home dir with the %repositorydir% macro:
Note: you can also set the location of the log and tmp dirs:
ramadda.docache=falseThis just turns off RAMADDA's memory cache mechanism. But, if you are doing lots of simultaneous editing and deletion and moving of content on the different RAMADDA's you might run into some issues.