- Simplified the API service build configuration in `docker-compose.yml` by consolidating the build context and Dockerfile path.
- Added `diesel_migrations` dependency to `Cargo.toml` for database migration management.
- Implemented database migration logic in `main.rs`, including error handling and logging for migration success or failure.
- Introduced a new mail service in `supabase/docker-compose.yml` for handling SMTP, POP3, and web interface.
- Removed version specification from `supabase/dev/docker-compose.dev.yml` for cleaner configuration.
These changes improve the overall structure and functionality of the application, facilitating better database management and service orchestration.
- Modified SITE_URL from http://localhost:3000 to http://localhost:3003 to reflect the new local server configuration.
- Updated STUDIO_PORT from 3000 to 3003 to align with the updated local development environment.
These changes ensure consistency in the local development setup and prevent port conflicts.
- Consolidated Redis service into the main `docker-compose.yml`, removing the separate API Docker Compose file.
- Added health checks for Redis and API services to ensure proper service readiness.
- Updated API router to include a public health check endpoint.
- Cleaned up the web Dockerfile by removing unnecessary environment variable copying.
These changes enhance service orchestration and improve the reliability of the application during development.
- Removed version specification from `docker-compose.yml` for simplicity.
- Eliminated the `env_file` directive in the `web` service to streamline environment variable management.
- Updated the `Dockerfile` for the API to conditionally copy SSL certificates based on the environment, enhancing flexibility for local and production setups.
These changes aim to simplify the configuration and improve the development workflow.
- Expanded `.env.example` with additional environment variables for local development, including AWS credentials, database connection strings, and API keys.
- Removed the `api/.env.example` file as its contents have been consolidated into the main `.env.example`.
These changes enhance the local development setup by providing a comprehensive example of required environment variables.
- Updated `docker-compose.yml` to streamline environment variable management using `.env`.
- Temporarily disabled the `postgres` service for cleaner development.
- Enhanced the `rest` service configuration for better integration with Nessie, including updated image and port mappings.
- Cleaned up unused imports in `post_datasets.rs` to improve code readability.
These changes enhance the development environment and prepare for future integrations.
* pass width in different selectors
* tooltip updates
* add ability to disable tooltip
* pie minimum percentage must be passed down to legend update
* axis title must be truncated
* update to scatter with a
* scatter tooltip update
* scatter tooltip updates
- Updated `docker-compose.yml` to use `.env` for environment variables and modified the `rest` service configuration for the Nessie integration.
- Temporarily disabled the `postgres` service by commenting it out.
- Removed unused imports in `post_datasets.rs` to enhance code readability and maintainability.
These changes streamline the development environment and improve code quality.
- Updated the logic to determine final_permission by checking if permission is Some, simplifying the condition.
- Improved error handling for non-public threads when no permissions are provided.
- Updated the `docker-compose.yml` file to change the environment file path for services to use `.env` instead of `../.env`.
- Commented out the `postgres` service configuration to disable it temporarily.
- Updated the `rest` service to use the `ghcr.io/projectnessie/nessie` image, changed the container name to `nessie`, and modified the port mapping from `8181` to `19120`.
- Adjusted environment variables for the `rest` service to align with the new Nessie configuration.
These changes streamline the setup for the warehouse services and prepare for the integration of Nessie.
- Removed unused imports for `serde_json` and `tokio::task::JoinSet` in the `post_datasets.rs` file.
- This cleanup improves code readability and reduces unnecessary dependencies.
- Added new Dependabot configurations for npm packages in the /api and /web directories, scheduled for weekly updates with a limit of 10 open pull requests.
- Updated the GitHub Actions workflows for both main and staging deployments to trigger on changes within the api directory, specifically for migrations, improving deployment reliability.
These changes streamline dependency management and enhance the deployment process for the application.
- Added a new job for database deployment, including steps for installing Rust, configuring AWS credentials, downloading the Postgres certificate from S3, and running migrations.
- Updated the existing porter-deploy job to include AWS credentials configuration and SSL certificate download from S3.
- Improved organization and reliability of the deployment process by ensuring all steps are correctly defined and executed in the appropriate context.
These changes streamline the deployment workflow and enhance the overall reliability of the application deployment process.
- Added a working-directory specification for the 'Run migrations' step in the GitHub Actions workflow, ensuring that Diesel migrations are executed in the correct context within the './api' directory. This change enhances the reliability of the migration process during deployment.
- Changed the S3 URL variable for downloading the Postgres SSL certificate in the GitHub Actions workflow from `PG_CERT_S3_URL` to `CERT_S3_URL`.
- This update ensures the workflow correctly references the updated secret for SSL certificate retrieval, improving the reliability of the deployment process.
- Added steps to configure AWS credentials and download the Postgres SSL certificate from S3 in the GitHub Actions workflow.
- Updated the Dockerfile to reflect the new path for the SSL certificate, ensuring it is correctly copied to the container.
These changes improve the security and organization of SSL certificate handling during the deployment process.
- Changed the directory structure for SSL certificates in the GitHub Actions workflow, creating a new path `certs/cert` for better organization.
- Updated the Dockerfile to reference the new certificate path, ensuring the SSL certificate is correctly installed in the container.
These changes improve the clarity and maintainability of the deployment process.
- Updated the runner specification for the database-deploy job to correct the Ubuntu version format.
- Ensured consistency in the runner configuration for the porter-deploy job by reverting to the previous Ubuntu version.
These changes enhance the accuracy of the workflow configuration, ensuring proper execution of deployment jobs.
- Added steps to create a directory for SSL certificates and copy the downloaded certificate to the new location in the GitHub Actions workflow.
- Updated the Dockerfile to reference the new certificate path, ensuring proper installation of the SSL certificate in the container.
These changes improve the organization of SSL certificates and enhance the deployment process.
- Added support for pull requests targeting the staging branch to the existing workflow.
- This change improves the deployment process by ensuring that pull requests are also considered for staging deployments.
- Introduced a new job for database deployment, including steps to install Rust, cache dependencies, and run Diesel migrations.
- Updated the existing porter-deploy job to include AWS credentials configuration and SSL certificate retrieval from S3.
- Enhanced the overall structure and organization of the workflow for improved clarity and maintainability.
- Changed the directory for the buster-cli package from "/packages/buster-cli" to "/cli".
- Added a new configuration for the cargo package in the "/api" directory.
- Updated scheduling and branch settings for both packages to improve dependency management.
These changes streamline the dependency update process and enhance the organization of package configurations.
dal
dal
Nate Kelley
Nate Kelley
porter-deployment-app[bot]