Tutorial: Connect Vercel Previews to Signadot Sandboxes for Full-Stack Preview Environments #66
Conversation
This file contains hidden or 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
…end service, CI/CD workflows, and documentation. Introduced .gitignore, Dockerfile, Kubernetes deployment/service configurations, and a comprehensive README tutorial for connecting Vercel previews to Signadot sandboxes.
- Created .gitignore to exclude unnecessary files and directories. - Added README.md with a comprehensive tutorial for connecting Vercel previews to Signadot sandboxes. - Introduced Signadot sandbox template and configuration files for backend deployment. - Implemented CI/CD pipeline for building and pushing Docker images for the backend service. - Established Kubernetes deployment and service configurations for the backend application.
…eployment - Introduced backend CI/CD pipeline for building and pushing Docker images on pull requests and pushes to main/master branches. - Added full-stack preview deployment workflow to create Signadot sandboxes and deploy frontend to Vercel, including commenting preview URLs on PRs. - Configured AWS credentials and Signadot CLI for sandbox management.
- Introduced .dockerignore to exclude unnecessary files from Docker builds. - Updated config.js to clarify environment variable usage. - Refined Dockerfile for better dependency management and security practices. - Added Kubernetes deployment and service configurations for the backend application. - Enhanced CI/CD workflow to include deployment to EKS and Signadot sandbox management.
- Cleaned up ESLint, Next.js, and PostCSS configuration files by removing unnecessary newlines. - Updated TypeScript configuration to include additional file types and improved include paths. - Enhanced GitHub Actions workflow for Signadot sandbox management, including better error handling and verification steps. - Modified frontend layout and home page content for improved clarity and user guidance. - Added new SVG assets for branding and favicon. - Streamlined API proxy route documentation and functionality.
- Modified sandbox-template.yaml to replace variable placeholders with static names for better clarity. - Updated deployment.yaml to remove unnecessary comments and clarify the image override process for Signadot sandboxes. - Cleaned up service.yaml by removing redundant comments, streamlining the configuration for the Kubernetes service.
…ence before deploying to Kubernetes
…integration tutorial - Streamlined instructions for connecting Vercel previews to Signadot sandboxes. - Updated prerequisites and configuration details for backend and frontend setups. - Enhanced workflow steps for creating and deploying sandboxes, including security best practices for API keys. - Improved troubleshooting section for common issues related to sandbox creation and API calls.
- Expanded introduction to clarify the problem and solution for Vercel previews and Signadot sandboxes. - Updated prerequisites section with a detailed table for clarity. - Improved step-by-step instructions for backend and frontend configurations, including sandbox deployment and API proxy setup. - Enhanced troubleshooting section with specific checks for common issues. - Streamlined overall content for better readability and user guidance.
…ment - Added an image to illustrate the GitHub Action PR comment containing preview links for frontend and backend URLs. - Improved clarity in the instructions for finding the PR comment in the Vercel and Signadot integration tutorial.
- Clarified instructions for configuring the frontend to read the backend URL from environment variables, applicable to any framework with build-time env support. - Added detailed steps for installing the Signadot Operator manually if not using the backend CI job with `SIGNADOT_CLUSTER_TOKEN`. - Included a note on enabling the optional `deploy-to-eks` job in the backend CI workflow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.