chore: add ci for web stag

[hiento09]

This pull request updates the CI/CD workflows for the Jan Web Server to better support multiple deployment environments (development, staging, and production) and improves the Docker build process to use environment-specific API base URLs. The changes include renaming workflow files for clarity, adding a new staging workflow, and ensuring environment variables are consistently passed into Docker builds and build steps.

Workflow environment separation and configuration:

• Added a new workflow file, jan-server-web-ci-stag.yml, to handle builds and Docker image pushes for the staging environment, including setting the JAN_API_BASE for staging and configuring image tagging and registry login.
• Renamed workflow files for clarity: the production workflow is now jan-server-web-cicd-prod.yml (from jan-server-web-ci-prod.yml), and the development workflow is now jan-server-web-ci-dev.yml (from jan-server-web-ci.yml). [1] [2]

Environment variable handling and Docker build improvements:

• Updated all workflows to explicitly set the JAN_API_BASE environment variable for their respective environments and to pass it as a build argument to the Docker build command, ensuring the correct API endpoint is used in each environment. [1] [2] [3]
• Updated the Dockerfile to define JAN_API_BASE as a build argument and environment variable, so it can be properly injected during image builds.
• Ensured that additional environment variables (e.g., GA_MEASUREMENT_ID) are passed to build steps in the production workflow for consistency and correct configuration.

---

Important

This PR updates CI/CD workflows for different environments and improves Docker build processes by adding a staging workflow, renaming existing workflows, and ensuring environment variables are correctly handled.

• Workflows:
  • Added jan-server-web-ci-stag.yml for staging builds and Docker image pushes, setting JAN_API_BASE for staging.
  • Renamed jan-server-web-ci-prod.yml to jan-server-web-cicd-prod.yml and jan-server-web-ci.yml to jan-server-web-ci-dev.yml for clarity.
• Environment Variables:
  • Set JAN_API_BASE in all workflows and passed as a build argument in Docker builds.
  • Passed additional environment variables like GA_MEASUREMENT_ID in production workflow.
• Dockerfile:
  • Added JAN_API_BASE as a build argument and environment variable.

^{This description was created by for 207f216. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 207f216 in 2 minutes and 31 seconds. Click for details.

• Reviewed 131 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. .github/workflows/jan-server-web-ci-prod.yml:28

• Draft comment:
  Remove the commented-out env vars block if it's no longer used to keep the workflow clean.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. .github/workflows/jan-server-web-ci-prod.yml:10

• Draft comment:
  Confirm that using 'ubuntu-latest' for production (versus 'ubuntu-24-04-docker' in other workflows) is intentional.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. .github/workflows/jan-server-web-ci-stag.yml:1

• Draft comment:
  Consider using 'staging' instead of the abbreviated 'stag' in the workflow name for better clarity.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

4. Dockerfile:4

• Draft comment:
  The default JAN_API_BASE ARG is set to the dev URL; ensure that staging/production builds properly override this value.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

5. Dockerfile:28

• Draft comment:
  Using 'COPY ./.* /' may inadvertently copy hidden or unwanted files; consider refining the copy pattern or using a .dockerignore.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_5gvpwiMMIboxzVHe

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}