The testing instance: what differs from production
On the Business plan, a testing instance is a copy of your community where you try a HumHub upgrade, a module or a setting before your members see it. This page lists exactly what is copied, what is changed on the copy and what is switched off.
What is copied
When you click "Create a testing instance" on your hosting dashboard, CUZY copies your running community on the same server, in a few minutes:
- The database, as it is at that moment: spaces, posts, comments, wiki pages, events, messages, settings. The date of the data is shown on the copy and on your dashboard.
- The modules, at the exact versions your community runs, with your custom modules and your theme.
- The license keys of your paid modules, so they work on the copy too.
- The uploaded files are not copied: the copy shows the files of your community read-only. A file you upload on the copy stays on the copy, and your community never sees it.
The copy has its own address, <your name>-test.<region>.cuzy.app, and runs the same HumHub version as your community until you upgrade it.
Who can sign in
The copy is in maintenance mode for its whole life: only system administrators can sign in, with their usual password and two-factor authentication. A banner on every page says it is a testing instance, with the date of its data.
Every session of your community is signed out on the copy, and pending invitations are deleted. An administrator who usually signs in through single sign-on (LDAP, SAML, OAuth, Keycloak…) has no single sign-on on the copy: give that account a password on your community before you create the copy.
What is anonymized
Every account that is not a system administrator is anonymized:
| On the copy | |
|---|---|
| Name | "Member 123" (the account number) |
| Username | member-123 |
| Email address | member-123@example.invalid |
| Profile fields (phone, address, birthday, title, every custom field) | emptied |
| Password and external sign-in links | deleted: these accounts cannot sign in |
What members wrote stays as it is: posts, comments, messages, wiki pages and files keep their text, shown under the anonymized name. Treat the copy with the same care as your community: it holds the same content.
System administrators keep their accounts unchanged.
What is switched off
Nothing on the copy may reach your members or the services your community is connected to:
- Email goes to system administrators only, with
[TEST]at the start of the subject. Every other recipient is dropped. - Mobile push notifications are off: the push module is disabled.
- Single sign-on modules (LDAP, SAML, OAuth, OpenID Connect, Keycloak…) are disabled: an LDAP synchronization on a copy could delete accounts.
- Credentials of connected services are removed: every setting whose name says key, secret, token, password, webhook, client id or license (payment, maps, AI services, integrations). Set a test key again on the copy if you want to try a connection. Your dashboard shows how many were removed.
- Waiting background jobs of your community (emails not yet sent, for example) are not carried over.
- The copy has a new installation id, so the HumHub marketplace never sees two installations as one.
What the copy does not have
- No backups and no monitoring: it is a disposable copy. Anything you want to keep, do it on your community.
- One copy per community. "Recreate from production" deletes the current copy, with everything done on it, and makes a new one from today's data.
- Deleted 7 days after its last use: an administrator signing in or an upgrade counts as a use. You get an email the day before.
- It is also deleted when your community leaves the Business plan, is suspended or is deleted.
Upgrading the copy
On your dashboard, "Upgrade the testing instance" moves the copy to a newer HumHub version at once, without a backup. Check the pages your members use, then upgrade your community. The guide Test a HumHub upgrade before your community sees it has the checklist.