Preparation
What to decide before launch
The installer will ask about this itself, but the answers should be prepared in advance.
- How many servers and which is master
-
The master holds the platform domain and is responsible for configuration. The other nodes connect to it, knowing the mic addresses. On the master
--master=yand--masterdomain, on nodes--master=nand--micaddress. - Where the database will be
-
Three options: in a container on the same server, as a cluster on the host, or on a separate server. In the first two cases
--dopginstall=yand--pgmode=dorh. In the third--dopginstall=nand--pghostwith the address of the ready server. The DB administrator creates the platform role in advance and gives the engineer the address, port, role name, its password, and SSL requirements. On the platform master (--master=y) this data is entered on the PostgreSQL access screen:pghost,pgport,pgpostgresuser,pgerapwd,pgssl. The built-inpostgresrole password is not needed for this scenario. More: era_installer/install-ssh.adoc#era-installer-external-pg. - Whether replication is needed
-
If yes, on the database master
--usereplic=y, and the replica is installed by a separate run with--pghostmode=r. - Where the shared directories are
-
The platform needs directories visible to all site nodes. One server can serve them over NFS (
--installnfsserver=y), the others mount them (--nfsserveraddr). For a single server neither is needed.
Put into the distribution
era/image/era_*.tar.gz platform image, required
era/image/postgres_*.tar.gz PostgreSQL image, if the database is in a container
era/assets/era_product_*.zip product layer, if used
The PostgreSQL image may be omitted: with the --usedockerhubpgimage=y key the installer takes it from Docker Hub.
This requires internet access from the server.
ssh access
Needed if you install from your machine to a remote server.
Key-based login is the preferred method:
ssh-copy-id -p 22 user@192.168.0.10
bash install_ssh.sh --host=192.168.0.10 --user=user --sshkey=~/.ssh/id_ed25519
Password login also works. The password is asked once per run: the installer keeps one connection and reuses it for all commands, rsync, and installation launch.
The account needs sudo on the remote server: the installation itself runs there with root privileges.
Server fingerprint
If the server was reinstalled, ssh will refuse to connect: the fingerprint in ~/.ssh/known_hosts will not match.
The installer does not delete the entry silently — that would disable authenticity verification.
Remove it yourself:
ssh-keygen -R 192.168.0.10
or allow the installer to do it with the explicit key --resetknownhosts=y.
Proxy
If the server accesses the internet through a proxy:
bash era/scripts/install.sh --useproxy=y --ehttpproxy=http://proxy:3128
--ehttpsproxy defaults to the --ehttpproxy value; set it separately only if the addresses differ.
Installation without internet
With the --useapt=n key the installer does not install packages itself.
This means that by launch time the server must already have:
-
docker and a running
dockerservice; -
a PostgreSQL server of the required version, if the database is installed on the host;
-
nfs-kernel-serverornfs-utils, if the server serves directories.
Prechecks will list what is missing before the confirmation screen.
Platform and PostgreSQL images in this mode must be in era/image.
The installer will ask to confirm this mode (--proceedwithoutapt=y) so that --useapt=n accidentally included in the command does not lead to an incomplete installation.