librelist archives

« back to archive

Hosting BrowserQuest

Hosting BrowserQuest

From:
Aaron Hill
Date:
2013-06-19 @ 23:35
Hello,

I think that it would be nice if we had a running instance of BrowserQuest
somewhere (e.g. Heroku). While Mozilla does host it, it is, of course,
their unmaintained version.

Does anyone know of a good PAAS for BrowserQuest? I know Heroku doesn't
support WebSockets, but you can configure it to use long polling (I'm not
sure how well this ends up working).

Any thoughts?

--Aaron Hill

Re: [browserquest] Hosting BrowserQuest

From:
Justin Clift
Date:
2013-06-20 @ 00:12
On 20/06/2013, at 12:35 AM, Aaron Hill wrote:
> Hello,
> 
> I think that it would be nice if we had a running instance of 
BrowserQuest somewhere (e.g. Heroku). While Mozilla does host it, it is, 
of course, their unmaintained version.
> 
> Does anyone know of a good PAAS for BrowserQuest? I know Heroku doesn't 
support WebSockets, but you can configure it to use long polling (I'm not 
sure how well this ends up working).
> 
> Any thoughts?

Pretty sure that it'll run on OpenShift. :)

Tom McKay (CC'd) got it up and running a while back before
OpenShift supported WebSockets, so might have good input
here.

Since then, I think OpenShift has added some sort of WebSockets
support, so it might "just work".  No idea for sure.

Note, I'm mentioning OpenShift as a first preference because
I work for Red Hat (who is also behind OpenShift).

But, if it turns out not to run well there, I don't really have
a problem with running it somewhere else.

Does that help?

Regards and best wishes,

Justin Clift

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift

Re: [browserquest] Hosting BrowserQuest

From:
Aaron Hill
Date:
2013-06-20 @ 00:21
Thanks! This looks great!

--Aaron Hill


On Wed, Jun 19, 2013 at 8:12 PM, Justin Clift <jclift@redhat.com> wrote:

> On 20/06/2013, at 12:35 AM, Aaron Hill wrote:
> > Hello,
> >
> > I think that it would be nice if we had a running instance of
> BrowserQuest somewhere (e.g. Heroku). While Mozilla does host it, it is, of
> course, their unmaintained version.
> >
> > Does anyone know of a good PAAS for BrowserQuest? I know Heroku doesn't
> support WebSockets, but you can configure it to use long polling (I'm not
> sure how well this ends up working).
> >
> > Any thoughts?
>
> Pretty sure that it'll run on OpenShift. :)
>
> Tom McKay (CC'd) got it up and running a while back before
> OpenShift supported WebSockets, so might have good input
> here.
>
> Since then, I think OpenShift has added some sort of WebSockets
> support, so it might "just work".  No idea for sure.
>
> Note, I'm mentioning OpenShift as a first preference because
> I work for Red Hat (who is also behind OpenShift).
>
> But, if it turns out not to run well there, I don't really have
> a problem with running it somewhere else.
>
> Does that help?
>
> Regards and best wishes,
>
> Justin Clift
>
> --
> Open Source and Standards @ Red Hat
>
> twitter.com/realjustinclift
>
>

Re: [browserquest] Hosting BrowserQuest

From:
Justin Clift
Date:
2013-06-21 @ 18:54
I've been chatting with Wesley Hearn, who works on the OpenShift team
here at Red Hat.

He did an initial port of BQ to work on OpenShift at the start of this
year, based on the original Moz code dump.  He had to fairly radically
change stuff around, because the original Moz code didn't serve the
client JS/HTML through node... it needed a separate http server.

We're kind of suspecting that our repo might "just work" on OpenShift,
if someone has time to try it.

OpenShift even has support for Redis (there's a Redis "Cartridge"
for OpenShift).  So, really no obvious blockers. :)

Is anyone interested in trying to get it up and running? :)

Regards and best wishes,

Justin Clift


On 20/06/2013, at 1:21 AM, Aaron Hill wrote:
> Thanks! This looks great!
> 
> --Aaron Hill
> 
> 
> On Wed, Jun 19, 2013 at 8:12 PM, Justin Clift <jclift@redhat.com> wrote:
> On 20/06/2013, at 12:35 AM, Aaron Hill wrote:
> > Hello,
> >
> > I think that it would be nice if we had a running instance of 
BrowserQuest somewhere (e.g. Heroku). While Mozilla does host it, it is, 
of course, their unmaintained version.
> >
> > Does anyone know of a good PAAS for BrowserQuest? I know Heroku 
doesn't support WebSockets, but you can configure it to use long polling 
(I'm not sure how well this ends up working).
> >
> > Any thoughts?
> 
> Pretty sure that it'll run on OpenShift. :)
> 
> Tom McKay (CC'd) got it up and running a while back before
> OpenShift supported WebSockets, so might have good input
> here.
> 
> Since then, I think OpenShift has added some sort of WebSockets
> support, so it might "just work".  No idea for sure.
> 
> Note, I'm mentioning OpenShift as a first preference because
> I work for Red Hat (who is also behind OpenShift).
> 
> But, if it turns out not to run well there, I don't really have
> a problem with running it somewhere else.
> 
> Does that help?
> 
> Regards and best wishes,
> 
> Justin Clift
> 
> --
> Open Source and Standards @ Red Hat
> 
> twitter.com/realjustinclift
> 
> 

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift

Re: [browserquest] Hosting BrowserQuest

From:
Aaron Hill
Date:
2013-06-23 @ 18:29
I've successfully gotten BrowserQuest up and running on Openshift here:
http://browserquest-aaron1011.rhcloud.com:8000/

Note that port 8000 is necessary: Openshift only has websocket support on
port 8000, not 80.
You can look at the code on the "production" branch of my repo here:
https://github.com/Aaron1011/BrowserQuest/tree/production.

If this looks good, I can squash the commits into one.

--Aaron Hill


On Fri, Jun 21, 2013 at 2:54 PM, Justin Clift <jclift@redhat.com> wrote:

> I've been chatting with Wesley Hearn, who works on the OpenShift team
> here at Red Hat.
>
> He did an initial port of BQ to work on OpenShift at the start of this
> year, based on the original Moz code dump.  He had to fairly radically
> change stuff around, because the original Moz code didn't serve the
> client JS/HTML through node... it needed a separate http server.
>
> We're kind of suspecting that our repo might "just work" on OpenShift,
> if someone has time to try it.
>
> OpenShift even has support for Redis (there's a Redis "Cartridge"
> for OpenShift).  So, really no obvious blockers. :)
>
> Is anyone interested in trying to get it up and running? :)
>
> Regards and best wishes,
>
> Justin Clift
>
>
> On 20/06/2013, at 1:21 AM, Aaron Hill wrote:
> > Thanks! This looks great!
> >
> > --Aaron Hill
> >
> >
> > On Wed, Jun 19, 2013 at 8:12 PM, Justin Clift <jclift@redhat.com> wrote:
> > On 20/06/2013, at 12:35 AM, Aaron Hill wrote:
> > > Hello,
> > >
> > > I think that it would be nice if we had a running instance of
> BrowserQuest somewhere (e.g. Heroku). While Mozilla does host it, it is, of
> course, their unmaintained version.
> > >
> > > Does anyone know of a good PAAS for BrowserQuest? I know Heroku
> doesn't support WebSockets, but you can configure it to use long polling
> (I'm not sure how well this ends up working).
> > >
> > > Any thoughts?
> >
> > Pretty sure that it'll run on OpenShift. :)
> >
> > Tom McKay (CC'd) got it up and running a while back before
> > OpenShift supported WebSockets, so might have good input
> > here.
> >
> > Since then, I think OpenShift has added some sort of WebSockets
> > support, so it might "just work".  No idea for sure.
> >
> > Note, I'm mentioning OpenShift as a first preference because
> > I work for Red Hat (who is also behind OpenShift).
> >
> > But, if it turns out not to run well there, I don't really have
> > a problem with running it somewhere else.
> >
> > Does that help?
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> > --
> > Open Source and Standards @ Red Hat
> >
> > twitter.com/realjustinclift
> >
> >
>
> --
> Open Source and Standards @ Red Hat
>
> twitter.com/realjustinclift
>
>

Re: [browserquest] Hosting BrowserQuest

From:
Justin Clift
Date:
2013-06-24 @ 02:14
On 23/06/2013, at 7:29 PM, Aaron Hill wrote:
> I've successfully gotten BrowserQuest up and running on Openshift here: 
http://browserquest-aaron1011.rhcloud.com:8000/

Excellent stuff there!  Tried it, and it's working well.  Nicely, I
don't have the problem creating usernames with "a" or "f" in them on
that instance. :)


> Note that port 8000 is necessary: Openshift only has websocket support 
on port 8000, not 80. 
> You can look at the code on the "production" branch of my repo here: 
https://github.com/Aaron1011/BrowserQuest/tree/production.
> 
> If this looks good, I can squash the commits into one.

Looks good.  Tried out the production branch locally here too, and it's
working fine.  So, the same code base will now run both locally and in
OpenShift with no changes.  That's definitely what we want. :)

Made a few tiny comments through your production branch commits.  The
only (super nit picky) change needed is on one line where the
indentation is out of whack.  Everything else looks good.

So, definitely go ahead and squash the commits, then open a PR.  Feel
free to merge the PR yourself too if you want.  Having the PR there
(for larger important bits of work) gives us a reference point for
later if we need it, and helps with our stats. :)

+ Justin


> --Aaron Hill
> 
> 
> On Fri, Jun 21, 2013 at 2:54 PM, Justin Clift <jclift@redhat.com> wrote:
> I've been chatting with Wesley Hearn, who works on the OpenShift team
> here at Red Hat.
> 
> He did an initial port of BQ to work on OpenShift at the start of this
> year, based on the original Moz code dump.  He had to fairly radically
> change stuff around, because the original Moz code didn't serve the
> client JS/HTML through node... it needed a separate http server.
> 
> We're kind of suspecting that our repo might "just work" on OpenShift,
> if someone has time to try it.
> 
> OpenShift even has support for Redis (there's a Redis "Cartridge"
> for OpenShift).  So, really no obvious blockers. :)
> 
> Is anyone interested in trying to get it up and running? :)
> 
> Regards and best wishes,
> 
> Justin Clift
> 
> 
> On 20/06/2013, at 1:21 AM, Aaron Hill wrote:
> > Thanks! This looks great!
> >
> > --Aaron Hill
> >
> >
> > On Wed, Jun 19, 2013 at 8:12 PM, Justin Clift <jclift@redhat.com> wrote:
> > On 20/06/2013, at 12:35 AM, Aaron Hill wrote:
> > > Hello,
> > >
> > > I think that it would be nice if we had a running instance of 
BrowserQuest somewhere (e.g. Heroku). While Mozilla does host it, it is, 
of course, their unmaintained version.
> > >
> > > Does anyone know of a good PAAS for BrowserQuest? I know Heroku 
doesn't support WebSockets, but you can configure it to use long polling 
(I'm not sure how well this ends up working).
> > >
> > > Any thoughts?
> >
> > Pretty sure that it'll run on OpenShift. :)
> >
> > Tom McKay (CC'd) got it up and running a while back before
> > OpenShift supported WebSockets, so might have good input
> > here.
> >
> > Since then, I think OpenShift has added some sort of WebSockets
> > support, so it might "just work".  No idea for sure.
> >
> > Note, I'm mentioning OpenShift as a first preference because
> > I work for Red Hat (who is also behind OpenShift).
> >
> > But, if it turns out not to run well there, I don't really have
> > a problem with running it somewhere else.
> >
> > Does that help?
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> > --
> > Open Source and Standards @ Red Hat
> >
> > twitter.com/realjustinclift
> >
> >
> 
> --
> Open Source and Standards @ Red Hat
> 
> twitter.com/realjustinclift
> 
> 

--
Open Source and Standards @ Red Hat

twitter.com/realjustinclift