Skip to content

Add HTTPS support and replace the legacy release workflow - #106

Merged
Paul2803k merged 5 commits into
developmentfrom
feature/https-release
Sep 24, 2026
Merged

Paul2803k merged 5 commits into
developmentfrom
feature/https-release

Conversation

@Paul2803k

@Paul2803k Paul2803k commented Sep 24, 2026 •

Copy link
Copy Markdown
Collaborator

This PR adds HTTPS support to SOARCA-GUI, replaces the Go-based release workflow, and includes the manual-action fixes from one of my old branches. It was not super necessary but let's keep it as a baseline.

In details for the HTTPS support, changes include:

  • Add optional HTTPS support to the Vite development and preview servers.
  • Load the certificate and private key from configurable paths.
  • Allow Vite to proxy requests to an HTTPS SOARCA backend.
  • Configure production Nginx to serve the GUI over HTTPS.
  • Configure Nginx to proxy API requests to an HTTPS backend.
  • Mount certificates into the development and production containers.
  • Update the relevant doc.

Allow Vite and Nginx to serve the GUI over HTTPS while keeping backend certificate verification configurable for local self-signed certificates.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was linked to issues Sep 24, 2026
@Paul2803k Paul2803k changed the title feature: add https support Add HTTPS support and replace the legacy release workflow Sep 24, 2026
@Paul2803k
Paul2803k force-pushed the feature/https-release branch from 8906e17 to 9c87f28 Compare September 24, 2026 12:19
Comment thread .github/workflows/ci.yml
tags: cossas/soarca-gui:pr-${{ env.describe_version }}
build-args: |
VERSION=${{ env.describe_version }}
VITE_APP_VERSION=${{ env.describe_version }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason to not use plain version?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we use it to later on inject it into the build of the app and it needs to start with VITE_ to be used.

Comment thread .github/workflows/release.yml Outdated
push: true
target: production
tags: |
cossas/soarca-gui:${{ github.ref_name }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be the describe version right? This is consistent over all Github and non Github describe.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also it keeps it consistent with the CI build

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah yes, it should be the same tho no? as this is triggered by the pushed tag. But for consistency i will bring back the old thing

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should, but is not guaranteed if we change release process.

Comment thread nginx.conf Outdated
@Paul2803k
Paul2803k merged commit 62496a9 into development Sep 24, 2026
5 checks passed
@Paul2803k
Paul2803k deleted the feature/https-release branch September 24, 2026 13:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐛 Fix release CI ✨ feature: support https in production

2 participants