deploy:index but forgot to build first

[jbrown]

Then you're stuck. 😳

Version for key [e105df69ae] has already been uploaded

[zpatten]

👍 having a similar issue where even when my files under dist are changing, it keeps wanting to use the same version key and fails with the same error

[zpatten]

$ npm list | grep ember-cli-deploy
npm├─┬ ember-cli-deploy@0.0.5
│ ├─┬ ember-cli-deploy-redis-index-adapter@0.0.2
 ├─┬ ember-cli-deploy-redis-index-adapter@0.0.2

[achambers]

The version key used is the current git hash. Therefore, if you've made changes, you need to commit them, then build, then deploy. If you make changes, build, deploy then you are still using the same git hash.

[zpatten]

I did exactly that and still had the same results; it appeared to get stuck on a specific key.

[achambers]

Hey @jbrown, this isn't due to not having built first. It's because you haven't committed. Because the current index adapter we use the git hash as the key.

How would you expect this to work?

Also, this may not be an ember-cli-deploy change but more so an ember-cli-redis-index-adapter change

[jbrown]

@achambers Unless you have a post commit hook that builds your production bundle, it's pretty easy to forget to build between committing and deploying. In previous versions you could just overwrite a key but that functionality is gone now which leaves no room for error. How do you feel about a --force flag that allows you to overwrite a key?

[BryanCrotaz]

Rather than using the git hash, just hash the file? Then you'd have a unique hash if the file had changed. Isn't this how fingerprinting works?

[achambers]

ember-cli-deploy is in the process of merging with ember-deploy. Therefore, no more changes will be made to this repo. Please see the README for more details. /cc @jbrown @zpatten

[zpatten]

@achambers Thanks for the update, but considering your response is around 3 months old I've long since moved on.

[achambers]

No problems @zpatten. These changes won't effect you then.