You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
long answer: each c9 server process is limited to a single user, but you can theoretically start multiple server processes for multiple users. that would mean each user would have a different url (port) (or you could have a reverse-proxy map the same url to the correct c9 server process based on any sort of authentication you chose.)
it is unclear to me how to differentiate the usernames and user ids for each c9 process in such a scenario though. some hints from c9 staff would be appreciated.
in particular, there seems to be a user config in settings/standalone.js and then some other seemingly unrelated one in plugins/c9.vfs.standalone/standalone.js and it's not clear which needs to be changed. also to make it different for each user, it would be more convenient if it were actually loaded from ~/.c9/ ...
lastly, for more convenient and secure reverse-proxy setup it would be good if c9 processes were not listening on a tcp port but on a unix socket... but that's really a whole separate issue
how to register a new user on local c9 cloud system?
The text was updated successfully, but these errors were encountered: