Build Artifacts for SITMUN 3 Deployment Outside of Docker #18
Description
Is your feature request related to a problem? Please describe.
Certain environments require deploying SITMUN 3 without using Docker in production. Moreover, the artifacts (front-end static files and back-end services) need to be run on IIS (Internet Information Services). This calls for an alternative build process that still leverages Docker in development/CI, but produces outputs suitable for IIS deployment.
Describe the solution you'd like
A new or modified build pipeline that uses Docker only for compilation and packaging. After that process, it should export:
- Static front-end assets, which IIS can serve directly.
- Back-end services (Java .war or .jar) that can be integrated into IIS (or a compatible Java server behind IIS).
Describe alternatives you've considered
- Running Docker in production environments anyway, which may clash with institutional policies or technical constraints.
- Manually building SITMUN 3 on local machines, which can lead to inconsistent environments and more complex deployments.
Additional context
By providing a clear path to generate IIS-friendly artifacts from Docker builds, more organizations can adopt SITMUN 3 without being forced to containerize the production environment. This approach also ensures standardization and easier integration with existing IIS-based deployment pipelines.