Bower package needed! about dexie.js HOT 11 CLOSED

Little more detail, registering a bower package is pretty easy. http://bower.io/docs/creating-packages/

I think someone mentioned NPM in another issue as well.

from dexie.js.

Adding a bower package is simple, but before doing it I think the current built version should be moved to outside of the dist folder. A common issue with installing a package from bower is that you get tons of extra stuff which you don't want in a public folder on your web server. So the dist folder should be in the ignore array in bower.json.

@dfahlander What do you think about moving the latest folder outside of dist? Or even better, only having the latest code in dist and using git tags to reference older releases.

from dexie.js.

Maybe move older versions to dist/old/ would do? Then we could ignore that
folder.
Den 17 nov 2014 07:55 skrev "Anders Ekdahl" [email protected]:

Adding a bower package is simple, but before doing it I think the current
built version should be moved to outside of the dist folder. A common
issue with installing a package from bower is that you get tons of extra
stuff which you don't want in a public folder on your web server. So the
dist folder should be in the ignore array in bower.json.

@dfahlander https://github.com/dfahlander What do you think about
moving the latest folder outside of dist? Or even better, only having the
latest code in dist and using git tags to reference older releases.

—
Reply to this email directly or view it on GitHub
#26 (comment).

from dexie.js.

I'm not sure I understand why the built files are checked in, and I'm even less sure I understand the need to check in all old versions?

from dexie.js.

I would like to keep the older versions easily accessable without having to
spend much time investigating the history.
Den 17 nov 2014 13:02 skrev "Anders Ekdahl" [email protected]:

I'm not sure I understand why the built files are checked in, and I'm even
less sure I understand the need to check in all old versions?

—
Reply to this email directly or view it on GitHub
#26 (comment).

from dexie.js.

Well, okey, then I guess moving everything but the current version from
dist/ to dist/old/ would do.

On Mon, Nov 17, 2014 at 1:20 PM, David Fahlander [email protected]
wrote:

I would like to keep the older versions easily accessable without having
to
spend much time investigating the history.
Den 17 nov 2014 13:02 skrev "Anders Ekdahl" [email protected]:

I'm not sure I understand why the built files are checked in, and I'm
even
less sure I understand the need to check in all old versions?

—
Reply to this email directly or view it on GitHub
#26 (comment).

—
Reply to this email directly or view it on GitHub
#26 (comment).

from dexie.js.

I started working on this, and moving releases from dist/ to dist/allversions/ but that's not enough for bower. Bower doesn't work like npm in that you upload a package, you're supposed to use git tags for versions instead, and bower will checkout the correct tag. But since Dexie currently doesn't use tags, it can't be published to bower.

@dfahlander Any reason for not tagging releases in git?

from dexie.js.

Ok. We should take a look into github tags and see how we could start using
them. I suppose it's a good thing anyway. If you want and have the time
soon, please feel free to tag Dexie (I think I hould have gave you the
access as a contributor to Dexie). Otherwise, I'll look into it when I have
time, later this week.

2014-11-18 8:08 GMT+01:00 Anders Ekdahl [email protected]:

I started working on this, and moving releases from dist/ to
dist/allversions/ but that's not enough for bower. Bower doesn't work
like npm in that you upload a package, you're supposed to use git tags for
versions instead, and bower will checkout the correct tag. But since Dexie
currently doesn't use tags, it can't be published to bower.

@dfahlander https://github.com/dfahlander Any reason for not tagging
releases in git?

—
Reply to this email directly or view it on GitHub
#26 (comment).

from dexie.js.

Registered on bower. To add packe write:

bower install dexie

from dexie.js.

Just to throw it out there, git flow makes tagging & releases pretty easy. I've been using it on a project and am pretty happy. Just in case it is helpful, here is a resource for getting started:

http://danielkummer.github.io/git-flow-cheatsheet/

from dexie.js.

Quick comment, I just installed via bower & all I get is the package.json, bower.json & dist.

My two cents, I think its good to keep the dist folder in here with the .min.js files for those who pull and go.

May need/want to tweak the .bower.json so that the /src, /test & /samples come down with it as well.

Thanks!

from dexie.js.