{"_id":"573ed0b587cbd20e00208c9f","version":{"_id":"5735936aafab441700723a53","__v":12,"project":"5735936aafab441700723a50","createdAt":"2016-05-13T08:42:18.615Z","releaseDate":"2016-05-13T08:42:18.615Z","categories":["5735936aafab441700723a54","5735a32931a73b1700887c94","5735b55beceb872200abbc6c","5735b56eb667601700d3bd6f","5735b9ba4b0ab120000b7dd4","5735b9c94b0ab120000b7dd5","5735cb131f16241700c8a0f7","5735e5c4e4824c3400aa1f21","5735e5d9e4824c3400aa1f23","5735e5f2ec67f6290013ac72","573ecfe0804f901700a9dfc7","573f276c7eeb8b190094ca7d"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":false,"codename":"","version_clean":"1.0.0","version":"1.0"},"parentDoc":null,"__v":7,"category":{"_id":"573ecfe0804f901700a9dfc7","version":"5735936aafab441700723a53","project":"5735936aafab441700723a50","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-05-20T08:50:40.206Z","from_sync":false,"order":5,"slug":"customising-your-ensembl","title":"Next steps"},"project":"5735936aafab441700723a50","user":"573592b84b0ab120000b7d44","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-20T08:54:13.960Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":1,"body":"Ensembl sites use a modular architecture allowing features to be added, modified or overwritten by including additional plugins.  The default ``setup.ini`` file includes three plugins in the [[REPOSITORIES]](doc:repositories) stanza and [easy mirror](https://github.com/lepbase/easy-mirror) makes it straightforward to include additional plugins from the Ensembl [public-plugins](https://github.com/Ensembl/public-plugins) or any other suitable ``git`` repository.  To add/customise features, changing or including additional plugins in the [[REPOSITORIES]](doc:repositories) stanza will ensure that the latest version (of the specified branch) is loaded each time you run [Step 4.1: Update Ensembl webcode](doc:step-41-update-ensembl-webcode).\n\nEach plugin that is loaded has the potential to override parts of the plugins that were loaded before so the Ensembl [public-plugins/mirror](https://github.com/Ensembl/public-plugins/mirror) plugin is the last to be loaded.  This is where configuration settings such as which species to include and database connection details are stored by [easy mirror](https://github.com/lepbase/easy-mirror) and can be directly edited to make changes between running [Step 4.1](doc:step-41-update-ensembl-webcode) and [Step 4.2](doc:step-42-reload-ensembl-website).  However local changes will  be overwritten every time you run [Step 4.1](doc:step-41-update-ensembl-webcode) so it is best to make persistent changes to your Ensembl instance by [Creating a plugin](doc:creating-a-plugin) of your own.","excerpt":"","slug":"using-plugins","type":"basic","title":"Using plugins"}
Ensembl sites use a modular architecture allowing features to be added, modified or overwritten by including additional plugins. The default ``setup.ini`` file includes three plugins in the [[REPOSITORIES]](doc:repositories) stanza and [easy mirror](https://github.com/lepbase/easy-mirror) makes it straightforward to include additional plugins from the Ensembl [public-plugins](https://github.com/Ensembl/public-plugins) or any other suitable ``git`` repository. To add/customise features, changing or including additional plugins in the [[REPOSITORIES]](doc:repositories) stanza will ensure that the latest version (of the specified branch) is loaded each time you run [Step 4.1: Update Ensembl webcode](doc:step-41-update-ensembl-webcode). Each plugin that is loaded has the potential to override parts of the plugins that were loaded before so the Ensembl [public-plugins/mirror](https://github.com/Ensembl/public-plugins/mirror) plugin is the last to be loaded. This is where configuration settings such as which species to include and database connection details are stored by [easy mirror](https://github.com/lepbase/easy-mirror) and can be directly edited to make changes between running [Step 4.1](doc:step-41-update-ensembl-webcode) and [Step 4.2](doc:step-42-reload-ensembl-website). However local changes will be overwritten every time you run [Step 4.1](doc:step-41-update-ensembl-webcode) so it is best to make persistent changes to your Ensembl instance by [Creating a plugin](doc:creating-a-plugin) of your own.