> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/v5.x-1/hmvc/modules/module-service/common-methods.md).

# Common Methods

Here are the most common methods you can use to manage modules:

* `reloadAll()` : Reload all modules in the application. This clears out all module settings, re-registers from disk, re-configures them and activates them
* `reload(module)` : Target a module reload by name
* `unloadAll()` : Unload all modules
* `unload(module)` : Target a module unload by name
* `registerAllModules()` : Registers all module configurations
* `registerModule(moduleName,[instantiationPath])` : Target a module configuration registration
* `activateAllModules()` : Activate all registered modules
* `activateModule(moduleName)` : Target activate a module that has been registered already
* `getLoadedModules()` : Get an array of loaded module names
* `rebuildModuleRegistry()` : Rescan all the module locations for newly installed modules and rebuild the registry so these modules can be registered and activated.
* `registerAndActivateModule(moduleName,[instantiationPath])` : Register and Activate a new module

With these methods you can get creative and target the reloading, unloading or loading of specific modules. These methods really open the opportunity to build an abstraction API where you can install modules in your application on the fly and then register and activate them. You can also do the inverse and deactivate modules in a running application.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://coldbox.ortusbooks.com/v5.x-1/hmvc/modules/module-service/common-methods.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.