Jeff -
I've been playing with some HTML templates for my RAMADDA
web pages, and have a hopefully simple question to be sure
I'm not missing something and am understanding this correctly.
I have two projects that would like to use RAMADDA. They
are using the same web server, and the same disk... but
otherwise, their projects are unrelated.
I have a html/css template for each.
But - I don't think I can configure the two templates based
on the project (directory/folder), true? One project will
use logins/usernames, but the other will not. And, even if
they did both have users log in --- the entry login-page
would be shared, so the top-level HTML template would have
to be shared.
If this is correct, then I'll need to split and run two
instances of RAMADDA (and hope there is not a 3rd, 4th, etc
project sharing this same machine!). Would you recommend
using the shared-database with multiple servers approach,
or having two completely distinct instances?
Thanks for your help.
Laurie Carson
(JNT/RAL/NCAR)
Hi Laurie,
Right now there isn't a way to associate a template with an entry (or tree of entries). But, this is something Don Murray and I were just talking about the other day. We're going to add the ability to specify a template (using the Page Style metadata) for different sections of RAMADDA.
But, as you point, this will only work for when you are looking at entries. For the search or login page there isn't an entry to get the template from. So, you could have a common template for the search/login/help pages and then have specific templates for particular areas of RAMADDA.
I'll try to add the templates to the Page Style metadata this weekend.
If this doesn't work for you you can run 2 separate ramadda instances under the same tomcat (someone is running 200+ instances). Its not documented how to do this but if you want to go down that route I'll write something up. They would have separate databases, files, etc.
-Jeff
Laurie,
I'm implementing the page template as metadata and will get it out this weekend.
I just realized that I keep track of the last entry a user was viewing and will use that when they go to search, login, etc. So, once a user is in a folder hierarchy that has a page template when they go to some non-entry page (e.g., search) the page template will stick with them.
-Jeff