Configuring a Muppy Enterprise Instance¶
Once your Muppy Enterprise server is installed, the next step is to configure the instance: create the Muppy database, install the Muppy apps, and set the handful of options that make the instance usable.
Warning
Create one database per Muppy server. Nothing technically prevents more, but a single database is the only supported configuration.
1. Create the Muppy database¶
Open your Muppy server's URL. The database creation form appears. Fill it in as follows:
| Field | Value |
|---|---|
| Master Password | The admin_passwd you defined when the server was installed. |
| Database Name | Must match the IKB_DB_FILTER you set at installation — the default filter is muppy_.*, so e.g. muppy_001. |
| The administrator account's address. | |
| Password | The administrator account's password. |
| Language | Leave English (US). |
| Country | Your country. |
Then click Create Database.
2. Install the Muppy apps¶
Log into the database you have just created, with the administrator account.
Open the Apps menu and install Muppy - All in one Installer. It depends on every Muppy app of a standard installation, so installing it pulls in the whole set in the right order — you do not have to install them one by one.
Then install what is specific to your deployment:
- optional cloud provider modules you need,
- the modules developed by you or for you.
Info
If you get "The server is busy right now, module operations are not possible at this time, please try again later.", click Ok and launch the operation again.
3. Store attachments in the database¶
The Inouk Attachments Storage app lets Muppy store its documents in the PostgreSQL
database rather than on the filesystem — which is what makes a Muppy instance easy to back
up and restore as a single object.
- Open the Settings page.
- Scroll to the Attachment Storage (Inouk) section.
- Set Attachment Storage to PostgreSQL Database.
- Click Save, at the top left of the page.
- Scroll back to Attachment Storage (Inouk).
- Click Move all Attachments to Specified Storage to migrate what is already stored.
Attachment Migration Batch Size controls how many attachments are migrated per batch (50 when unset), and Check all Files Attachments Storage launches an asynchronous task that verifies every file attachment's storage.
4. Configure the Muppy SSH key¶
Configure the SSH key Muppy will use to connect to every host it manages — see SSH Keys.
5. Disable the firewall (optional)¶
If you do not need Muppy to manage UFW, this is the moment to turn it off — see Disabling UFW globally.
6. Synchronise Tasks and Scripts¶
Run the Task and Script synchronisation so that the mpy.task / mpy.script records of
the installed apps exist — see
Task and Script Synchronisation.
7. Configure the installation source locations¶
When Muppy runs in a private network with no Internet access, it must be told where to fetch the tools it installs.
- Open the Settings page.
- Select the Muppy settings.
- For each URL parameter, enter a URL that is reachable from your network — or click the reset button next to it to restore the default.
Custom URLs are not supported for the parameters that offer that reset button.
Your Muppy server is now ready to use.