Comments (9)
from better-wp-config.
The way I see it calmPress is going to end with two types of distributions, one with the "classical" directory structure and one which is composer friendly. 3 sounds like the most flexible for such a thing as it is possible to just distribute a different one based on the containing distribution.
But alternatively I would be happy to just pass whatever file can be used for defaults as a parameter to the bootstrap constructor (or by any other way). We can even agree on some naming scheme to avoid collisions if that is needed.
from better-wp-config.
@markkap Hmm. Let me mull over that suggestion for a potential implementation. Thanks.
from better-wp-config.
I am still thinking that as much of better-wp-config as possible should be incorporated into ClassicPress, to make it a first-class option that is very simple to use.
In this context, you just have to pick a different file (or set of files) to edit instead of wp-config.php, and any defaults that ClassicPress supplies would be baked into the code already.
So I don't think having platform-specific defaults should be necessary at all, basically.
from better-wp-config.
@nylen My thinking along these lines is that hopefully BWPC
could be seamlessly included in ClassicPress just like how Requests, SimplePie, getID3(), kses and others are already included in WordPress core.
In this scenario ClassisPress core would provide the platform specifics but the ClassicPress user/developer perspective would not need to even be aware of this, unless of course they dive into the ClassicPress source code.
As I told @markkap on our Slack this weekend (just mentally replace "CalmPress" with "ClassicPress" when you read this):
"Speaking of CalmPress using
BWPC
w/o modification, I will happily commit to not breaking CalmPress and not making a decision that saddles CalmPress with supporting something you want to get rid of, as long as you are okay with enhancements being ones you can change and/or optional that you need not enable, as applicable. My goal is to create something that can become defacto-stardard across all the "X-Press" family."
Clearly it is up to you and the ClassicPress community exactly how you approach this, but I am hoping that having BWPC
stay version controlled in one place vs. copied and modified incompatibly in many places will be better for all the X-Press family. I don't think there is a competitive value in differentiating on config since it will be easier for web hosts to support a single config standard vs. multiple slightly incompatible approaches. In fact I think it will be a competitive disadvantage to has divergent config solutions.
(Also, as an aside, I have no real reason to want to control this, as long as it can meeting my needs which it already does. The lack of a solution causes me problems in other areas and I just want a viable solution to exist and thrive. I'll be happy to create a new GitHub org that with a charter that a consortium of parties interested in being good steward managed, if that ever becomes a need. That said I think early on that action was needed before any such collaboration would be likely to happen.)
from better-wp-config.
@nylen Also, I envision ClassicPress would include a copy of BWPC
and then stick pat with it unless or until you are ready to upgrade to a later version.
If BWPC
ever ends up diverging from ClassicPress' goals, you'd just start maintaining and evolving the last version you used and take it in your preferred direction.
That said, my goal would be you would never have a reason to want/need to diverge from our versioned master
branch, so as long as I am leading BWPC
.
from better-wp-config.
Ok, so we already have a place for a config standard to live: https://github.com/corePress
This is the place for collaboration between pieces that ClassicPress and calmPress share.
The what can live there. (How do I configure ClassicPress, calmPress and WordPress for multiple environments? What extra steps do I need to take to make this work on WordPress?)
The how can live in the ClassicPress and calmPress source code, and the code here can be the pieces that you need to drop in for this to work with WordPress.
I am happy for ClassicPress to refine and follow a standard/implementation like that.
from better-wp-config.
"Ok, so we already have a place for a config standard to live: https://github.com/corePress"
So, we could potentially move BWPC
there, once it gets a little more mature. That sounds like a solid plan.
_"The what can live at corePress and the how can live in the ClassicPress and calmPress source code,
So are you saying you do not want a standard implementation, but instead want multiple implementations of the same standard, and thus the need for 3rd parties to have to understand and work around the inevitable incompatibilities, ala Internet Explorer and all the other browsers?
Wouldn't it not be better for the how to live at corePress — for BWPC
as well as for anything else shared — unless and until there is actually a need for divergence?
I believe the idea of trying to maintain multiple different implementations of the same standard — especially without the backing of large companies to fund said development and maintenance — will be fraught with peril.
Or said more simply: "There be dragons."
from better-wp-config.
Wouldn't it not be better for the how to live at corePress — for
BWPC
as well as for anything else shared — unless and until there is actually a need for divergence?
Sure, maybe so. I guess I was thinking this would make it more difficult to fit BWPC
into individual projects, but I don't have a strong opinion there.
from better-wp-config.
Related Issues (16)
- Update WP_Bootstrap to allow multiple environment-specific options for 'file_format' and 'provider'
- Update WP_Bootstrap to allow multiple wp-bootstrap.com to contain only a single value for 'config'
- Break out classes in better-wp-config.php into a /src directory
- Enable support for WPEngine
- Ensure we work with WP CLI
- config directory should probably be .config HOT 1
- Move better-wp-config.php to wp-includes? HOT 1
- PHP 5.2 is dead even in WP, namespaces can be used everywhere :)
- Add in a config.secrets.* file
- Consider moving better-wp-config.php to subdirectory one level below web root HOT 2
- Ensure better-wp-config works with Roots/Bedrock
- Provide sample configuration files for multi-tenancy
- Update so `wp-bootstrap.php` if only required for non-default locations
- Select a coding standard HOT 2
- Add method for 3rd parties to add to list of available config options for their own plugin/theme/etc. configuration
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from better-wp-config.