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

chore(conf): migrate production static storage to GCS buckets #62

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

kennedykori
Copy link
Contributor

Migrate the production static storage from the local filesystem to a Google Cloud Storage bucket. Other changes included are:

  • Change the deployment process to also perform database migrations and collect static files. The prior implementation would perform this during container startup which would in turn lengthen the container startup by a few more seconds.
  • Change environment loading behaviour in production to first load the environment variables from a .env file if a path to one was provided. If not, load the environment variables from the GCP Secret Manager service. If neither of these is successful, fail with a descriptive error message.

Included also are other minor improvements and fixes.

@kennedykori kennedykori force-pushed the chore-migrate-gcloud-run-static-storage branch 5 times, most recently from 3b78a55 to b3b81a2 Compare April 4, 2023 16:28
@kennedykori kennedykori self-assigned this Apr 4, 2023
@kennedykori kennedykori requested a review from saladgg April 4, 2023 18:49
Migrate the production static storage from the local filesystem to a Google Cloud Storage bucket. Other changes included are:

- Change the deployment process to also perform database migrations and collect static files. The prior implementation would perform this during container startup which would in turn lengthen the container startup by a few more seconds.
- Change environment loading behaviour in production to first load the environment variables from a `.env` file if a path to one was provided. If not, load the environment variables from the GCP Secret Manager service. If neither of these is successful, fail with a descriptive error message.

Included also are other minor improvements and fixes.
@kennedykori kennedykori force-pushed the chore-migrate-gcloud-run-static-storage branch from b3b81a2 to 1b03c30 Compare April 4, 2023 19:49
@saladgg saladgg merged commit 7f96982 into develop Apr 5, 2023
@saladgg saladgg deleted the chore-migrate-gcloud-run-static-storage branch April 5, 2023 03:14
kennedykori added a commit that referenced this pull request Apr 5, 2023
Migrate the production static storage from the local filesystem to a Google Cloud Storage bucket. Other changes included are:

- Change the deployment process to also perform database migrations and collect static files. The prior implementation would perform this during container startup which would in turn lengthen the container startup by a few more seconds.
- Change environment loading behaviour in production to first load the environment variables from a `.env` file if a path to one was provided. If not, load the environment variables from the GCP Secret Manager service. If neither of these is successful, fail with a descriptive error message.

Included also are other minor improvements and fixes.
github-actions bot pushed a commit that referenced this pull request Apr 5, 2023
## [1.6.2](v1.6.1...v1.6.2) (2023-04-05)

### Bug Fixes

* GCS blobs signed URLS generation ([#61](#61)) ([56209d9](56209d9))

### Dependency Updates

* **deps:** update node dependencies ([#60](#60)) ([3a7eca4](3a7eca4))

### Refactors

* **conf:** migrate production static storage to GCS buckets ([#62](#62)) ([fd816c8](fd816c8))
* **conf:** update storages configuration ([#63](#63)) ([70b6244](70b6244)), closes [/docs.djangoproject.com/en/4.2/releases/4.2/#psycopg-3](https://github.com/savannahghi//docs.djangoproject.com/en/4.2/releases/4.2//issues/psycopg-3)
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.

2 participants