Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

dev.sh and codegen #2

Open
joeblew99 opened this issue Apr 29, 2017 · 1 comment
Open

dev.sh and codegen #2

joeblew99 opened this issue Apr 29, 2017 · 1 comment

Comments

@joeblew99
Copy link

At the moment it does not watch for changes and then codegen ?

For example new assets etc.

This might be interesting for you..
https://github.com/tockins/realize
It can watch and codegen etc.

i am planning to try to match it up with some of your stuff.

what do you think ?

@deankarn
Copy link
Contributor

@joeblew99 I tried realize a while back and I'm sure it's more mature now it was way too verbose and why I created justdoit in the first place; one that just works.

The way I have it configured is different than most and I find this way more beneficial.

justdoit - watches for file changes that require a recompile
livereload - allows you to add, and modify assets and automatically see changes in the browser without needing to recompile nor wait for a recompile which can take time due to embedding assets.

my statics package is used and when in debug mode reads from DISK and production mode the embedded(codegen) assets after running go generate

I find that this also works better when a more complicated pipeline exists eg. using SASS or LESS and needing to compile down to CSS prior to doing anything else.

It also saves allot of waiting and wasted CPU cycles I mean codegen and recompiling just because I changed a .js or .css file.

I have no problem with you trying to match it up with my stuff though 😄 I just may keep that in another branch for people to choose which they'd prefer 👍

PS. if you also want godegen one only has to modify the justdoit -build argument to say run a script that runs codegen and then recompiles.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants