IRIS System requirements: Unterschied zwischen den Versionen
Ddang (Diskussion | Beiträge) |
|||
(6 dazwischenliegende Versionen von 3 Benutzern werden nicht angezeigt) | |||
Zeile 1: | Zeile 1: | ||
[[de:IRIS_Systemvoraussetzungen]] | [[de:IRIS_Systemvoraussetzungen]] | ||
− | + | Here you can find the hardware and software requirements to run [[IRIS_cloud_system|IRIS]]. | |
− | + | Keep in mind that the requirements are not final yet. | |
− | === | + | ===Hardware requirements=== |
− | ==== | + | ==== At least ==== |
− | *1 | + | *1 core |
*1 GB RAM | *1 GB RAM | ||
− | *2 GB | + | *2 GB free memory on a SSD |
− | * | + | *internet connection |
− | ** | + | **public / static IP-address |
− | ** | + | **assigned and public DNS-entry |
− | ** | + | **at least 5 Mbit/s Upload |
− | ==== | + | ==== Mediocre capacity (up to 1.000 packages per hour) ==== |
− | *2 | + | *2 cores |
*2 GB RAM | *2 GB RAM | ||
− | *10 GB | + | *10 GB free memory on a SSD |
− | === Software- | + | === Software- and other requirements === |
− | ==== | + | ==== General ==== |
− | + | General requirements, regardless of the installation method. | |
− | * SMTP-Account ( | + | * SMTP-Account (authentification with OAUTH2 is possible) |
− | * | + | * public address / (Sub-)Domain |
− | ** | + | ** a separate domain or subdomain must exist |
− | ** | + | ** example: iris.firmenname.de or hvscloud.firmenname.de |
− | ** | + | ** not possible: firmenname.de/iris |
* Standard HTTP / HTTPS Ports: 80, 443 | * Standard HTTP / HTTPS Ports: 80, 443 | ||
− | * | + | * certificate for the HTTPS Server |
− | ** | + | ** from public certification body |
− | ** | + | ** self-signed certificates for the public HTTPS Server are not possible |
− | ==== Option 1: Docker | + | ==== Option 1: Docker ==== |
− | + | Additional information, when IRIS is operated by a Docker-Container. | |
− | * Docker | + | * Docker environment |
− | * | + | * willingness, to regulary update the Container. |
− | |||
− | ==== Option 2: Installation | + | ==== Option 2: Installation on your own operating system ==== |
− | + | Additional requirements, when the IRIS services are installed on an operating system. | |
− | * Reverse Proxy ( | + | * Reverse Proxy (for example IIS with ARR or nginx), configured with the Port and certificate from above |
− | * | + | * willingness to update several services (at the moment 2) regularly |
− | * | + | * own certification authority to create HTTPS certificates for our services (not to be confused with a public HTTPS Server) |
* MariaDB | * MariaDB | ||
− | ** | + | ** Databases: |
*** iris_common | *** iris_common | ||
*** iris_account | *** iris_account | ||
*** iris_shipping | *** iris_shipping | ||
− | *** [ | + | *** [further Databases possible at extension of IRIS] |
− | ** | + | ** database accounts |
− | *** | + | *** the User should be able to adjust the database structure and also the records. |
− | *** | + | *** for better security, every database should be provided with their own user. |
Aktuelle Version vom 16. November 2023, 13:09 Uhr
Here you can find the hardware and software requirements to run IRIS.
Keep in mind that the requirements are not final yet.
Hardware requirements
At least
- 1 core
- 1 GB RAM
- 2 GB free memory on a SSD
- internet connection
- public / static IP-address
- assigned and public DNS-entry
- at least 5 Mbit/s Upload
Mediocre capacity (up to 1.000 packages per hour)
- 2 cores
- 2 GB RAM
- 10 GB free memory on a SSD
Software- and other requirements
General
General requirements, regardless of the installation method.
- SMTP-Account (authentification with OAUTH2 is possible)
- public address / (Sub-)Domain
- a separate domain or subdomain must exist
- example: iris.firmenname.de or hvscloud.firmenname.de
- not possible: firmenname.de/iris
- Standard HTTP / HTTPS Ports: 80, 443
- certificate for the HTTPS Server
- from public certification body
- self-signed certificates for the public HTTPS Server are not possible
Option 1: Docker
Additional information, when IRIS is operated by a Docker-Container.
- Docker environment
- willingness, to regulary update the Container.
Option 2: Installation on your own operating system
Additional requirements, when the IRIS services are installed on an operating system.
- Reverse Proxy (for example IIS with ARR or nginx), configured with the Port and certificate from above
- willingness to update several services (at the moment 2) regularly
- own certification authority to create HTTPS certificates for our services (not to be confused with a public HTTPS Server)
- MariaDB
- Databases:
- iris_common
- iris_account
- iris_shipping
- [further Databases possible at extension of IRIS]
- database accounts
- the User should be able to adjust the database structure and also the records.
- for better security, every database should be provided with their own user.
- Databases: