Download the PHP package northern/doctrine without Composer
On this page you can find all versions of the php package northern/doctrine. 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 doctrine
Doctrine
Northern Doctrine is a small library that makes it easy to add Doctrine configuration to plain PHP applications without having to rely on frameworks such as Symfony 2.
Installation
Simply add it to your Composer.json:
"northern/doctrine": "1.0.0"DoctrineConfig
To use the DoctrineConfig class simply instantiate it and pass the path to the location in the file system when the YAML configuration files are located:
``
The DoctrineConfig class tries to load 2 configuation files from the specified location. The first configuration file is called config.yml and contains the basic configuration. The config.yml has the following sections:
Thedatabase` section should be pretty straight, simply supply the database details.
The entity section specifies the file system location of where your entity class files are located. Notice that paths is an array and you can add multiple locations here.
The proxy section specifies where the proxy classes Doctine generates will be stored. It's also required to specify the namespace of your proxies. Usually this is just the regulat namespace of your entites followed by Proxies.
The isDevMode parameter is true by default but for production applications can be set to false instead.
Besides needing the config.yml described above, it's also required to have an environment specific configurations. In the example above where we instantiate the DoctrineConfig class we also specify the enviroment which in this case is dev. Because of this, DoctrineConfig will after loading the config.yml try to load the config_dev.yml file. The environment specific configuration contains the settings for that specific enviroment. Usually this are just the database connection settings, such as:
` Make sure your enviroment config exists.
After instantiating the DoctrineConfig it's easy to get access to the Entity Manager:
``
All versions of doctrine with dependencies
symfony/yaml Version ~2.0
psr/log Version ~1.0
northern/common Version ~1