Docker file setup #212
Open
Docker file setup #212
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
…ackage.json accordingly.
- Introduced Docker Compose configuration for PostgreSQL service. - Added package-lock.json and updated package.json with AWS SDK dependencies. - Created new dashboard layout with navigation for spaces and file uploads. - Implemented spaces management with user authentication and access control. - Developed API routes for file uploads, downloads, and management. - Added S3 integration for file storage and retrieval. - Documented architecture and implementation plans in the docs directory.
- Introduced multiple markdown files outlining best practices for authentication, database management, development workflow, file uploads, Next.js conventions, project structure, space management, and UI components. - Each file includes key files, code examples, and guidelines to ensure consistency and maintainability across the project.
- Added comprehensive end-to-end testing suite using Playwright, including global setup and teardown scripts. - Implemented various test cases for authentication, dashboard functionality, file uploads, and API integration. - Updated project documentation to include testing guidelines and structure. - Refactored middleware and session management for improved authentication flow. - Introduced new S3 client configuration for local testing and production environments. - Updated README and other documentation to reflect recent changes and enhancements.
- Added new Playwright test scripts for comprehensive file upload and download scenarios, including validation of metadata and error handling. - Introduced helper functions for file creation and cleanup to streamline test setup. - Updated Playwright configuration for local development and testing environments. - Refactored login component to ensure proper handling of search parameters. - Improved session management by providing a fallback for the authentication secret. - Added shell scripts for running file tests and setting up environment variables.
Feat/playwright_tests
- Added new activity types for file uploads, downloads, and deletions in the dashboard. - Updated the activity formatting function to include messages for the new file actions. - Refactored login actions to generate a team slug and S3 prefix during team creation. - Modified API routes to handle promises for parameters, improving type safety and consistency. - Updated user ID handling in various API routes to use string instead of integer for better compatibility.
- Added .env.production to .gitignore for better environment management. - Refactored middleware configuration by removing the runtime property. - Updated Next.js and React dependencies in package.json and package-lock.json to use caret (^) for versioning. - Introduced tailwind.config.js for Tailwind CSS setup. - Modified npm scripts in package.json for improved development and production workflows. - Fixed parameter destructuring in the download route for better clarity.
- Added trailingSlash and unoptimized image settings to next.config.ts to address deployment issues on Vercel. - Introduced vercel.json to define build commands and function runtimes for better integration with Vercel's platform.
- Simplified vercel.json by removing the functions property, streamlining the deployment configuration for Next.js.
- Added function runtime settings for TypeScript API routes in vercel.json to ensure compatibility with Node.js 22.x during deployment.
- Deleted vercel.json to eliminate the build command and function runtime settings, simplifying the deployment configuration for Next.js.
… environment variables - Added support for Microsoft 365 authentication, including new actions and routes for handling OAuth flow. - Updated environment variables to replace AWS credentials with S3-specific variables for better clarity and consistency. - Refactored various components and documentation to reflect the new project name "Sunlighten - Partner Storage" and its features. - Enhanced testing suite to cover new authentication flows and updated test scripts accordingly. - Updated database schema to accommodate Microsoft user integration and modified seeding scripts for initial data setup.
- Refactored Microsoft authentication functions to handle missing credentials gracefully and ensure proper error handling. - Updated the sign-up page to redirect users to the sign-in page, indicating that sign-up is currently disabled. - Enhanced the getMicrosoftAuthUrl function to return a promise and improved the handling of the authentication callback.
- Introduced amplify.yml for build and deployment configuration in AWS Amplify. - Added amplify-config.ts for managing environment variables and secrets. - Implemented debug-env.ts and env.ts for logging environment variables in production. - Enhanced database and S3 configuration handling with error management. - Updated layout.tsx to include debugging of environment variables during production.
- Added .npmrc for AWS Amplify NPM configuration. - Updated Tailwind CSS to version 3.4.0 and adjusted related dependencies. - Refactored PostCSS configuration to use the new Tailwind CSS plugin structure. - Enhanced Tailwind configuration with new color and border radius settings. - Cleaned up globals.css by removing legacy styles and integrating Tailwind's utility classes.
…on handling - Added AWS Amplify secrets management integration in amplify-secrets.ts for loading environment variables and secrets. - Updated getDatabaseUrl and getS3Config functions to utilize the new secrets management system. - Refactored imports in drizzle.ts and local-config.ts to source configurations from amplify-secrets.ts instead of amplify-config.ts. - Created documentation for AWS Amplify environment variables setup and troubleshooting.
- Introduced a new configuration system in amplify-gen2-config.ts for managing environment variables and secrets in AWS Amplify Gen 2. - Updated existing modules to utilize the new configuration system, including drizzle.ts and local-config.ts. - Added detailed debug logging and troubleshooting steps for environment variable issues in amplify-secrets.ts. - Created comprehensive documentation for AWS Amplify Gen 2 configuration in AWS_AMPLIFY_GEN2_CONFIGURATION.md.
…ment and troubleshooting documentation - Added a complete solution guide for AWS Amplify environment variables, detailing common issues and fallback strategies. - Implemented a new runtime environment handler to ensure graceful handling of missing environment variables. - Created a troubleshooting guide to assist users in resolving configuration issues with AWS Amplify. - Updated relevant modules to utilize the new environment variable management system, enhancing error handling and debug logging.
…cumentation - Removed outdated environment variable handlers and documentation related to AWS Amplify. - Updated layout.tsx to eliminate the debug environment variable function call. - Consolidated environment variable management into a single source of truth, enhancing code clarity and maintainability. - Created a cleanup summary document to outline changes and next steps for deployment.
- Add AWS Amplify secrets support for secure credential management - Create lib/auth/amplify-config.ts with secret definitions and configuration - Update lib/auth/microsoft.ts to use async secret loading with better error handling - Enhance lib/amplify-runtime-env.ts with Azure AD secrets support - Add comprehensive documentation in docs/AWS_AMPLIFY_SECRETS_INTEGRATION.md - Update docs/AZURE_AD_SETUP.md with AWS Amplify secrets option - Install @aws-amplify/backend package for secrets management - Update production URLs across documentation files Security improvements: - Centralized secret management in AWS Amplify - Encryption at rest using AWS KMS - Better access control and audit logging - Easy secret rotation without code changes - Maintains backward compatibility with environment variables
updated missing libraries
made changes to fix deployment issues
updated ampilfy.yml file
|
@Tejesh-Duvvuru is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.