CSSCurrent en:Requirements for Self Installed Systems: Unterschied zwischen den Versionen

Aus Cryptshare Documentation
Wechseln zu:Navigation, Suche
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 1: Zeile 1:
= Supported Operating Systems =
= Supported Operating Systems =
Cryptshare is a platform-independent solution that runs on Linux or Windows systems capable of running '''Java 17 (64 bit)'''.
Cryptshare is a platform-independent solution that runs on Linux or Windows systems capable of running '''Java 17 (64 bit)'''.
We support openSUSE, Ubuntu, and Windows Server. Other Linux distributions may use different basic commands and are therefore not supported.
We support openSUSE, Ubuntu, and Windows Server 2008 – 2016. Other Linux distributions may use different basic commands and are therefore not supported.


= Minimum Requirements =
= Minimum Requirements =

Version vom 26. August 2024, 12:38 Uhr

Supported Operating Systems

Cryptshare is a platform-independent solution that runs on Linux or Windows systems capable of running Java 17 (64 bit). We support openSUSE, Ubuntu, and Windows Server 2008 – 2016. Other Linux distributions may use different basic commands and are therefore not supported.

Minimum Requirements

  • CPU: Dual core or better
  • Memory: At least 4 GB
  • Free disk space:
    • Installation directory: At least 1 GB
    • Upload directory: Depends on several factors - the expected number of transfers per day, the expected average size for a transfer and the preferred average retention period for the transfers. Calculation example:
<minimum upload directory size> = <average transfer size> \* <average amount of transfers per day> \* <retention period> \*1.25

Optimum System Equipment / Sizing

We are happy to determine the optimum system resources for your system. For this some information about the expected system load is required:

  • Expected number of transfers per day
  • Expected average size for a transfer
  • Preferred average retention period for the transfers
  • Expected peak load (How many up,- and download operations shall the system be able to handle at maximum)