Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a way I can specify or disable the hash in the file names after ember build? #1418

Closed
mewben opened this issue Jul 21, 2014 · 6 comments

Comments

@mewben
Copy link

mewben commented Jul 21, 2014

After ember build --environment=production, I get files like this,
assets/vendor-49b0784051ff2fcef9a3b5dfb8636c7a.js

This file changes everytime I invoke build. Is there a way to disable this and specify the file names, or just remove the hash part?

@stefanpenner
Copy link
Contributor

Yes you can disable fingerprinting, once I'm at my laptop I will provide you with the in incantation

@abuiles
Copy link
Member

abuiles commented Jul 21, 2014

Fingerprinting is done with broccoli-asset-rev, just remove it from you package.json and that will do. —
Sent from Mailbox

On Mon, Jul 21, 2014 at 4:57 AM, Stefan Penner notifications@github.com
wrote:

Yes you can disable fingerprinting, once I'm at my laptop I will provide you with the in incantation

Reply to this email directly or view it on GitHub:
#1418 (comment)

@rwjblue
Copy link
Member

rwjblue commented Jul 21, 2014

You can also remove via the following in your Brocfile.js:

var app = new EmberApp({
  fingerprint: {
    enabled: false
  }
});

@stefanpenner
Copy link
Contributor

Let's get this in the docs

@jdjkelly
Copy link
Contributor

It's in the docs: http://iamstef.net/ember-cli/#fingerprinting-and-cdn-urls

@mewben just curious if you checked there? Did you search for anything in particular? Just wondering if we can make it easier to find.

stefanpenner added a commit that referenced this issue Jul 21, 2014
Make explicit how to disable fingerprinting. (closes #1418)
@mewben
Copy link
Author

mewben commented Jul 23, 2014

Thanks guys. @jdjkelly Yes, I checked there but I guess I must have missed it or it has been just added lately. The last time I checked the docs was way before version 0.0.34

Lesson learned. Check the docs for updates.

Thanks everyone for the kind reply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants