[geomoose-psc] dist contents in Releases

[James Klassen]

Ah, that makes sense now.

We have a releases page on GitHub?  That's news to me.

On Fri, Jul 17, 2020, 15:20 Brent Fraser <bfraser at geoanalytic.com> wrote:

> Ah, totally my mistake.  These days, for various projects,  I tend to go
> straight to GitHub and download from Releases page.
>
> 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.
>
> Many Thanks,
> Brent
>
>
>
>
> ------------------------------
> *From*: "James Klassen" <klassen.js at gmail.com>
> *Sent*: July 17, 2020 2:08 PM
> *To*: "Brent Fraser" <bfraser at geoanalytic.com>
> *Cc*: "GeoMOOSE PSC" <geomoose-psc at lists.osgeo.org>
> *Subject*: Re: [geomoose-psc] dist contents in Releases
>
> I'm not sure what you are asking.  All of the packages/releases have the
> dist directory already.
>
> 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.
>
> 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.
>
> 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.
>
>
> 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).
>
>
> * 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.
>
> On Fri, Jul 17, 2020, 13:51 Brent Fraser <bfraser at geoanalytic.com> wrote:
>
>> 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?
>>
>> Thanks!
>> Brent
>>
>>
>>
>> ------------------------------
>> *From*: "Jim Klassen" <klassen.js at gmail.com>
>> *Sent*: July 17, 2020 9:58 AM
>> *To*: geomoose-psc at lists.osgeo.org
>> *Subject*: Re: [geomoose-psc] dist contents in Releases
>>
>>
>> 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).
>>
>> 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.
>>
>> The npm package has /package/dist
>>
>> The Linux package has /gm3-exmaples/htdocs/geomoose/dist
>>
>> The MS4W package has /ms4w/apps/gm3/htdocs/geomoose/dist
>>
>>
>> On 7/16/20 4:29 PM, Brent Fraser wrote:
>>
>>
>> Hi All,
>>
>>   Is there a reason why we don't include the "dist" directory and
>> contents (specifically geomoose.min.js) in a Release package?
>>
>> Thanks!
>> Brent
>>
>>
>>
>> _______________________________________________
>> geomoose-psc mailing listgeomoose-psc at lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/geomoose-psc
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-psc/attachments/20200717/2eaacc11/attachment.html>