After finding that https://trac.osgeo.org/featureserver was responding
with the full trac environment for the old trac instance I decided to
move the DocumentRoot of trac.osgeo.org down one directory, so to
have a more restricted environment for static documents.
Ideally the instances would be moved to live elsewhere (a good
candidate would be /osgeo/trac/env or similar) but for now, not
knowing what could be referencing the current paths I didn't do
that.
The new docroot, /var/www/trac/html, has now its own local git
repository. We are having a good amount of such repos now, time
to "centralize" them a bit ?
I changed DocumentRoot again to /osgeo/trac/htdocs.
For now, /osgeo/trac/instances is a symlink to /var/www/trac,
but I think it should really be the other way around.
Before moving the trac instance data, thought, I'd need to
know which directories are watched by the backup procedure
(if any). I guess we want to backup the "data" and "conf"
subdirectories of each trac instance.
--strk;
On Sat, May 14, 2016 at 05:17:34PM +0200, Sandro Santilli wrote:
After finding that https://trac.osgeo.org/featureserver was responding
with the full trac environment for the old trac instance I decided to
move the DocumentRoot of trac.osgeo.org down one directory, so to
have a more restricted environment for static documents.
Ideally the instances would be moved to live elsewhere (a good
candidate would be /osgeo/trac/env or similar) but for now, not
knowing what could be referencing the current paths I didn't do
that.
The new docroot, /var/www/trac/html, has now its own local git
repository. We are having a good amount of such repos now, time
to "centralize" them a bit ?
On Sat, May 14, 2016 at 05:48:50PM +0200, Markus Neteler wrote:
On Sat, May 14, 2016 at 5:41 PM, Sandro Santilli <strk@keybit.net> wrote:
> Before moving the trac instance data, thought, I'd need to
> know which directories are watched by the backup procedure
> (if any).
All I know is that is a bacula driven setup, see for example:
osgeo6:/etc/bacula/bacula-fd.conf
I don't have read access to that file (not a sudoers, would
you make me one ?).
Likewise on other machines.
I looked at the tracsvn machine and did find a "trac"
section but could not find any mention of the trac instances
files path or database accesses.
> I guess we want to backup the "data" and "conf"
> subdirectories of each trac instance.
.. and the rest as well.
The rest is database dumps, which I think Martin mentioned
being already backed up (but I hadn't seen an entry in bacula-fd.conf
there)