-
Notifications
You must be signed in to change notification settings - Fork 92
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
Bootstrap file #11
Comments
I started out with a config file, but found it too inflexible. I like having the bootstrap as the main entry point, perhaps we could make the bootstrap an executable unto itself. As for being accessible via apache, I don't think it makes any odds for me. If you can protect dot files, you can protect a single phpmig.php file? That's not to say I'm against configuration files, they could have their place, but I'd rather it be secondary to the bootstrap. Just about every project I've come across has their own configuration and bootstrapping already, the phpmig bootstrap is there to try and take advantage of that. |
Perhaps phpmig could even look for both Another reason I would perfer not to have a The Apache access is not so much of a major. It just by default any file starting with a |
But do your projects have a config file? If so, wouldn't it be kind of pointless to have a phpmig config file, that calls your bootstrap, that calls your config file? And if that work wasn't done in the bootstrap file (that phpmig generates for you), phpmig would have to do it anyway? I think it's just a differing of opinions. Like you say, in my projects, the project config file and the project bootstrap do all the hard work, like setting up services, switching config for development/testing/staging/production environments (which can be a lot of changes) and having phpmig piggy back off that is quick and easy. If you feel that strongly about it, I'm happy to merge it in, as long as it doesn't replace the phpmig.php Otherwise feel free to fork? |
Another feature for thought.
Instead of having a default php bootstrap file called
phpmig.php
, perhaps a configuration file would be better, such as.phpmig
A few reasons for this would be:
The .phpmig format could be as simple as an INI, or perhaps even YAML, JSON, or XML
The text was updated successfully, but these errors were encountered: