[THREDDS #CZI-169887]: thredds/content

Hi Roland,

Sounds good. Let us know if you have any thoughts or suggestions on any of this.

Ethan

Roland wrote:
> Ethan Davis wrote:
> > The use of the TOMCAT_HOME/content directory for storing configuration
> > files is not a servlet standard nor is it a widely used convention.
> > Thinking about it now, another option would be to set up a directory
> > in the user's home directory, though it would require a scheme to keep
> > the configuration for multiple TDS instances separate.
> 
> Thanks Ethan.  We currently set things up with the LAS configuration
> files in the same directory where they unpack and configure the server
> (typically the users home directory).  We are getting push back from at
> least one important customer that this set up is "not secure". Maybe it
> is because in our case we are actually writing some files into that
> directory.
> 
> I think we will be adopting your convention by putting the
> configuration and cache files we want to preserve under
> $TOMCAT_HOME/content/las.
> 
> > Yes, we developed the code ourselves to check and copy over the initial
> > content from the exploded war content.
> > 
> > We also allow TDS admins to change the "content" directory to somewhere
> > outside TOMCAT_HOME as described on this page:
> > 
> > http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/reference/InstallOptions.html#ChangeTdsContentDir
> > 
> > If you are interested in code level detail, most of the code for all
> > this is in thredds.servlet.ServletUtils and
> > thredds.server.config.TdsContext.
> 
> I'll have a look at that code.
>
> Thanks.
>
> Roland

Ticket Details
===================
Ticket ID: CZI-169887
Department: Support THREDDS
Priority: Normal
Status: Closed