-
Notifications
You must be signed in to change notification settings - Fork 246
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
Config file inheritance doesn't actually work #144
Comments
@khiltd - Can you share your source somewhere? I don't see this issue on my sites. |
There's nothing I could share that isn't in the above snippets. Your documentation makes an allusion to the necessity of producing an "extended config" file for the purposes of inheriting, but the link that is meant to point the reader to an example of what this actually is 404s (as do an inordinate number of links in the documentation pages): https://github.com/hyde/hyde/blob/master/hyde/layouts/doc/pages.yaml |
So have you abandoned this project or what? |
So this is happening because https://github.com/hyde/hyde/blob/master/hyde/model.py#L200 Blindly assumes that everyone is going to be keeping their config files at the root of the I'm not going to bother asking for a fix, but hopefully this will help anyone else who finds themselves similarly chained to a sinking ship: Fake it out with a dot followed by a full path and it seems to actually load
|
@khiltd - Not a blind assumption. Thats by design. Throughout hyde, you will see that there default values for locations of things (content folder, layout folder, media folder, config files). Each of them can be overridden in the config. You can also try:
and it should work just fine. Also, you are not on a sinking ship. You decided to throw yourself over and hang by the side rails and now you are complaining that water is splashing all over you. Time spent on supporting projects like hyde are time taken away from something else important. When you ask for support it is important to provide the information requested for deducing the problem. If you had shared your source (or a pared down version of it) somewhere, your problem would have been solved "a month ago". |
I've got a
base.yaml
aproduction.yaml
and adevelopment.yaml
base.yaml
has the following:development.yaml
does this:Generating with
development.yaml
fails to honor the deploy_root setting, and any context data properties set in the base file are completely missing in all of Hyde's output.The text was updated successfully, but these errors were encountered: