Skip to content
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.

Collab asks for c9.api #35

Closed
Program3r opened this issue Mar 18, 2015 · 23 comments
Closed

Collab asks for c9.api #35

Program3r opened this issue Mar 18, 2015 · 23 comments

Comments

@Program3r
Copy link

{ [Error: Can't find './c9.api/ping.js' relative to '/root/c9sdk/plugins'] code: 'ENOENT' }

Seems like there are still some files missing to run collab?

@isc30
Copy link

isc30 commented Mar 19, 2015

Maybe compiler failed for that file.
With node version of 0.10.36 it works fine

@nightwing
Copy link
Member

Seems like there are still some files missing to run collab?

this time there are unnecessary files instead, it should work if you delete
https://github.com/c9/core/blob/master/configs/api.standalone.js

@ClashTheBunny
Copy link

@nightwing, that works for me. Thanks!

Is this going to get merged any time soon?

@Program3r
Copy link
Author

running node v0.10.36 Without removing api.standalone.js I get

{ [Error: Can't find './c9.api/ping.js' relative to '/root/c9sdk/plugins'] code: 'ENOENT' }   

after removing I get this after loading the UI

[vfs-collab] Missing dependencies - NODE_PATH: /.nvm/v0.10.36/lib/node_modules; node v0.10.36

Cloud9 detected you are missing one or more collab dependencies. Would you like to open the installer to update to the latest version?

After pressing NO, I try to set it to PUBLIC and I get a prompt saying

The server returned an error

Please try again later.

@ClashTheBunny
Copy link

I just share the link to the page I'm on. It's "public" as the page you are viewing when collab is enabled.

If I'm on localhost:8181, and I go to hydra:8181 from another computer on the same network, we're collaborating. Since PUBLIC is about authentication, and the SDK lacks the same authentication that c9.io has, it's moot.

@nightwing
Copy link
Member

@ClashTheBunny it is merged in a822db7
@Program3r this can happen if installation of sqlite3 fails. Did you see any errors while running install-sdk.sh, if no try running cloud9 with ~/.c9/node/bin/node server.js ...

@Program3r
Copy link
Author

I noticed sqlite3 gave me the error

version `GLIBC_2.14' not found

It compiled, but I wasn't happy with that so I upgraded libc6 and the error went away.
I'm always getting this error no matter what

Shuting down a faulty collab server - reason:  { [Error: [vfs-collab] Missing dependencies

What OS are you installing on? or should it matter? - Debian Wheezy for me. Node 0.10.38

@nightwing
Copy link
Member

Strange it should have worked, do you have node_modules/pty.js and node_modules/sqlite3?
If no try running cloud9 with the node 0.12 installed by c9/install in ~/.c9 directory
something like

C9DIR="$HOME/.c9";
NODE_PATH="$C9DIR/node_modules";
"$C9DIR/node/bin/node" server.js -p 8181 -l 0.0.0.0 --collab -a :

@lijianying10
Copy link

I can not use collaborate, the IDE tell me that

[vfs-collab] Missing dependencies - NODE_PATH: /root/.c9; node v0.12.0

Cloud9 detected you are missing one or more collab dependencies. Would you like to open the installer to update to the latest version?

choose yes or no always do nothing .

I cheeked sqlite3 and pty.js is installed correctly.

NEED HELP!

@master5227
Copy link

I also am having problems.

[vfs-collab] Missing dependencies - NODE_PATH: /usr/lib/nodejs:/usr/lib/node_modules:/usr/share/javascript; node v0.10.38

Running on Ubuntu 14.10

EDIT:
I checked /usr/lib/node_modules and pty didn't exist. I ran a sudo npm install pty, and but it's still giving me the same error.

EDIT 2:
Solved. Using the install script puts node, and it's modules into ~/.c9/node and ~/.c9.node_modules respectively. I was able to get collaboration working with export NODE_PATH="/home/john/.c9/node_modules" and ~/.c9/node/bin/node server.js --listen 0.0.0.0 -p 8181 -a admin:admin --collab

@romanman
Copy link

image

@master5227 : thanks I have tried your advise and the ide started
but I got some missing plugin

@romanman
Copy link

@master5227 : have you succeeded with the --collab to work ?

@lijianying10
Copy link

@master5227 I hv solved this problem, then how can I manager account on C9 local ?

@romanman
Copy link

@lijianying10 : you see some members on the collab panel , right ?

@lijianying10
Copy link

@romanman Not some member , Just ME....

@romanman
Copy link

so what server have you installed to manage this?@lijianying10

@lijianying10
Copy link

Ubuntu server 14.04

@romanman
Copy link

@lijianying10 : sorry, I mean what have you installed except the c9 sdk , what service
actually manage the members panel?

@lijianying10
Copy link

@romanman no other service, just Env value error.
do you know how to manage user ? add a new user on local c9 IDE?

@fusspawn
Copy link

fusspawn commented May 1, 2015

Note. the missing depencies issue still seems to be happening. I tried both the bundled node 10.37 and the latest build of node v12. both have the same issue.

Tried manually installing sqllite globally via npm. to be told it was already installed via c9.io Im at a loss :/ Has anyone successfully got collab working on Ubuntu?

@nightwing
Copy link
Member

The issues were caused by mismatch between version of node used to install binary modules and to run sdk. Latest update fixes this by always using node from ~/.c9.
Please try again and let us know if it works.

@Program3r
Copy link
Author

Alright! I got the new code cloned in and whatnot. Looks like I still have to export the node path:

export NODE_PATH="$HOME/.c9/node_modules"

and I still have to remove this file

/configs/api.standalone.js

then I run it like stated above

~/.c9/node/bin/node server.js --listen 0.0.0.0 -p 80 -a admin:admin --collab

If I don't specify an auth method it seems to listen on 127.0.0.1, I'm not sure why. After that it looks like it works!

I will release a docker container with these fixes soon! Next thing we need to do is figure out how to hook it up to an auth system but that's kind of a different issue. Thanks for the help everyone!

@nightwing
Copy link
Member

@Program3r maybe something went wrong when updating, and you were testing old branch. there is no api.standalone.js file in https://github.com/c9/core/tree/master/configs

If I don't specify an auth method it seems to listen on 127.0.0.1, I'm not sure why. After that it looks like it works!

It is a security measure. If you don't want a password use -a :.

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

8 participants