The Road to 1.0 #98

tomdale · 2016-01-27T22:54:45Z

danmcclain · 2016-01-27T23:05:49Z

What about appending requested host to absolute paths in ajax requests

tomdale · 2016-01-27T23:16:11Z

taveras · 2016-01-29T19:42:20Z

How about being able to control over the /robots.txt response served from fastboot?

tomdale · 2016-01-30T12:35:50Z

@taveras It's just an Express middleware, so you can add your own handling for arbitrary endpoints. We should try not to let FastBoot turn into a generic HTTP server.

tomdale · 2016-02-03T19:04:11Z

Per this week's meeting:

@ronco is working on adding support for head.hbs to render <head> elements
@rwjblue is working on a change to Ember CLI so that config is written to a JSON file
@cibernox is updating his addon to work in FastBoot and collecting a list of pain points for dual testing an addon in both scenarios
@tomdale will work on exposing the Express request as FastBoot.request
@RuslanZavacky is investigating getting good performance out of the Googlebot and is working on a PR that allows disabling <script> tags from FastBoot's HTML page.

jpadilla · 2016-02-03T19:40:06Z

I also started working on #99 😃

tomdale · 2016-02-03T20:29:11Z

If you're interested in helping out, join us in #fastboot in the Ember community Slack.

sebyx07 · 2016-02-04T10:19:53Z

it would also be nice at first to have cache headers in the response

ember fastboot --cache-headers 15000

before we have better access to headers

tomdale · 2016-02-04T12:40:49Z

@sebyx07 It's just an Express middleware, you can add whatever headers you want.

MiguelMadero · 2016-03-17T02:48:23Z

@tomdale what about "hydrating" or making the fastboot app into a normal emberApp after everything is loaded?

danmcclain · 2016-03-17T02:50:03Z

@MiguelMadero I think that hydrating is blocked until Glimmer 2.0 lands, I'll let someone else confirm

tomdale · 2016-03-21T15:30:21Z

@MiguelMadero @danmcclain Confirmed

MiguelMadero · 2016-03-23T19:39:42Z

Thanks for clarifying.

danmcclain · 2016-03-24T12:16:55Z

Support multi-stage (browser → FastBoot) build with asset rewriting, so FastBoot index.html points at browser build, not FastBoot build

@tomdale Your latest PR achieves this, right?

tomdale · 2016-03-26T18:07:23Z

@danmcclain Confirm, good catch!

coladarci · 2016-04-03T16:16:06Z

Wow - when this is finished, Ember will really be able to DoItAll™️!
Realllllly want to start a new project w/ fastboot but am scared that w/out Hydration landing relatively soon, it won't be the right decision and we might be left in a tough spot. Any ballpark ideas of when hydration will be added? I looked for a Glimmer 2.0 roadmap and couldn't find one.. Thanks for all the work on this - really a game-changer for Ember.

hhff · 2016-04-03T17:06:18Z

@coladarci - I think it's a safe bet - while fastboot doesn't technically 'rehydrate', it does 'redraw' the application once the browser JS payload hits. It kinda clicks into place. Works really well for the most part 👍

coladarci · 2016-04-04T15:32:35Z

Yeah I noticed that, which is great. That said, that means for ~1.5s the actions on the page don't do anything, which is a bit of a blocker for my application :) I'd love to know where to follow the Glimmer 2.0 progress so I can get a rough idea of the blockers and how actively they are being addressed. We'll probably use ember for the new project w/out fastboot but checking it along the way to make sure there are no surprises, then hope we can flip it on before the launch.. I was thinking about a hybrid model where I remove a body class w/ the booted ember app so I can sort of gray out the body until the app is fully loaded; will give the end user immediate feedback and excitement but not render a bunch of busted actions for an awkward few seconds.

tomdale · 2016-04-04T16:30:46Z

@coladarci Yeah, one thing I'd like to do is automatically add an ember-fastboot class name to the <body> that gets removed once the app boots up. That would allow people to easily style interactive elements as disabled until the JavaScript has finished booting.

Cryrivers · 2016-04-04T17:10:29Z

@tomdale So 'hydrating' feature will come with Fastboot 1.0 and Ember 2.7?

tomdale · 2016-04-04T18:47:52Z

@Cryrivers I suspect it will not be in by FastBoot 1.0, but it's largely gated on Glimmer 2 work.

oligriffiths · 2016-08-23T20:58:33Z

@tomdale Am I right in thinking, according to the checklist above, that fastboot is essentially code ready, but needs the associated docs, website, watch, etc, sorting out?

tomdale · 2016-09-05T16:41:50Z

@oligriffiths Yes, we are very close. The last thing gating a 1.0 release is some performance improvements to the build process. After a lot of core team discussion, people were hesitant about the almost-doubling of build times that installing FastBoot adds to the boot process.

@stefanpenner had some great ideas for how we can avoid the extra cost, and I'm hopeful we can get those implemented soon. They will also clean up some of the monkeypatches to Ember CLI internals we have to do at the moment, and should address other usability concerns like #246.

stefanpenner · 2016-10-07T17:16:19Z

@stefanpenner had some great ideas for how we can avoid the extra cost, and I'm hopeful we can get those implemented soon. They will also clean up some of the monkeypatches to Ember CLI internals we have to do at the moment, and should address other usability concerns like #246.

related: #264 (comment)

kratiahuja · 2016-10-18T07:25:43Z

@tomdale Here is an RFC that Stef and I worked on for fixing the fastboot builds. I would prefer to hold up 1.0 release until this is fixed since this a fully backward incompatible change to current fastboot ergonomics. If we don't hold, we will need to jump to Fastboot 2.0 and the experience may not be good.

I will be working 100% of my time on that RFC and some other fastboot OSS stuff so I can get this out soon enough.

simonihmig · 2017-02-22T17:23:25Z

Could we get an update on what is still blocking a 1.0 release?

I guess #356 is the major blocker here, which is hopefully landing soon, anything else that is not listed in the above to do list?

From that list, I think several items have not been updated yet...

Website Updates

Those things seem to have been addressed already, at least in some form. Anything missing there? Can help if needed...

Verify Node 0.12 compatibility

This can be dropped, right?

kratiahuja · 2017-02-22T19:52:07Z

there is one more item: fixing this issue #264 . There is a solution to address this and @leitsubomi is going to look at implementing it.

fotinakis · 2017-02-25T19:54:56Z

I'm curious, is there a security evaluation/penetration testing planned for fastboot v1? Has anyone attempted to break it?

I'm very excited about fastboot, just as a user I'm concerned about understanding the security implications of moving from a purely static-file serving production environment (which is relatively easy to serve and secure) to one where user requests will interact with a full dynamic server environment with node + middleware, which of course comes with a completely different security footprint.

shahkashani · 2017-03-20T17:09:45Z

Any word on whether rehydration will make it into 1.0, now that Glimmer 2.0 is out?

danmcclain · 2017-03-23T15:37:46Z

#360 supersedes this issue, closing this as it is no longer up to date.

Rehydration is not currently a 1.0 blocker, but that doesn't prevent it from landing during the 1.0 series

ghost · 2017-09-18T14:53:07Z

@danmcclain I haven't been able to find any information with how ember + fastboot deals with rehydration. Does the app just rerender from scratch in the background and replace the existing dom?

danmcclain · 2017-09-18T15:03:01Z

@citizenconn Rehydration has yet to be implemented, so it has to rerender the app from scratch (or some from the shoebox) then replace the dom

tomdale added this to the FastBoot 1.0 milestone Jan 27, 2016

bcardarella mentioned this issue Jan 12, 2017

Testing story #333

Closed

danmcclain closed this as completed Mar 23, 2017

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

The Road to 1.0 #98

The Road to 1.0 #98

tomdale commented Jan 27, 2016 •

edited

Loading

danmcclain commented Jan 27, 2016

tomdale commented Jan 27, 2016

taveras commented Jan 29, 2016

tomdale commented Jan 30, 2016

tomdale commented Feb 3, 2016

jpadilla commented Feb 3, 2016

tomdale commented Feb 3, 2016

sebyx07 commented Feb 4, 2016

tomdale commented Feb 4, 2016

MiguelMadero commented Mar 17, 2016

danmcclain commented Mar 17, 2016

tomdale commented Mar 21, 2016

MiguelMadero commented Mar 23, 2016

danmcclain commented Mar 24, 2016

tomdale commented Mar 26, 2016

coladarci commented Apr 3, 2016

hhff commented Apr 3, 2016

coladarci commented Apr 4, 2016

tomdale commented Apr 4, 2016

Cryrivers commented Apr 4, 2016

tomdale commented Apr 4, 2016

oligriffiths commented Aug 23, 2016

tomdale commented Sep 5, 2016

stefanpenner commented Oct 7, 2016

kratiahuja commented Oct 18, 2016

simonihmig commented Feb 22, 2017

kratiahuja commented Feb 22, 2017

fotinakis commented Feb 25, 2017

shahkashani commented Mar 20, 2017

danmcclain commented Mar 23, 2017

ghost commented Sep 18, 2017

danmcclain commented Sep 18, 2017

The Road to 1.0 #98

The Road to 1.0 #98

Comments

tomdale commented Jan 27, 2016 • edited Loading

Release Plan

Nice to Have

danmcclain commented Jan 27, 2016

tomdale commented Jan 27, 2016

taveras commented Jan 29, 2016

tomdale commented Jan 30, 2016

tomdale commented Feb 3, 2016

jpadilla commented Feb 3, 2016

tomdale commented Feb 3, 2016

sebyx07 commented Feb 4, 2016

tomdale commented Feb 4, 2016

MiguelMadero commented Mar 17, 2016

danmcclain commented Mar 17, 2016

tomdale commented Mar 21, 2016

MiguelMadero commented Mar 23, 2016

danmcclain commented Mar 24, 2016

tomdale commented Mar 26, 2016

coladarci commented Apr 3, 2016

hhff commented Apr 3, 2016

coladarci commented Apr 4, 2016

tomdale commented Apr 4, 2016

Cryrivers commented Apr 4, 2016

tomdale commented Apr 4, 2016

oligriffiths commented Aug 23, 2016

tomdale commented Sep 5, 2016

stefanpenner commented Oct 7, 2016

kratiahuja commented Oct 18, 2016

simonihmig commented Feb 22, 2017

kratiahuja commented Feb 22, 2017

fotinakis commented Feb 25, 2017

shahkashani commented Mar 20, 2017

danmcclain commented Mar 23, 2017

ghost commented Sep 18, 2017

danmcclain commented Sep 18, 2017

tomdale commented Jan 27, 2016 •

edited

Loading