# New Addon BootManager

**URL:** <https://discourse.getcockpit.com/t/new-addon-bootmanager/789>\
**Category:** Addons\
**Created:** [April 26, 2019, 6:39pm UTC](https://discourse.getcockpit.com/t/new-addon-bootmanager/789 "2019-04-26T18:39:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![raffaelj](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/raffaelj/32/331_2.png) [@raffaelj](https://discourse.getcockpit.com/u/raffaelj)\
**Post date:** [April 26, 2019, 6:39pm UTC](https://discourse.getcockpit.com/t/new-addon-bootmanager/789/1 "2019-04-26T18:39:29Z")

</div>

While discussing methods to implement logging functionality of the Logger addon into other addons with @pauloamgomes, I thought about a way to load addons in a specific order. The current way, cockpit loads modules, is iterating over `/modules`, `/addons`, custom addon folders, that are defined via config `loadmodules` and than they load alphabetically.

Today I wrote a simple addon, that adds the option to

- load modules in a specific order and to
- load modules only if you need them (e. g. api calls don’t need to load admin ui addons)

> **[raffaelj/cockpit\_BootManager](https://github.com/raffaelj/cockpit_BootManager)**
>
> Boot Manager for Cockpit CMS. Contribute to raffaelj/cockpit\_BootManager development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![raffaelj](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.getcockpit.com/raffaelj/32/331_2.png) [@raffaelj](https://discourse.getcockpit.com/u/raffaelj)\
**Post date:** [June 15, 2019, 3:21pm UTC](https://discourse.getcockpit.com/t/new-addon-bootmanager/789/2 "2019-06-15T15:21:54Z")

</div>

Big update: I added a GUI and I changed the default behavior a bit.

 ![cp-bootmanager](https://canada1.discourse-cdn.com/flex030/uploads/getcockpit/original/1X/c63c21a583752d00536c141b3eba3d5ef77faad5.png)

See the changelog and the readme for more info

> <https://github.com/raffaelj/cockpit_BootManager/blob/master/CHANGELOG.md>
