Make sure Composer is installed globally, as explained in the installation chapter of the Composer documentation.
Open a command console, enter your project directory and execute:
$ composer require sfu-dhil/nines:4.x-dev-up
Open a command console, enter your project directory and execute the following command to download the latest stable version of this bundle:
$ composer require sfu-dhil/nines:4.x-dev-up
Then, enable the bundle by adding it to the list of registered bundles
in the config/bundles.php
file of your project:
// config/bundles.php
return [
// ...
Nines\BlogBundle\NinesBlogBundle::class => ['all' => true],
Nines\DublinCoreBundle\NinesDublinCoreBundle::class => ['all' => true],
Nines\EditorBundle\NinesEditorBundle::class => ['all' => true],
Nines\FeedbackBundle\NinesFeedbackBundle::class => ['all' => true],
EWZ\Bundle\RecaptchaBundle\EWZRecaptchaBundle::class => ['all' => true],
Nines\MakerBundle\NinesMakerBundle::class => ['dev' => true],
Nines\MediaBundle\NinesMediaBundle::class => ['all' => true],
Nines\UserBundle\NinesUserBundle::class => ['all' => true],
Nines\UtilBundle\NinesUtilBundle::class => ['all' => true],
];
NinesUtilBundle is required by all the others.
Import the routing information as required:
# config/routes.yaml
nines_blog:
resource: '@NinesBlogBundle/config/routes.yaml'
prefix: blog
nines_dublin_core:
resource: '@NinesDublinCoreBundle/config/routes.yaml'
prefix: dc
nines_editor:
resource: '@NinesEditorBundle/config/routes.yaml'
prefix: editor
nines_feedback:
resource: '@NinesFeedbackBundle/config/routes.yaml'
prefix: feedback
nines_media:
resource: '@NinesMediaBundle/config/routes.yaml'
prefix: media
nines_user:
resource: '@NinesUserBundle/config/routes.yaml'
Copy the configuration files from the bundles and edit them as required:
$ cp vendor/sfu-dhil/nines/*/config/nines_*.yaml config/packages/
How you do this one depends on your project and your config. Doctrine migrations are the recommended approach.
This should be enough to get the bundles working. You may also wish to load the Doctrine fixtures.
Fixtures are available for development, testing, and production. They are
labelled dev
, test
, and prod
.
$ ./bin/console doctrine:fixtures:load --group=dev
- BlogBundle - various blogging functionality
- DublinCoreBundle - Attaches Dublin Core Metadata to entities
- EditorBundle - Wrapper around CKEditor
- FeedbackBundle - Attach comments to entities
- MediaBundle - Upload media files and attach them to entities
- UserBundle - User logins and security related things
- UtilBundle - Various things that don't fit well elsewhere
Each bundle should include documentation.