remove derived files from repo and add them to .gitignore about angular-esri-map

[jabadia]

related to discussion in #14

[tomwayson]

@jabadia I agree that I would prefer not to include the derived files in the repo, but if we want to use bower as the means of distributing the files, then we need to at least include dist (sad face).

I'd like to at least not include two copies of the built files, so I'm thinking ways to base gulp serve and gh-pages off the dist folder.

[patrickarlt]

The best solution to this I have found is Leaflets publish.sh file https://github.com/Leaflet/Leaflet/blob/master/build/publish.sh.

When you build it force checks in the built files in to a temporary release branch and tags the repo at that point then the temp branch is deleted. This means that the only point in which the built files are in the repo is at that tag.

[tomwayson]

And of course, since I used gulp, we can't take advantage of grunt-releaseable w/o either adding grunt, or creating gulp-releasable.

[tomwayson]

So, ignoring the built files under the app folder (#22) was half the solution. Ultimately, I think we should a publish task like @patrickarlt suggests. The question is if we need to do this before we the first public release.

I will try to take a look at this when I get a chance, but I don't know if this should be something that prevents us from going live.

In other words do we keep this in the Beta 1 milestone?

[tomwayson]

Looks like Esri leaflet has moved on from grunt-releasable to using custom publish/build scripts with gh-release. gh-release looks pretty 🔥, and seems like it could be useful in solving this issue.

[tomwayson]

Resolved (finally!) by 080f5a0