4 ms·

Really? Last time I tried it, it was a git clone and executing one, maybe two commands. I've seen very early unix beginners get it running quickly... sudo

Really? Last time I tried it, it was a git clone and executing one, maybe two commands. I've seen very early unix beginners get it running quickly... sudo apt-get install libssl0.9.8 git clone https://github.com/ajaxorg/cloud9.git cloud9 ./cloud9/bin/cloud9.sh (roughly) Yep, just tried in a clear dir, it's up and running with that alone.

poink 15y ago
I've never used Cloud9 before, but that just worked for me on a Xubuntu VM. As a Vim fanboy, I'll be giving it a shot.
maratd 15y ago
Ok. Let's try that: support/node-builds-v4/node-linux64: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory Wait, what? Ahh, I have a newer version installed and it really wants the old 0.9.8. Let's fake the links and see what happens: ./cloud9/bin/cloud9.sh: line 11: 23557 Segmentation fault support/node-builds-v4/node-linux64 bin/cloud9.js "$@" -a x-www-browser Not good. Maybe I can try the node already installed on my system instead of the bundled binaries? Sure, let's try that: Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead. Right. Because it's not compatible with the latest stable version of NodeJS, which is 0.6 ... that's what the guy was talking about. Unless you want to setup a box with the exact dependencies that it needs and use it only for that, it'll be a real pain.
- krmmalik 15y ago
  Yep - That last error is the real problem i've had each time.
- drivebyacct2 15y ago
  Okay, I didn't know my node was a version behind, but are you really telling me checking out node.js into another directory and building it is a "real pain"? Maybe beta quality open source software isn't something I'd recommend to you then.
  - maratd 15y ago
    > Maybe beta quality open source software isn't something I'd recommend to you then. Beta grade software isn't something I would recommend to anyone for the purposes of writing production code. That doesn't mean it's not for everyone, but it's certainly not for me.
    - drivebyacct2 15y ago
      What? Now you're just playing word games to make me sound unreasonable. Unless you're implying that Cloud9 is going to hack my GitHub account and somehow wipe out my repository, I see no problem whatsoever using a beta text editor to write code. It's not like the "beta" aspect of the editor is going to slip in some weird bug into the code I'm writing while I'm not looking.
krmmalik 15y ago
"Error. require.paths is removed" is what i get even when i follow your instructions exact. I had the same problem on Linux but im on Windows now. I dont think this is a Windows problem though? Something with the way i have things configured maybe? PS. I used Win-Git for the git clone

poink 15y ago

I've never used Cloud9 before, but that just worked for me on a Xubuntu VM. As a Vim fanboy, I'll be giving it a shot.

maratd 15y ago

Ok. Let's try that: support/node-builds-v4/node-linux64: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory Wait, what? Ahh, I have a newer version installed and it really wants the old 0.9.8. Let's fake the links and see what happens: ./cloud9/bin/cloud9.sh: line 11: 23557 Segmentation fault support/node-builds-v4/node-linux64 bin/cloud9.js "$@" -a x-www-browser Not good. Maybe I can try the node already installed on my system instead of the bundled binaries? Sure, let's try that: Error: require.paths is removed. Use node_modules folders, or the NODE_PATH environment variable instead. Right. Because it's not compatible with the latest stable version of NodeJS, which is 0.6 ... that's what the guy was talking about. Unless you want to setup a box with the exact dependencies that it needs and use it only for that, it'll be a real pain.

krmmalik 15y ago
Yep - That last error is the real problem i've had each time.
drivebyacct2 15y ago
Okay, I didn't know my node was a version behind, but are you really telling me checking out node.js into another directory and building it is a "real pain"? Maybe beta quality open source software isn't something I'd recommend to you then.
- maratd 15y ago
  > Maybe beta quality open source software isn't something I'd recommend to you then. Beta grade software isn't something I would recommend to anyone for the purposes of writing production code. That doesn't mean it's not for everyone, but it's certainly not for me.
  - drivebyacct2 15y ago
    What? Now you're just playing word games to make me sound unreasonable. Unless you're implying that Cloud9 is going to hack my GitHub account and somehow wipe out my repository, I see no problem whatsoever using a beta text editor to write code. It's not like the "beta" aspect of the editor is going to slip in some weird bug into the code I'm writing while I'm not looking.

krmmalik 15y ago

"Error. require.paths is removed" is what i get even when i follow your instructions exact. I had the same problem on Linux but im on Windows now. I dont think this is a Windows problem though? Something with the way i have things configured maybe? PS. I used Win-Git for the git clone