Ensembles Concepts article needs updating
This is an open discussion with 2 replies, filed under Ensembles.
Search
What it used to say:
#### Overview Ensembles are packaged copies of a Symphony project. Created from within the <a rel="concept">admin interface</a>, ensembles bundle the system—along with its database and workspace files—into an installable .Zip archive. Ensembles can be used to back up, migrate, or distribute a project. Community-contributed ensembles can be found <a href="/download/ensembles">here</a>. #### Usage Ensembles can be created by logging into the admin interface, navigating to `System > Preferences`, and clicking the “Create Ensemble” button. Your server will need to have PHP's Zip module enabled. Ensembles can be installed by following the general installation instructions for Symphony (see <a rel="tutorial" href="install-symphony">"Install Symphony"</a>). Note that ensembles will not copy custom database tables, including those created by third-party extensions. If your project includes non-core tables, be sure to backup or migrate your SQL separately. Full database packaging is planned for a future version of Symphony. #### Details Ensembles are essentially copies of a Symphony project, and so their structure mirrors that of Symphony itself. #### The Big Picture Ensembles are a convenient way to package and share a Symphony project. Because Symphony is so open and flexible, there are many possible use cases. A developer, for example, could build a highly customized CMS or web application and package it for distribution and installation with the click of a button. An agency, on the other hand, could use ensembles to scaffold common project types for rapid deployment and development.
Create an account or sign in to comment.
I just noticed that the content of the Ensembles Concepts article contains some out-dated content.
Actually, this change was made and has been a feature of version 2.0 of the Export Ensemble extension since its release in May 2012.
The extension excludes specific database tables, configuration settings, directories and files. You can see a list of the items that are excluded to avoid the issue of sharing sensitive data in the README file.
Be aware that, if you are using the Members extension, the member data WILL be included, because the tables it uses are standard section fields.