The URL is very similar but notice how the subdomain differs. The outer Cloud9 runs on (ide.)cloud9-lennartcl.c9.io. It responds on that URL and on *.cloud9-lennartcl.c9.io. That's where the inner Cloud9 runs: (ide.)cloud9-lennartcl.cloud9-lennartcl.c9.io. Visit that URL and you actually go through 3 proxies: the production proxy of c9.io and those of two inner instances. And note that the user names look the same in this case in this case, but that's really just for symmetry; ide.cloud9-2-lennartcl-2.cloud9-lennartcl.c9.io would have looked too awkward :) Each instance can have its own database with user names and workspaces. And each workspace runs in its own container.
Comments
Great article, it's good to hear about IDE companies dogfooding and using that to improve their product.
I don't want to call you out but in https://c9.io/blog/content/images/2015/07/recursion.png you're really only running C9 in C9 - the rest have the same URL.
The URL is very similar but notice how the subdomain differs. The outer Cloud9 runs on (ide.)cloud9-lennartcl.c9.io. It responds on that URL and on *.cloud9-lennartcl.c9.io. That's where the inner Cloud9 runs: (ide.)cloud9-lennartcl.cloud9-lennartcl.c9.io. Visit that URL and you actually go through 3 proxies: the production proxy of c9.io and those of two inner instances. And note that the user names look the same in this case in this case, but that's really just for symmetry; ide.cloud9-2-lennartcl-2.cloud9-lennartcl.c9.io would have looked too awkward :) Each instance can have its own database with user names and workspaces. And each workspace runs in its own container.