Generated JS is checked into git about strut HOT 6 CLOSED

Oh, actually I don’t know if that’s supposed to be. @tantaman can you check, and if need be revert my commit 4a488fc

Also, if the templates are not supposed to be committed, we should add them to the .gitignore

from strut.

Side note: It makes git reset --hard and git stash useless, as rake compileCoffee[w] will immediately change the tree after these commands.

from strut.

The main reason I checked in the generated code was so people could run Strut right after checking it out. The proper solution would be to provide pre-built downloads for people that just want to run Strut on their own box without doing anything.

So I agree. We should remove the generated code once a built version is available for download.

from strut.

Optimally, building a download zip/tar should be automated. There are two ways:

1. Build it automatically on you machine and upload it to github, e.g. with a rake upload:

   see Programmatically add files to a GitHub download page

2. Use TravisCI to build it for you automatically and upload it to github.

   This is not really possible yet, as there is no way yet to securely give Travis github access without giving the world github access.

I would therefore go for the first option, especially because you use Rake already, so it would be easy to use the Ruby github API bindings.

from strut.

I like the idea of a rake upload task.

from strut.

The compiled coffee script and compiled templates are no longer checked in.

Closing this and making the rake upload task a separate issue.

from strut.