Open copongcopong opened 13 years ago
yup, right now only attachment changes are picked up, working on better sync support.
looking forward to better sync. sometime soon. :)
@boxxxie monitoring changes to app.js
would involve some child process spawning hackery. Is that the only thing you'd like the sync code to do that it isn't currently doing?
I feel that the major use case for the sync
command is to sync your client side code between your filesystem and couch, since thats where you spend the majority of your development time when writing couchapps. If you have a different opinion I'd love to hear your feedback.
Thanks,
Max
Actually, we could do it , it would just be kind of difficult.
We could require.uncached() the module and blow away all the state from before, but we would need to also kill all the file watches and other stuff.
-Mikeal
On Aug 31, 2011, at August 31, 201110:17 AM, maxogden wrote:
@boxxxie monitoring changes to
app.js
would involve some child process spawning hackery. Is that the only thing you'd like the sync code to do that it isn't currently doing?I feel that the major use case for the
sync
command is to sync your client side code between your filesystem and couch, since thats where you spend the majority of your development time when writing couchapps. If you have a different opinion I'd love to hear your feedback.Thanks,
Max
Reply to this email directly or view it on GitHub: https://github.com/mikeal/node.couchapp.js/issues/6#issuecomment-1959587
A bit of a hijack here.:) You might want to give reupholster a try. It supports most of the node.couchapp.js format and it will monitor changes to app.js
http://reupholster.iriscouch.com/reupholster/_design/app/index.html
This has my vote. Really annoying to manually do a push especially when comming from reupholster
using "sync", changing/editing existing files (e.g. app.js) doesn't appear to be detected and changes were not sync. I am using mac os x using node 0.4.0. Issue with watch? (maybe)