Moving Cozy from Node 0.8 to Node 0.10

[Frank Rousseau]

Hi all,

  This week we are going to change the version of the biggest dependency of Cozy: Node.js.

We are going to merge code that is only compatible with version of Node.js superior to 0.10. For existing installation it doesn't change anything until you run an update. We'll provide very soon details on how to upgrade your Cozy instance to Node 0.10.

If you experience problems while making a fresh installation of Cozy, notify us and we'll debug installation script as soon as possible. About images. we'll update them all this week.

Once we'll be done, the 0.10.26 version of Node.js will be the reference version for Cozy.

Regards,

Frank

[Frank Rousseau]

Hi again,

Update is complete. You can find details in this blog post about how to upgrade your existing installation of Cozy.
http://blog.cozycloud.cc/news/2014/04/17/move-from-node08-to-node010/

If you meet any problems, answer to this thread. It will provide additional information for other Cozy users.

Frank

[B]

Hi,

Congratz on the update!
I hit a few issues when updating:
- On your blog post, the manual list of commands says at some point to do "cozy-monitor cozy-stack", the actual command is "cozy-monitor update-cozy-stack".
- Using the fab script fails locally for me:

[ubuntu@localhost] sudo: pkill node
[ubuntu@localhost] out: sudo password:
[ubuntu@localhost] out:
Fatal error: sudo() received nonzero return code 1 while executing!

This happens as pkill can't find any node process, so this isn't really an error.
- When commenting the pkill node command in the fabfile, I still get an error:

[ubuntu@localhost] out: Update data-system...
[ubuntu@localhost] out: Update failed
[ubuntu@localhost] out: An error occured.
[ubuntu@localhost] out: Cannot update application that is not running.
[ubuntu@localhost] out: undefined
[ubuntu@localhost] out: undefined
[ubuntu@localhost] out: undefined
[ubuntu@localhost] out:

When starting manually the data-system app, it seems that the node_modules aren't reinstalled (they were deleted before during the upgrade process).

I don't have more time to diagnostic and find workarounds now, but plan to do so later if nobody beats me to it :)
Cheers!
Benjamin (:bnj)