Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

link to this from nodeschool.io #10

Open
max-mapper opened this issue Aug 21, 2014 · 9 comments
Open

link to this from nodeschool.io #10

max-mapper opened this issue Aug 21, 2014 · 9 comments

Comments

@max-mapper
Copy link

heya,

we're working on a new nodeschool website.

what do we have to do to make this production ready enough to be able to link to it from nodeschool.io?

e.g. we can try and get digital ocean to sponsor hosting, etc

@generalhenry
Copy link
Owner

  1. Get a domain
    Something like nodeschoolinteractive.io or *.nodeschool.io

It needs a wildcard subdomain to work fully.
So that could be interactive.nodeschool.io + silly_names.nodeschool.io or even
interactive.nodeshool.io + silly_names.interactive.nodeschool.io

By having each instance have it's own full subdomain I can open up ports in a nice way.

  1. Get sponsored hosting.
    It's currently on digital ocean, but all it really needs is a host that can run node and docker.

@max-mapper
Copy link
Author

nice, we can definitely get a wildcard subdomain set up for interactive.nodeschool.io

@mikeal can we get a sponsored DO account for this?

@generalhenry do you have any ideas about how many interactive sessions we can expect to host before stuff stops working? e.g. limits

@generalhenry
Copy link
Owner

Overhead per user is:

Server:
1 ws proxy connection

Container:
1 container
2 node processes (proxy + server)
1 bash process

new windows add a ws proxy and bash session

And then of course there's the load of whatever the user is running.

I'd need to do benchmarking to come up with a number. It'll likely end up either bound by memory or disk io. Even then it'll be a really fuzzy number since it doesn't simply stop working, everything just gets slow.

@max-mapper
Copy link
Author

OK cool. I think we should try adding a button to the website but not heavily promote it at first, just to test it out as a sort of beta feature.

We're going to release a new website soon, i'll work on getting all this stuff set up

@brianloveswords can we get a DNS entry for shell.nodeschool.io and *.shell.nodeschool.io ?

@rosskukulinski
Copy link

@maxogden just reaching out to see if DO is going to sponsor an account for this. Otherwise, I think Rackspace (via @kenperkins) would be interested.

@kenperkins
Copy link

Yes we can help with hosting OSS projects; just say the word.

@brianloveswords
Copy link

@maxogden did I already set up that DNS when we were in Portland or is this something different?

@kenperkins
Copy link

If you want to use Rackspace, just signup for an account on through https://developer.rackspace.com/signup and when you're in the CP, send me the account number, and we'll register it for the open source credit.

@mikeal
Copy link

mikeal commented Oct 24, 2014

DigitalOcean can also offer any hosting you need :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants