Page History
| Table of Contents | ||
|---|---|---|
|
Overview
This page takes you from a prepared Linux host to the first login to iDNA Applications, and describes how to operate the installation afterwards. What the host needs is described in Running iDNA on your own Linux; upgrades in Upgrading iDNA Applications.
...
- points to this server: DNS resolves the name to this host. Choose such a name.
- IP address of …; links break if it changes: works without DNS, but every link breaks when the address changes.
- found locally, not verified in DNS: only the host itself knows the name; your users' browsers may not reach it.
- points to …, not to this server (for an IP address: not an address of this server): correct if a load balancer, a reverse proxy or a public NAT address forwards to this host.
- short name; works only if users' DNS completes it: works only where your users' DNS completes it to the full name.
- not found in DNS: your users' browsers will probably not reach it. Register the name in DNS first, or choose another one. If the check took about a minute, the host itself may not reach a DNS server; a name you know is registered can still be typed and confirmed.
- not checked: the installer could not check the name in DNS from this host, because the host has no IPv4 address outside Docker or the DNS lookups failed.
| Warning | ||
|---|---|---|
| ||
|
Press Enter to accept option 1, or type the number of another option. You can also type a host name yourself, for example a DNS alias your users already know. If that name does not point to this host, the installer says what it found and asks Use it? [y/N]; answer N to return to the list. Enter only the name, without https://, port or path: at most 63 characters, or an IPv4 address. If users reach iDNA through a reverse proxy with another port or path, choose the proxy's name here and, after the installation, set PANAGENDA_METABASE_SITE_URL as well (see Configuration File). The installer confirms your choice with a line starting with "Selected:".
...
- Save the certificate as
certfile.pem(PEM format, followed by any intermediate certificates) and the private key askeyfile.key(PEM format, without a passphrase). Keep exactly these file names. - Copy both files to
/opt/panagenda/appdata/volumes/nginx/. Restart iDNA:
Code Block language bash ifa restart
...
The installer creates the configuration file /opt/panagenda/appdata/ifa/config with the server address you chose and the values it detects on the host. Later runs do not replace the file; they only change single settings: the server address when you choose one, and the time zone after you confirm it. Settings you may want to change:
| Setting | Purpose |
|---|---|
PANAGENDA_HOSTNAME | The server address: the name users open in their browser, also used for the Metabase reports and in the links of alert emails. Chosen during the installation; change it with ifa hostname rather than in the file. |
PANAGENDA_TIMEZONE | The time zone of the containers. Detected from the host. |
PANAGENDA_COMPOSE_NETWORK_SUBNET | The private /24 subnet of the internal Docker network, by default 192.168.238.0/24. Change it if your network already uses this subnet. |
PANAGENDA_METABASE_SITE_URL | The address of the Metabase reports, by default https://<PANAGENDA_HOSTNAME>/metabase. Set it only if users reach Metabase through a reverse proxy with another port or path, in the form https://proxy.acme.com:8443/metabase; for another name, change the server address with ifa hostname instead. While it is set, the installer does not ask for the server address. |
PANAGENDA_POSTGRES_SHM_SIZE | Shared memory of the database, by default 2gb. Lower it only on small test hosts with less than 4 GB RAM. |
PANAGENDA_ENABLE_MCP | Enables the MCP server for AI clients, by default false (see Setting up the MCP Server). |
The file may also contain PANAGENDA_CONFIRMED_HOSTNAME. The installer and ifa hostname write it to remember that the server address was confirmed; do not edit it.
...
Operate iDNA with the command ifa as root:
| Command | What it does |
|---|---|
ifa start | Starts the containers if they are not running. |
ifa stop | Stops the containers. |
ifa restart | Restarts the containers. |
ifa down | Stops and removes the containers; all data is kept. |
ifa recreate | Stops, removes and starts the containers. Use it after changing the configuration file. |
ifa hostname | Shows the current server address and lets you choose a new one on the same screen as during the installation (needs a terminal). If you choose a different address, it asks whether to apply it right away, which makes iDNA unavailable for a few minutes, and shows the addresses as at the end of the installation. If you apply right away, the reachability check may report "could not reach" only because the containers are still starting. |
ifa hostname <name> | Checks the name and saves it as the server address without questions; if the name does not point to this host, it says what it found. Apply it with ifa recreate. |
ifa diagnose-network | Checks whether the internal Docker network collides with networks known to the host. Changes nothing. |
ifa uninstall | Removes iDNA Applications including the database (see Uninstalling). |
Logs
- Installer:
/opt/panagenda/logs/ifa-upgrade_<date>_<time>.log, one file per run. Attach it to every support request about an installation or upgrade. - Services:
/opt/panagenda/logs/<service>/, for exampleidna,dda,postgresornginx. iDNA deletes these files after 7 to 14 days. - Containers:
docker logs panagenda_<service>shows the latest output of a container; add-fto follow it.
...