gulp serve:dist errors out about ioweb2016 HOT 7 CLOSED

I've been wondering whether this app actually needs a GAE server at this point: no templates, everything's moving to firebase, right.

Unless I missed something?

from ioweb2016.

FB isn't decided yet.

#22 only removes template partials for individual pages (the ajax system). We still need a server for parts of the app, including templates in general.

I personally trust GAE's reliability and scaling more than other cloud products. Is there a reason not to stick with it?

from ioweb2016.

Oh no, sorry I meant during local development: if you only had a static site, GAE dev server would seem like an overkill. Otherwise, yeah, I agree, deployment to prod is a different story.

When is FB decided? :)

from ioweb2016.

Oh! Yea, I never use GAE locally. Just gulp serve, which runs the standalone server.

We should chat about FB today. Shailen was gone all last week :\

from ioweb2016.

I'm not sure I can make it :(
Need to catch a train at 6.30pm today, which exactly when the weekly starts
in my timezone.
But I guess we can chat some other time, one of the next days.

On 25 January 2016 at 16:51, Eric Bidelman [email protected] wrote:

Oh! Yea, I never use GAE locally. Just gulp serve, which runs the
standalone server.

We should chat about FB today. Shailen was gone all last week :\

—
Reply to this email directly or view it on GitHub
#30 (comment)
.

from ioweb2016.

@crhym3, looks like this is b/c we need to fix the SDK at:

gcloud config set component_manager/fixed_sdk_version 0.9.55
gcloud components update -q

bckenny was able to build fine since he was still on it all the way from last year! I have an up to date SDK. What can we do?

from ioweb2016.

Right. That's one way of fixing it but it's rather a workaround.

gcloud, especially for golang, now recommends (again!) using good old dev_appserver. I'll be updating README and gulpfile soon.

from ioweb2016.