feat: Add turborepo and Docker config #24
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add Docker support and switch to TurboRepo This update introduces Docker support for the Currencia application. A new Dockerfile has been added, along with docker-compose configuration for local development. The build process now uses two stages: a build stage and a final stage. The project's package.json scripts have been updated to use TurboRepo commands instead of bun, reflecting a shift in the build tooling. This includes changes to dev, lint, and other script commands. A turbo.json file was also introduced to manage tasks related to building, generating, developing, and testing the application using TurboRepo. Lastly, an example .env file was added for setting up environment variables in Docker.
Introduced a new GitHub Actions workflow to automatically build and push Docker images for the application. The workflow triggers on pushes to main branch, tag creation, or manual dispatch. It checks for changes in specific paths before proceeding with the build. Updated .gitignore to ignore .turbo files. Modified Dockerfile of the currencia app to include DATABASE_URL as an argument and environment variable. Also adjusted the build steps and added installation of curl. Adjusted nuxt.config.ts file to allow setting NITRO_PRESET from environment variables. Updated docker-compose.local.yml file to include database service configuration for local development. Added a new script "build:app" in package.json for building only the currencia app.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 14476214 | Triggered | Generic Password | d0839b2 | docker/docker-compose.local.yml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
|
Thank you for following the naming conventions! 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to automate the build and deployment process using Docker and Turbo, as well as updates to configuration files and scripts. The most important changes include the addition of a GitHub Actions workflow for building and pushing Docker images, the creation of a multi-stage Dockerfile, and updates to the build and development scripts.
Automation and CI/CD:
mainbranch or when a new tag is created. This workflow includes steps to check for changes, set up Docker, and build and push the Docker image. (.github/workflows/build-app-image.yml)Docker and Environment Configuration:
currenciaapplication, which includes a build stage using theoven/bunimage and a final stage for running the application. (apps/currencia/Dockerfile)NUXT_PUBLIC_SITE_URLvariable. (docker/.env.example)currenciaapplication and a PostgreSQL database. (docker/docker-compose.local.yml)Build and Development Scripts:
package.jsonscripts to use Turbo for various tasks such as development, building, linting, and testing. (package.json)turbo.jsonconfiguration file to define global dependencies and task configurations for Turbo. (turbo.json)Configuration Updates:
apps/currencia/nuxt.config.ts)