1 · Servers to provide
Three machines. Virtual machines are fine, provided their cores and memory are reserved rather than shared. What to install on them is in section 5.
| Server | Processor | Memory | Storage |
|---|---|---|---|
| V4 serverThe live eRegistrations service | 16 physical cores32 threads, dedicated | 256 GB | 600 GB system+ 8 TB data (SSD) |
| S4 serverHolds the old records so they stay readable | 8 coresdedicated; today’s 16 shared cores are lightly used | 32 GB | 160 GB system+ 200 GB database + 2 TB documents |
| Backup serverHolds copies of both systems, on a separate machine | 4 cores | 16 GB | 8 TB |
One backup machine is enough for both systems: a full copy of both together comes to about 4.6 TB, of which 1.8 TB is old files that no longer change. An incremental backup stores those files only once: 8 TB then holds two full generations of the rest, or more once the V4 data is cleaned up, as the next paragraph describes. Use two smaller machines instead if that suits your resources better, or if the two systems end up in different buildings.
Plan at least 6 TB for the data disk of the V4 server. Uploaded files older than 90 days, 1.8 TB, are not on the machine: they are kept on a separate archive storage, and come back with the rest. About two thirds of the data on the machine is old logs and workflow history, not the registry records themselves. Decide what must be kept, clean up the rest, measure again, then order the disks.
2 · The two systems
They are different products and need different handling.
V4 server
- What it is
- The live service. Applications are filed and processed here.
- Runs on
- 28 Docker services, plus PostgreSQL, MongoDB and Redis installed directly on the machine.
- Data today
- 3.9 TB (2.1 TB on the machine and 1.8 TB of old files on an archive storage), built up over 30 months — about 130 GB a month on average.
- How it moves
- The whole machine can be rebuilt and restored on the new server. Step-by-step transfer guide (in French).
S4 server
- What it is
- The old system, kept so that past records can still be opened.
- Runs on
- Plesk hosting, with MariaDB and PHP (versions 7.2 to 8.0 are installed).
- Data today
- 718 GB of documents and a 17 GB database.
- How it moves
- Only the archive’s databases and its two document folders are copied, not the whole machine. Step-by-step transfer guide.
3 · Network ports
For the V4 server. Two ports are open to everyone, one to your administrators, and one to specific addresses only. Everything else stays closed.
| Port | Open to | Purpose |
|---|---|---|
| 443 | Everyone | The service itself (HTTPS) |
| 80 | Everyone | Redirect to HTTPS |
| 22 | Your administrators only | Server administration (SSH) |
| 61613 | Specific known addresses only | Message exchange with outside systems. Keep it only if the service still exchanges messages that way. |
The databases must never be reachable from the internet. Keep PostgreSQL, MongoDB, Redis and MariaDB closed to the outside. The V4 server also makes outgoing HTTPS calls of its own, including to translations.eregistrations.org and archive.monentreprise.bj. These must be allowed out, and the first is an outside service the platform still depends on — worth deciding whether to keep it or bring it in-house. The servers also need outgoing access on 443 and 80 for software images, updates and certificates, 587 for email, and 53 and 123 for name resolution and time.
4 · Web addresses
Nine names point at the V4 server and one at the S4 server.
| Address | Points to | Serves |
|---|---|---|
services.monentreprise.bj | V4 server | The service itself — applicants and officers |
login.monentreprise.bj | V4 server | Signing in |
bpa · gdb · stats | V4 server | Service design, registry data, dashboards |
admin-home · home-new · admin-home-new | V4 server | The published information pages, and the tools that edit them |
graylog.monentreprise.bj | V4 server | System logs, for your IT team |
archive.monentreprise.bj | S4 server | The old records |
One certificate covers every *.monentreprise.bj name. A new install obtains the first certificate over port 80; the present system renews through the DNS provider, so whoever manages DNS must be able to do that.
5 · Software and access
The platform is installed by a single installer, which checks the machine before it starts.
What you need to provide
- Operating system
- Ubuntu Server 24.04 LTS, 64-bit. MongoDB cannot run on the 26.04 kernel, so 24.04 is the version to install.
- Processor
- x86-64 with AVX. MongoDB will not start without AVX. ARM processors are not supported.
- Disks and swap
- ext4 file systems, and 32 GB of swap on the V4 server.
- Access
- An administrator account that can use
sudo, reachable over SSH. - DNS
- Control of the zone that holds the names in section 4, to create the records and to obtain and renew the certificate.
- A mail relay for notifications: server, port, username and password. The platform sends its mail through an outside provider today, and that arrangement does not transfer with the systems.
- Installer minimum
- 4 processors, 8 GB of memory, 100 GB of disk. The sizes in section 1 are well above this floor.