Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
hugo deploy ignores patterns always removing files #6681
My website is hosted on a AWS S3 bucket which also containst other files not managed by hugo. That works on a bare domain which means that I cannot move conttent another bucket to isolate hugo generated site.
I tried to use patterns to control deployment but apparent it has zero effect, it always ignore them.
What version of Hugo are you using (
@bep I do not think that this bug should be closed, maybe transformed in a feature request but clearly not closed.
As we all know, AWS S3 buckets are a flat, with no folders but let's assume they are as their technical detail should not affect behaviour.
Deploying to a prefix path makes no sense when you try to publish a website. AWS S3+CloudForm does require you to use bucket root. There is nothing to configure about that on AWS as far as I know.
Now that I read the documentation again I finally realize the matchers are only for adding extra metadata to files.
I wonder if we could re-use the same matcher sections and patterns to tell hugo to skip/ignore those patterns, maybe something like:
I almost never comment on closed issues.
I'm not sure what you mean by ClodForm, but I guess you mean CloudFlare.
I have not implemented this feature, but I'm very familiar with the AWS tech stack (see https://github.com/bep/s3deploy), and buckets don't need to be flat. If you want to discuss this, use the forum. We're not adding more complexity to this unless we get some really convincing arguments.