mardi 18 juillet 2017

Ember fingerprinting

I am new to ember and am running into an issue deploying an ember app. I am using ember server to server my ember app that was built with fingerprinting enabled.

/app/node_modules/ember-cli/bin/ember build --environment=production

When I run this in production mode, it works great, until I scale to multiple deployments.

/app/node_modules/ember-cli/bin/ember server --port 80 --live-reload=false --environment $EMBER_ENV

When I have more then one ember server instance in a load balancer, the fingerprint generated on each is different, even though they were the same build, and this causes an intermittent 404.

172.x.x.x - - [18/Jul/2017:18:44:59 +0000] "GET /assets/vendor-a4e09847ae5ed0421fd631873a322bdb.js HTTP/1.1" 404

  • Is this fingerprint generated at run time and not build time?
  • Is there any way I can make it a build time action?

Thanks so much.




Aucun commentaire:

Enregistrer un commentaire