Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

82 feature request suggestion create GitHub actions workflow for automating the build and deployments for feature branches #87

Draft
wants to merge 54 commits into
base: main
Choose a base branch
from

Conversation

lmcdonough
Copy link
Contributor

This pull request introduces a new GitHub Actions workflow to build and deploy Docker containers for Rust and Next.js projects. The workflow includes steps for building, testing, and pushing Docker images to the GitHub Container Registry.

GitHub Issue: [Closes] #82

Changes

  • Added a new Github Actions workflow configuration file .github/workflows/build_and_deploy_containers.yml to automate the build and deployment process for feature branches and pull requests to the main branch.
  • Defined two main jobs: build_test_run for building and testing the project, and build_and_push_docker for building and pushing Docker images. The latter job depends on the successful completion of the former.
  • Configured steps to checkout the repository, install the Rust toolchain, use cached dependencies, install seaORM CLI, build the project, and run tests.
  • Configured steps to checkout the repository, log in to the GitHub Container Registry, set up Docker Buildx, cache Docker layers, and build and push Docker images for both the Rust backend and the Next.js frontend.
  • Implemented a caching mechanism for Docker layers to optimize the build process, including steps## Description

Testing Strategy

  • Manually use the workflow_dispatch to iterate and view any errors from the workflow run.

Concerns

  • Managing environment variables, and secrets can be improved upon in the future.

@lmcdonough lmcdonough self-assigned this Dec 13, 2024
@lmcdonough lmcdonough requested a review from jhodapp December 13, 2024 19:56
@lmcdonough lmcdonough added the feature work Specifically implementing a new feature label Dec 13, 2024
lmcdonough and others added 21 commits December 14, 2024 19:01
… with updated actions, improved environment variable handling, and added artifact attestations for images.
…rams. Also accept a list of CORS allowed origin URLs instead of hardcoding them.
…tions are set and passed from the backend/docker-compose.yaml
calebbourg and others added 29 commits February 7, 2025 21:00
There is a lot of duplicated code here. The plan is to defer refactoring for now and
take a look at a better error handling system.
Improving the bug reporting template.
From README:
Layer of abstraction above `entity_api` and intended to encapsulate most business logic. Ex. interactions between `entity_api` and network calls to the outside world.
I will be extending this pattern and using code does not quite fit in my mind
Considering a record not found as an Error to improve upstream ergonomics
Clap was complaining and just having a -t seems not super expressive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature work Specifically implementing a new feature
Projects
Status: 🏗 In progress
3 participants