Skip to content

Minimum Machine Requirements for SITMUN 3 #20

@fjlopez

Description

@fjlopez

Is your feature request related to a problem? Please describe.
Deploying SITMUN 3 involves running multiple components (front-end, back-end, and proxy/middleware), which can be containerized or installed directly on the host. Teams need clear guidance on the minimum CPU, RAM, and storage requirements to properly size a single machine—particularly for development, testing, or light production scenarios. Without this information, there’s a risk of underprovisioning (leading to performance issues) or overprovisioning (leading to wasted resources).

Describe the solution you'd like
A concise and official reference outlining recommended hardware specifications for running SITMUN 3, including:

  • CPU: Minimum number of cores (and potential differences between Linux and Windows hosts).
  • Memory: Recommended RAM for typical or higher loads.
  • Storage: Minimum required disk space, with guidelines on SSD vs. HDD.
  • OS requirements: Suitable Linux distributions (without a GUI), Windows with WSL2, etc.
  • Docker: Clarification on whether Docker is required, which version to use, and any license implications.

Describe alternatives you've considered

  • Conducting ad-hoc tests on various hardware setups to find workable configurations, which is time-consuming and inconsistent.
  • Reusing existing SITMUN 2 infrastructure without a clear sense of new requirements, potentially leading to suboptimal performance or unplanned downtime.

Additional context
Offering a range (e.g., minimum specs vs. recommended specs) can help cover different usage levels. Clear guidelines will also reduce guesswork and accelerate onboarding for teams migrating from SITMUN 2 to SITMUN 3 or new adopters unsure of what hardware environment to prepare.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions