MyZapp

Declaring the source of a GOLIVE

Available in en es fr

Updated on 10/25/2026

On the instance that receives the configuration (the target), you declare once the instance that provides it (the source): the testing instance declares development, production declares testing. Open Administration › Instance and operations › GOLIVE, then GOLIVE — source.

Nothing is written into this instance's configuration until a GOLIVE is applied: declaring the source, testing the connection or adding bindings changes no process, form or service.

Declaring the source

  1. Environment: the source instance name, as the team calls it ("DEV", "Acceptance"…).
  2. Source instance address: its full https:// address. An address on the company's internal network is accepted; the instance itself (localhost) is not.
  3. GOLIVE read key: the key created on the source (see "Prepare the source instance of a GOLIVE"). It is stored encrypted in this instance's secrets and never shown again.
  4. Save.

To change the source later, leave the key empty: the current key is kept. If the address changes, the key is asked again: a key is never sent to an instance it did not serve.

Remove the source also deletes its key and all its bindings.

Testing the connection

Test the connection reads the source catalog and shows how many modules and items it offers. When it fails, the message says why:

  • address refused or source unreachable: check the address, the network and the source certificate;
  • key refused: the key was revoked, is not a GOLIVE read key, or its owner may no longer read GOLIVE on the source;
  • redirect: the source points to another address, which is never followed; declare the final address directly.

Saved bindings

A configuration item often refers to something that exists in every instance: a group by its code, an account by its email, a mailbox or a machine group by its name. When the same name exists here, it is found automatically.

When it has another name here (the source mailbox support-dev is called support in production), bind it once:

  1. in Saved bindings, choose the type, enter the key in the source and the key in this instance;
  2. Bind. The key in this instance must designate an existing item; the "Items of this instance" list helps you find it.

The binding is reused by every later GOLIVE from this source. If the bound item is deleted here, the binding is flagged "not found".

A secret cannot be bound: the configuration quotes its name as is. Create it here under the same name, with the value specific to this instance.

Applies from version 1.0 Verified for version 1.0

Was this article helpful?

Still need help? Create a request