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

Implement Continuous Integration Workflow for Vercel Auto-Deployment #34

Draft
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

snobbee
Copy link
Contributor

@snobbee snobbee commented May 31, 2024

  • Added a step in the Dockerfile to copy the .nvmrc file and use nvm to install the specified Node.js version, ensuring Node.js version compatibility.
  • Included Istanbul (nyc) in pyproject.toml under [tool.poetry.dev-dependencies] to enforce JavaScript test coverage thresholds.
  • Replaced .env file reference in docker-compose.yml with GitHub Secrets for enhanced secrets management.
  • Created and modified .github/workflows/deployment.yml to include deployment failure notifications via Slack, conditional deployment steps, caching of node modules, and a linting step with ESLint.
  • Introduced a new GitHub Actions workflow in .github/workflows/branch_protection_rules.yml for enforcing branch naming conventions and protecting the master branch.
  • Provided comprehensive documentation in .github/workflows/README.md for the CI/CD workflow, covering setup, configuration, and usage.
  • Modified the Dockerfile to integrate Prometheus for monitoring and Fluentd for logging, configured for Vercel deployments.

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.

1 participant