<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
All,
<div class=""><br class="">
</div>
<div class="">From the Windows side, I’ve also thought about OSGeo4W from time to time as an optional server framework for GeoMOOSE.</div>
<div class=""><br class="">
</div>
<div class="">I wonder what it would take to add that as an option. We’ve always been mainly in the MS4W camp, but maybe more (varied) is better.<br class="">
<div class=""><br class="">
</div>
<div class="">bobb</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Dec 23, 2015, at 10:26 AM, Brent Fraser <<a href="mailto:bfraser@geoanalytic.com" class="">bfraser@geoanalytic.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div bgcolor="#FFFFFF" text="#000000" class="">Good idea. A note for those Linux users who read the intro doc would be good.<br class="">
<br class="">
My changes to the intro doc assume MS4W. I'll have to look into OSGeo Live to understand the implications...<br class="">
<pre class="moz-signature" cols="72">Best Regards,
Brent Fraser</pre>
<div class="moz-cite-prefix">On 12/23/2015 9:20 AM, James Klassen wrote:<br class="">
</div>
<blockquote cite="mid:CAHqX7945=OgDk0FS_MZO27X3GYcVeJVomJScaC4QhxxmNHeB9g@mail.gmail.com" type="cite" class="">
<p dir="ltr" class="">Introductory material could also assume OSGeo Live which uses a similar layout to MS4W but under /usr/local/geomoose. Similarly there are the build from source on Linux guides I wrote in the GitHub wiki that produce the standard layout
in /srv/geomoose.</p>
<p dir="ltr" class="">Also, I am starting to think we need at least one line to the effect of that this is an introduction and not the only way. I fear people will be unaware of the power/flexibility present in the design of GeoMoose because we tend to downplay
it in the Intros. Maybe this material just needs to be a Chapter 2 or something.</p>
<div class="gmail_quote">On Dec 23, 2015 10:10 AM, "Dan Little" <<a moz-do-not-send="true" href="mailto:theduckylittle@gmail.com" class="">theduckylittle@gmail.com</a>> wrote:<br type="attribution" class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Given Brent's observations, Introductory material should assume ms4w and expect linux/UNIX users are advanced enough to adapt. <br class="">
<br class="">
On Wednesday, December 23, 2015, Basques, Bob (CI-StPaul) <<a moz-do-not-send="true" href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:bob.basques@ci.stpaul.mn.us">bob.basques@ci.stpaul.mn.us</a>>
wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
All,<br class="">
<br class="">
I agree it’s confusing on it’s own, but if there were more than one server package configuration to look at it wouldn’t seem as mysterious. I was planning ahead somewhat, with the eventual idea that more of these simple diagrams might appear over time.<br class="">
<br class="">
Should a bare minimum approach to having a running GeoMOOSE be taken then in the diagram. Also, what would the bare minimum look like?<br class="">
<br class="">
Need APACHE (or ISS) obviously, and . .<br class="">
<br class="">
I can put more detail in into the diagram related to MS4W specifically vs an option where Apache/PHP are installed separately.<br class="">
<br class="">
bobb<br class="">
<br class="">
<br class="">
> On Dec 23, 2015, at 7:15 AM, Dan Little <<a moz-do-not-send="true" class=""></a><a class="moz-txt-link-abbreviated" href="mailto:theduckylittle@gmail.com">theduckylittle@gmail.com</a>> wrote:<br class="">
><br class="">
> I think the wording about MS4W is out of place and maybe even confusing. If you install MS4W then Apache and PHP aren't optional -- they come with the package -- and if someone /just/ installed GeoMOOSE they aren't necessarily going to understand that MS4w
is optional in and of itself. They either (a) had the wherewithal to install it on their platform of choice or (b) installed it from MS4W. Either way putting the "optional framework" stuff on there could cloud the user's impressions.<br class="">
<br class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
Geomoose-users mailing list<br class="">
<a moz-do-not-send="true" href="mailto:Geomoose-users@lists.osgeo.org" class="">Geomoose-users@lists.osgeo.org</a><br class="">
<a moz-do-not-send="true" href="http://lists.osgeo.org/mailman/listinfo/geomoose-users" rel="noreferrer" target="_blank" class="">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br class="">
</blockquote>
</div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset> <br class="">
<pre wrap="" class="">_______________________________________________
Geomoose-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/geomoose-users">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a></pre>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">
Geomoose-users mailing list<br class="">
<a href="mailto:Geomoose-users@lists.osgeo.org" class="">Geomoose-users@lists.osgeo.org</a><br class="">
http://lists.osgeo.org/mailman/listinfo/geomoose-users</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</body>
</html>