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

Specify manifest file path #41

Open
makabde opened this issue Jun 10, 2015 · 5 comments · May be fixed by #63
Open

Specify manifest file path #41

makabde opened this issue Jun 10, 2015 · 5 comments · May be fixed by #63

Comments

@makabde
Copy link

makabde commented Jun 10, 2015

When I run middleman build the manifest file is automatically created in the build folder. My issues is that between each build the content of the previous folder gets deleted.

I was wondering whether one can can specify the path to the manifest file.

@codyrobbins
Copy link

I have the same issue. But I’d love to be able to put the manifest somewhere else even if this wasn’t the case—the manifest is an intermediate build product and I don’t want it commingled with the actual build of my site.

@nshCore
Copy link

nshCore commented Jan 1, 2018

+1 for this same as @makabde my build directory is wiped every build so the manifest if lost, agreed with @codyrobbins this information doesn't belong in the build directory

@KevinBongart
Copy link

This might help: #58

I think there's still an issue happening if the file doesn't exist, but I'll give it a bit more work.

@dmerrick
Copy link

Trying this out, seems like the manifest file is stored in the right path, but it also seems like the manifest file isn't honored (all of my images are resized on every build). Is this a different bug?

@jagthedrummer
Copy link
Contributor

The problem here (probably) wasn't that the entire build directory was getting wiped but that the manifest specifically was being overwritten. #63 should fix that problem.

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

Successfully merging a pull request may close this issue.

6 participants