@Lupestro wrote:
I have a set of Ember client apps that will sit in directories served by IIS. Each one will be deployed as a website in IIS terms, although deployment of new versions is fundamentally no more than a file copy. I have a Web.config that will allow me to rewrite our /api requests to go to our API server. If Fastboot is running, it should be able to do a redirect to Fastboot as well to deliver our index.html as well.
What is the best way to integrate FastBoot into this environment?
Do we run a single FastBoot server running under Node providing pages for all the apps? Or do we run one per website - (one extra process per app)?
Can we tie initiation and shutdown of those processes with the lifecycle of the IIS website, so the admins remotely controlling the site through IIS don’t have to do anything special?
Is the code in our dist area sufficient to invoke directly from node to run the fastboot-app-server? Or does fastboot-app-server have to be installed separately in its own area? (What localhost:4200 does behind the scenes is kind of a black box to me. I’m really happy it works for development.)
I want to get a protoype scenario running so I can schedule a meeting with our ops guys to figure out what is feasible on our site.
Beyond this, I haven’t even scratched the surface of what this means in the context of Akamai and Alteon fronting our site. That’s a whole other kettle of fish, but I could use advice on that, too, so I can at least talk intelligently with our ops guys.
Thanks…
Posts: 1
Participants: 1