[Geomoose-users] Multiple sites sharing the same Geomoose code

[bobb]

All,

 From day one, I've wanted to take this idea to the next step and expose 
the layer catalog aspect to the end users.

The idea being to store some variables locally on the user end that list 
out the layers chosen by a user for display, and everything works 
automatically from that point on, the users could have multiple version 
of view configurations.

Could be an entirely different way of looking at the structure of things 
though.

The (master) layer catalog would become more of a user setting dialog, 
where the users can pull layers from for their viewing and isn't visible 
for the majority of the time.  The interface would operate pretty much 
as it does now, but only those layers chosen from the catalog would be 
displayed in it.  The MAPBOOK is built on the fly for the most part.

Anyway this used to be clearer in my mind way back, but so many more 
features have been added since . . .

:c)

Price of progress I guess.

bobb




On 12/6/10 11:31 AM, Jim Hagedorn wrote:
> All
>
> This is what I do to have multiple sites on the same geomoose.
>
> The main web page is a php page that sets the mapbook in a session variable.
>
> <?php
> 	session_start();
>      $_SESSION['settings'] = 'milbank_settings.ini';
> ?>
>
> So if I go to server/milbank.php it calls the Milbank mapbook.  I have 5 or 6 different sites on the same server using just one geomoose.
>
> Jim hagedorn
> Banner Associates
>
> -----Original Message-----
> From: Len Kne [mailto:lkne at houstoneng.com]
> Sent: Monday, December 06, 2010 11:16 AM
> To: 'Brent Fraser'; Bob Basques
> Cc: Geomooselist
> Subject: Re: [Geomoose-users] Multiple sites sharing the same Geomoose code
>
> Hi Brent
>
> We are doing something similar:
>
> We use a session variable to set settings.ini, which in turn sets the Mapbook.  See http://www.geomoose.org/wiki/index.php/Modification_to_Use_Multiple_Map_Books
>
> Len
>
> -----Original Message-----
> From: Brent Fraser [mailto:bfraser at geoanalytic.com]
> Sent: Monday, December 06, 2010 11:11 AM
> To: Bob Basques
> Cc: Geomooselist
> Subject: [Geomoose-users] Multiple sites sharing the same Geomoose code
>
> Bob (and others),
>
>     I've been thinking about enhancing GeoMoose to allow multiple "map sites" to share the same GeoMoose code, mostly to improve the ease of
> maintenance.  Rigth now I just copy the entire gemoose2 directory.
> While that is expedient (and allows me to tweak parts of the GUI without fear of impacting other sites), I'm deferring an upgrade nightmare.
>
> Instead of having geomoose.html as the site url, my strategy is to have something like:
>
> http://myserver/maps/php/geomoose_start.php?conf=site1
>
> The geomoose_start.php script would set a SESSION variable for the ini file name:
>      $_SESSION['ini_file'] = '../../conf/'.$_REQUEST['conf'];
>
> This would be used in config.php; so  instead of the current:
>       $CONFIGURATION = parse_ini_file('../../conf/settings.ini');
> it would be :
>       $CONFIGURATION = $_SESSION['ini_file'];
>
>
> geomoose_start.php would also read and send the site html file (e.g.
> site1_html.txt) to browser.  i think those are the only changes I'd need to make...
>
> FYI, the directory structure would be:
>
> geomoose2
>       conf\
>           site1.ini
>           site1.xml
>           site2.ini
>           site2.xml
>              :
>
>       htdocs\
>           site1_html.txt
>           site2_html.txt
>              :
>
>           skins\site1\site.css (optional)
>           skins\site2\site.css (optional)
>              :
>
>       maps\
>           site1\
>           site2\
>              :
>
> Your thoughts?
>
> --
> Best Regards,
> Brent Fraser
>
>
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geomoose-users
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geomoose-users
>
> ------------------------------------------------------------------------------
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geomoose-users