https://github.com/gnugat/symfony-empty-edition

[maintained] A skeleton to help you bootstrap your Symfony applications, without the fuss of the Standard Edition
https://github.com/gnugat/symfony-empty-edition

Last synced: 8 days ago
JSON representation

[maintained] A skeleton to help you bootstrap your Symfony applications, without the fuss of the Standard Edition

• Host: GitHub
• URL: https://github.com/gnugat/symfony-empty-edition
• Owner: gnugat
• License: mit
• Created: 2015-09-19T10:42:53.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2016-03-19T09:01:05.000Z (over 8 years ago)
• Last Synced: 2024-04-16T15:20:15.345Z (7 months ago)
• Language: PHP
• Homepage:
• Size: 11.7 KB
• Stars: 81
• Watchers: 7
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Symfony Empty Edition

A skeleton allowing you to create an empty Symfony application: it is provided without

any libraries or bundles (except for Symfony's FrameworkBundle).

You can then start building on it, and install the dependencies you need.

> **Note**: The [Symfony Standard Edition](https://github.com/symfony/symfony-standard)

> provides a big set of libraries and bundles (database, email, templating, etc).

> If you don't feel comfortable with picking your own yet, you should probably use it.

## Installation

Use [Composer](https://getcomposer.org/) to create a new application:

```

composer create-project gnugat/symfony-empty-edition my-project

```

## Differences with the Standard Edition

* Only 2 bundles: `src/AppBundle` and `symfony/framework-bundle`, add the ones you really need

* Only 1 front controller (`web/app.php`), change the environment using the `SYMFONY_ENV` environment variable

* No annotations (can be brought back by installing `sensio/framework-extra-bundle`)

## Use cases

There are many real world use cases for this distribution. Here's a small selection:

* tailored made applications: for applications that require "non standard" dependencies (e.g. Propel or Pomm for the database, etc)

* micro applications: for applications that don't need database, templating or mailing systems (Symfony can be a Micro Framework)

* legacy migrations: for applications that need to depend on legacy database, templating, etc while migrating to symfony

* teaching material: [better explained here](http://www.whitewashing.de/2014/04/24/symfony_hello_world.html)