setting_up_msupply:client_server_faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
setting_up_msupply:client_server_faq [2023/07/31 23:25] – [2) Client Server Connection Window] Nick Pendergrastsetting_up_msupply:client_server_faq [2024/11/21 23:38] (current) – [mSupply Server Requirements] Nick Pendergrast
Line 16: Line 16:
   * 4 cores minimum   * 4 cores minimum
  
-**STORAGE:** +**DRIVES:** 
-  * 100GB minimum allocated for mSupply backups (preferably on an additional volume rather than on the main drive)+  * Root drive: 100GB min  
 +  * Data Backup: 100GB minimum allocated for mSupply backups (preferably on an additional volume rather than on the root drive)
  
 **NETWORK:** **NETWORK:**
Line 25: Line 26:
   * We can provide remote daily datafile backups to Backblaze cloud storage. We utilise an application on the server to encrypt all data before sending to the cloud storage so your is safe. This service will require urls to be whitelisted if your server restricts outbound traffic   * We can provide remote daily datafile backups to Backblaze cloud storage. We utilise an application on the server to encrypt all data before sending to the cloud storage so your is safe. This service will require urls to be whitelisted if your server restricts outbound traffic
  
-===== Ports & Firewall Configuration =====+===== Port & Firewall Configuration =====
  
 === Central Sync Server === === Central Sync Server ===
Line 34: Line 35:
 | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) | | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) |
 | TSPlus Remote Web Kiosk | TCP 443 | HTTPS | Public | if running TSPlus for remote kiosk access to mSupply Client on the server | | TSPlus Remote Web Kiosk | TCP 443 | HTTPS | Public | if running TSPlus for remote kiosk access to mSupply Client on the server |
 +| SSL renewal | TCP 80 | HTTPS | Public | Required for automatic SSL renewal via ACME http challenge (no other web traffic will use this port) |
 +| mSupply ColdChain API | TCP 8090 | HTTPS | Public | For mSupply ColdChain API (if used) |
 | mSupply Application Server | TCP 19812, 19813, 19814 | | Local | mSupply Client connections to mSupply application server over LAN | | mSupply Application Server | TCP 19812, 19813, 19814 | | Local | mSupply Client connections to mSupply application server over LAN |
-| mSupply Client broadcast | UDP 49157 to 65535 | | Local | mSupply clients will automatically broadcast on the local network over this UDP port range to find the mSupply server |+| mSupply broadcast | UDP 49157 to 65535 | | Local | mSupply will automatically broadcast on the local network over this UDP port range to find the mSupply server |
  
-=== Central Server with no syncing remote sites ===+=== mSupply Server (Central or Remote) with no syncing remote sites ===
  
 All mSupply Client applications connect to the server over the LAN. There are no remote sites that need to sync to the central server. All mSupply Client applications connect to the server over the LAN. There are no remote sites that need to sync to the central server.
Line 51: Line 54:
 ===== Separate Dashboard Server Instance ===== ===== Separate Dashboard Server Instance =====
  
-The mSupply Dashboard application uses a PostgreSQL database. It may be advisable to run the Dashboard and Postgres server on a separate server instance from the mSupply server so that each instance can be configured specifically for the application that it is running, and so server resources required by Postgres do not interfere with the smooth functioning of mSupply Server.+The mSupply Dashboard application uses a PostgreSQL database. It may be advisable to run the Dashboard and Postgres servers together on a separate server instance from the mSupply server so that each instance can be configured specifically for the application that it is running, and so server resources required by Postgres do not interfere with the smooth functioning of mSupply Server.
  
 If mSupply Dashboards and PostgreSQL are running on a separate server instance to the mSupply Server the following configuration will be required for the dashboard server: If mSupply Dashboards and PostgreSQL are running on a separate server instance to the mSupply Server the following configuration will be required for the dashboard server:
  
 ^ Service ^ Allow Port ^ Protocol ^ Network ^ Requirement ^ ^ Service ^ Allow Port ^ Protocol ^ Network ^ Requirement ^
-| PostgreSQL | TCP 5432 | HTTP | Local | export of data from the mSupply db to the Postgres dashboard db  |+| PostgreSQL | TCP 5432 |  | Local | export of data from the mSupply db to the Postgres dashboard db  |
 | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) | | mSupply Dashboards | TCP 3000 | HTTPS | Public | mSupply Dashboard server traffic (if dashboards are to be accessible from the internet) |
  
Line 75: Line 78:
 === 1) Client configuration file === === 1) Client configuration file ===
  
-After mSupply Client has been installed edit the EnginedServer.4Dlink found at this path **C:\mSupply client\Database** using notepad. Replace **<SERVER IP ADDRESS>** in the code below with the Server IP. This same file edited file can then be deployed to this folder of all the mSupply Client installations on this LAN.+After mSupply Client has been installed edit the EnginedServer.4Dlink found at this path **C:\mSupply client\Database** using notepad. Replace **<SERVER IP ADDRESS>** in the code below with the Server IP. This same edited file can then be deployed to the client database folder of all the mSupply Client installations on this LAN.
  
 <code> <code>
  • Last modified: 2023/07/31 23:25
  • by Nick Pendergrast