Download the PHP package promet/settings_compile without Composer
On this page you can find all versions of the php package promet/settings_compile. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package settings_compile
Drupal Settings Compile
Motivation
You should be able to treat the Drupal configuration represented in settings.php like a simple dictionary that can be serialized in any format that can represent a dictionary, because that's what settings.php actually is. This makes it simple to change the settings without knowing php and even without logging onto the server or making any git commits. You would want to allow this because your application will likely need to exist in several different environments at any arbitrary commit in its history.
An alternate strategy would be to version a settings.php that sets the
configuration variables according to Environment Variables fetched with
getenv(). If you have control over the visibility of Environment Variables to
the running php process, then that approach is preferable.
How To
Install this project with composer.
See examples/config.yml and witness the resulting settings.php when invoking
like this:
or you could even do this:
The command simply takes a path to a correctly formatted yaml file and the desired path at which to write the resulting settings.php file.
Schema
You can see this stated fairly plainly in Drupal\Settings\Schema but the gist is that you address the globals that are available for modification in settings.php by using the settings key, hence your databases hash would start like this:
and the keys you can set under settings is limited to this list:
databasescookie_domainconfinstalled_profileupdate_free_accessdb_urldb_prefixdrupal_hash_saltis_httpsbase_urlbase_secure_urlbase_insecure_urlbase_url
You can require your composer autoloader (or any other php file) like this (for 2.0.x):
This works because all values are naively quoted in 2.0.x.
You can specify the full path without aid of the DRUPAL_ROOT macro, though
that would require whoever edits the yaml file to know the full path to the
Drupal application on whatever server.
You can additionally effect ini settings like this:
Starting with 2.1.1, you can disable quoting for your value by prefixing with
a %, which gives you full access to php:
Similarly, any value starting with a $ is also naively left untreated.
Alternate Strategy with Environment Variables
You can also use the % escaping to make a yaml file that can very easily model
your config as something that is aware of its environment:
This makes setting up for your PAAS simple, though it does begin to beg the question as to whether you gain anything by using yaml instead of just versioning the php file and letting another system manage setting the environment variables, as described above in Motivation.
