-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
[Proposal] Use "config/" instead of "etc/" #56
Comments
Why not, I'm not opposed to the idea... and I will probably not fight much long on this one :) |
Not strongly against going back to |
Same as @chalasr, encryption keys or other things than config totally fit in |
Why don't you think that encryption keys fit into |
It's the problem with With |
i prefer /etc but i'm ok with config i agreed with @chalasr |
Please stop reassembly Linux terms in Symfony project, that's already too many etcs in Linux(/etc, /usr/local/etc), just use something straightforward and easy to understand by anyone, and config is a very commonly used name, we should just use it. |
I don't have a hard argument that would favor either side to be honest. I know that I agree with @chalasr, but isn't there another way you can do that? Personally, I feel that |
@fabpot published a poll on Twitter and |
@thunderer don't forget that you can still customize what this directory is called |
Well, looking at a Symfony project for the first time it might not be obvious what should go into |
Both looks corrects to me. I would prefer
Personally, with a project based on Symfony but having Capistrano configuration and maybe others tools, I would like to configure all of them to have an unique |
I'm torn between consistency with |
A small comment for people saying that "config/" is only for config and "etc/" is for anything. We already have a dir for "anything" and it's called "Resources/". |
I use /configuration/etc when I use exactly the same structure of /etc if not I use subfolders in configuration. So config is best as it is more generic I guess. |
The linux directory structure is a pretty common industry standard these days. As previously mentioned, people with a little bit of linux experience know what these directories are for. If we are truely arguing whether My OCD doesn't go well where half of the directory structure is using linux terms and the other half isn't. So yeah, please go with |
I'm well swayed by the the arguments that I'm leaning towards I'm unconvinced by the arguments for providing a *nix-like directory - this is a PHP app, not a OS and while there are occasional similarities I don't think there is value in copying the *nix directory structure wholesale if it is opaque to people not already familiar with its conventions. |
@haroldiedema It is in no way a common industry standard for project layouts. |
It's not an OS but it does have a Kernel... So you have to assume the *nix philosophy here |
I saw that Paul Jones did a write-up discussing this and his mentioned some numbers he found when putting together his proposed pds/skeleton package. Perhaps it would be useful to reach out to him to discuss the research more in-depth (what was evaluated, how the evaluation was done, etc) to leverage the knowledge he gathered and what led to the decisions made for the skeleton? Not that I'm proposing to go with the skeleton, just to garner more insight into other independent research that was done |
+1 for config. Keep it simple. |
+1 for config. config is much easier to understand for beginners and all levels of developers. Using etc to match *nix directory structure seems unnecessary, and a pursuit of style/form over accessibility/function. |
How about renaming |
@rosier would be even worse IMO, as the whole |
@stof I thought |
It's not only about configuration. It's for everything that is not code, not binary, not vendor, and not public resource.
It's really different. "What doesn't fit anywhere fits in |
https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard Adapting it to the case of a Symfony project, Introducing a |
I've looked into some popular frameworks, and this is what I found:
Considering this, not only could Flex (and Sf4) rename |
@javiereguiluz while I don't have a strong opinion other than nostalgia: https://github.com/php-pds/skeleton I know there is no real standard, but it does seem like the majority is using public. |
Ok, I will rename |
👍 for doing so |
Please note that you need to rename |
Just a thought, but nobody considered cfg as a compromise? It doesn't jump out as much as "config", is consistent with the style of names and is also self-explanatory. It would also go nicely along with "tpl" for templates. |
@lukasz-zaroda |
This is a controversial topic that is often discussed in the Symfony Slack chat. More and more people are saying that
etc/
is not the best choice because it's not that easy to understand.At first I ignored them, but this idea is growing more and more in me. Names are great when you can understand them without explanation: "etc/" requires explanation and it complicates the first experience with the framework; whereas "config/" requires no explanation and it's exactly what everybody expects.
Other popular projects use "config/" (Laravel, Rails) and it's pretty common in PHP world too (according to these stats: http://paul-m-jones.com/archives/6564)
The text was updated successfully, but these errors were encountered: