being able to push client files without restarting the app

[louissmit]

"jitsu deploy" currently always restarts the app. You should be able to update your client files without restarting the app.

[mmalecki]

Not sure if that's even possible without monkey-patching node module system
and that's something we definitely want to avoid.
Does your app take so long to start or do you store things in memory?

Also, maybe jitsu apps update is what you're looking for?

-- Maciej Maecki
18-11-2011 14:05 uytkownik "louissmit" <
reply@reply.github.com>
napisa:

"jitsu deploy" currently always restarts the app. You should be able to
update your client files without restarting the app.

---

Reply to this email directly or view it on GitHub:
#122

[Marak]

He wants to upload files that change the source of the application, without restarting the process.

[louissmit]

yeah, anything in /public. What does 'jitsu apps update' do?

[Marak]

jitsu apps update is for updating configuration information about the application, like fields stored in the package.json ( subdomain, etc )

I'm going to have to say that hot-loading code is generally a bad idea and bad application design. jitsu isn't going to natively support this anytime soon.

If there is a generic way to expose this functionality ( through a user-land module ), I'll consider adding support for the feature.

[louissmit]

I'm not talking about hot-loading server code. Just updating the static files your app serves (js, css etc.). That shouldn't require a back-end restart & I don't think that's bad application design.

[Marak]

I was referring only to hot-reloading actual node code.

If there are changes to the contents of your application, it will require a restart. We have no way of knowing if you are trying to modify static assets or node.js code. If anything, this will become a non-issue when we have zero-downtime deploys working.

If you have a lot of static assets, you should be using a cloud storage file-system and linking your application to that.

[louissmit]

Zero-downtime deploys would solve the problem. However, it would create some unnecessary overhead when you're just need to push a simple CSS fix.
So, out of curiosity, the Nodejitsu API doesn't allow to just do like a 'git push' to your instance? That way your new static assets would be used immediately but your node code will only be used on restart.

[Marak]

Your application isn't bound to any one specific server.

When new code is pushed, it's pushed to a new machine ( usually ), which means the old version of the application needs to be stopped, and the new one needs to be started.

[louissmit]

Understood! Thanks.