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

Config file inheritance doesn't actually work #144

Closed
ghost opened this issue Jan 22, 2012 · 5 comments
Closed

Config file inheritance doesn't actually work #144

ghost opened this issue Jan 22, 2012 · 5 comments

Comments

@ghost
Copy link

ghost commented Jan 22, 2012

I've got a base.yaml a production.yaml and a development.yaml

base.yaml has the following:

deploy_root:                ../

development.yaml does this:

extends:                    base.yaml
mode:                       development

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.

@navilan
Copy link
Member

navilan commented Apr 18, 2012

@khiltd - Can you share your source somewhere? I don't see this issue on my sites.

@ghost
Copy link
Author

ghost commented Apr 19, 2012

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

@ghost
Copy link
Author

ghost commented May 27, 2012

So have you abandoned this project or what?

@ghost
Copy link
Author

ghost commented May 29, 2012

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 sitepath. Anyone who wants to place them elsewhere is simply out of luck.

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

extends: ./config/app/base.yaml

@navilan
Copy link
Member

navilan commented May 30, 2012

@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:

extends:  config/app/base.yaml

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".

@navilan navilan closed this as completed May 30, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant