<span style="font-family: Arial, Helvetica, Sans-Serif; font-size: 12px"><div>Ah, totally my mistake. These days, for various projects, I tend to go straight to GitHub and download from Releases page.</div>
<div> </div>
<div>I see that for GeoMoose, the place to download packages is https://www.geomoose.org/download.html. Maybe a note in the Quickstart for *nix -systems doc would make thinks obvious for GitHub'ers like me.</div>
<div> </div>
<div>Many Thanks,</div>
<div>Brent</div>
<div> </div>
<div> </div>
<div style="-webkit-touch-callout: none; -webkit-user-select: none; -khtml-user-select: none;-moz-user-select: none;-ms-user-select: none;-o-user-select: none;user-select: none;"> </div>
<div> </div>
<hr align="center" size="2" width="100%" />
<div><span style="font-family: tahoma,arial,sans-serif; font-size: 10pt;"><b>From</b>: "James Klassen" <klassen.js@gmail.com><br />
<b>Sent</b>: July 17, 2020 2:08 PM<br />
<b>To</b>: "Brent Fraser" <bfraser@geoanalytic.com><br />
<b>Cc</b>: "GeoMOOSE PSC" <geomoose-psc@lists.osgeo.org><br />
<b>Subject</b>: Re: [geomoose-psc] dist contents in Releases</span>
<div> </div>
<div dir="auto">
<div>I'm not sure what you are asking. All of the packages/releases have the dist directory already.</div>
<div dir="auto"> </div>
<div dir="auto">If they have no intention of debugging, etc and just want to get on with it, they can download and extract from gm3-examples-3.6.2.zip (and gm3-demo-data-3.6.0.zip if they are interested in that, it is separate because it has little use to production users). Or they can install with 'npm install geomoose/gm3' or they can download gm3-npm-3.6.2.zip and extract it manually.</div>
<div dir="auto"> </div>
<div dir="auto">If they want to upgrade, they can replace their existing geomoose folder with a newer one from one of the above sources (which is where using npm can make life easier). And then merge in whatever new features they might want into their app.js/mapbook/index.html (or however they have organised equivalents in their implementation). The main idea here is (following symver) replacing the geomoose folder with a newer version should not break their implementation (until, by definition, GeoMoose 4). This is meant to isolate "geomoose" files from "their" files so upgrades don't overwrite "their" files (a problem that was common in GeoMoose 2). But this doesn't mean they will get all the new features without changes to "their" files.</div>
<div dir="auto"> </div>
<div dir="auto">My understanding is the status quo is as you are asking for. We ship a dist directory. All they need is unzip and a webserver that can serve static files (if they restrict to using external data services/GeoJSON*). They can use npm install and benefit from npm package manger (and not have to build GeoMoose) - which may be ideal if GeoMoose is just part of a larger site, or they can use git and use npm to build GeoMoose.</div>
<div dir="auto"> </div>
<div dir="auto">
<div dir="auto"> </div>
<div dir="auto">The only place that doesn't have a dist directory is the git repository because it is bad practice to keep build artifacts in the git repo (they can get out of sync and not match the source code, they can mask build system issues, they are redundant, they clutter diffs and logs, they make merges/PRs nearly impossible as almost any two changes will cause a conflict).</div>
<div dir="auto"> </div>
<div dir="auto"> </div>
* Also keep in mind GeoMoose is built on OGC standards because we don't expect that GeoMoose will be the only application that needs to access the data. The data should generally be managed separately as standard OGC services usable by many client applications (and need not be only MapSever). gm3-demo-data exists solely so we have something concrete to test and demo.<br />
<div class="gmail_quote" dir="auto">
<div class="gmail_attr" dir="ltr">On Fri, Jul 17, 2020, 13:51 Brent Fraser <<a href="mailto:bfraser@geoanalytic.com">bfraser@geoanalytic.com</a>> wrote:</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">Thanks for the info. I was wondering if a common use-case would be a Linux admin wanting to just install GeoMoose and try the demo with no intent to debug etc. Should we require them to install Node and do the build? Can we just include the geomoose.min.js in the dist dir?</span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">Thanks!</span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">Brent</span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></div>
<hr align="center" size="2" width="100%" />
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:tahoma,arial,sans-serif;font-size:10pt"><b>From</b>: "Jim Klassen" <<a href="mailto:klassen.js@gmail.com" rel="noreferrer" target="_blank">klassen.js@gmail.com</a>><br />
<b>Sent</b>: July 17, 2020 9:58 AM<br />
<b>To</b>: <a href="mailto:geomoose-psc@lists.osgeo.org" rel="noreferrer" target="_blank">geomoose-psc@lists.osgeo.org</a><br />
<b>Subject</b>: Re: [geomoose-psc] dist contents in Releases</span> </span>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></div>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<p><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">The /dist/ folder (and contents) is basically the sum total of the release. The rest of the files are included basically for convenience sake (source code, examples/demos, documentation) but aren't needed (well examples is needed for the out of the box "demo" but people really shouldn't be using that for a production application, but should use them as starting points and make their own files in their own folders).</span></p>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<p><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">The MS4W and Linux packages are structured differently to ease migration from GeoMoose 2.x. I would say installing from the NPM package or git would be the preferred/modern option.</span></p>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<p><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">The npm package has /package/dist</span></p>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<p><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">The Linux package has /gm3-exmaples/htdocs/geomoose/dist</span></p>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<p><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">The MS4W package has /ms4w/apps/gm3/htdocs/geomoose/dist</span></p>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<p><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></p>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">On 7/16/20 4:29 PM, Brent Fraser wrote:</span></div>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<blockquote type="cite">
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">Hi All,</span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> Is there a reason why we don't include the "dist" directory and contents (specifically geomoose.min.js) in a Release package?</span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">Thanks!</span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">Brent</span></span></div>
<div><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></span></div>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<fieldset><span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></fieldset>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span>
<pre>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px">_______________________________________________
geomoose-psc mailing list
<a href="mailto:geomoose-psc@lists.osgeo.org" rel="noreferrer" target="_blank">geomoose-psc@lists.osgeo.org</a>
<a href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a></span></pre>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></blockquote>
<span style="font-family:Arial,Helvetica,Sans-Serif;font-size:12px"> </span></div>
</blockquote>
</div>
</div>
</div>
</div></span>