This is an automated notification sent by Gna!.
It relates to:
                task #735, project Savane



==============================================================================
LATEST MODIFICATIONS of task #735:
==============================================================================

Posted by:              an anonymous user
Posted on:              mar 09/11/2004 presso 19:19

------------------ Additional Follow-up Comments ----------------------------
I got my hardware fixed last Friday. I've thought of a couple of possibilities, 
but webapp support would always be partial. 



Anyway, maybe I came up with something that doesn't touch anything on savane 
code. I need some time to implement it, though, and it'll still require an 
admin to complete the installation. I'll work it out asap.



Sorry for the delay, but it was due to external causes.



==============================================================================
OVERVIEW of task #735:
==============================================================================

URL:
  <http://gna.org/task/?func=detailitem&item_id=735>

Project:                Savane
Submitted by:           Matteo Settenvini
Submitted on:           mar 07/09/2004 presso 17:08

Should Start On:                lun 27/09/2004 presso 00:00
Should be Finished on:          sab 23/10/2004 presso 00:00
Category:               Backend
Priority:               1 - Later
Status:         None
Privacy:                Public
Assigned to:            None
Percent Complete:               0%
Open/Closed:            Open
Effort:         0.00
Planned Release:                


Summary:                Support for Gentoo webapp-config: multiple installation 
of Savane on the same machine with different configuration files
_______________________________________________________

Original Submission:
This item should start after the merging of the CERN branch.



It should be possible to install savane multiple times on different vhosts on 
the same machine, and thus have a different configuration file / database for 
each one of them.



This will require some changes in the backend (probably in Savane::Conf?) to 
have it using an environment variable (SV_LOCAL_INC_PREFIX), like the frontend 
already does. 

Else, it'll use the default.


_______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: mar 09/11/2004 presso 19:19   By: 0 <None>
I got my hardware fixed last Friday. I've thought of a couple of possibilities, 
but webapp support would always be partial. 



Anyway, maybe I came up with something that doesn't touch anything on savane 
code. I need some time to implement it, though, and it'll still require an 
admin to complete the installation. I'll work it out asap.



Sorry for the delay, but it was due to external causes.

-------------------------------------------------------
Date: mar 09/11/2004 presso 18:20   By: Mathieu Roy <yeupou>
Any progress on this task?

-------------------------------------------------------
Date: mar 14/09/2004 presso 17:11   By: Mathieu Roy <yeupou>
Latest changes in CERN branch related to this:

SV_LOCAL_INC_PREFIX has been replaced by SAVANE_CONF (SV_LOCAL_INC_PREFIX is 
still accepted but no longer documented -- this is an old name who had it's 
logic two years ago, but it does no longe make sense).

SAVANE_CONF is honored by both the frontend and the backend. 
When SAVANE_CONF is not set, default goes to /etc/savannah, both on frontend 
and backend.

Distro scripts should just make sure SAVANE_CONF is set, to allow concurrent 
installation of Savane systems.













==============================================================================

This item URL is:
  <http://gna.org/task/?func=detailitem&item_id=735>

_______________________________________________
  Messaggio inviato via Gna!
  http://gna.org/


Reply via email to