Upgrade to Django 3.2 LTS and Dockerize junction#757
Merged
ananyo2012 merged 20 commits intomasterfrom Jun 15, 2023
Merged
Conversation
…Fix (#744) * Upgrade Python Version to 3.10 and Django Version 3.2 * Fix Github and Google Login/Signup * new package added to the requirements file * using f-strings Co-authored-by: @rohitchopra-epam
* Fix failing tests, Add gunicorn Added nox method for running gunicorn * Pin dependencies --------- Co-authored-by: Ananya Maiti <Ananya_Maiti@epam.com>
* Initial commit for Dockerization * Fix review comments and dockerignore * Update dev.py.sample with runsslserver * Fixes for using default settings module * Remove Dockerfile.celery and use image from junction web image * Update docker-compose.test.yml to not depend on postgres db * Add static asset compilation in Docker image * Add docker-compose.prod.yml and update server port configuration in application * Add social oauth env vars --------- Co-authored-by: Sanchit Balchandani <balchandani.sanchit@gmail.com> Co-authored-by: Ananya Maiti <Ananya_Maiti@epam.com>
sayatul
reviewed
Apr 25, 2023
261f1b7 to
76b20d6
Compare
76b20d6 to
4b238c6
Compare
sayatul
reviewed
Apr 27, 2023
Contributor
|
@ananyo2012 - now that we have seen issues while testing junction, maybe we could park this PR and merge only when all such issues are fixed? |
Contributor
Author
@inovizz Yes we can keep this on hold. But we do need to complete the upgrade soon so that others can consume the changes for junction upgrade. In the current stage we have to pretty much point everyone to this branch. |
ee5d1c6 to
0f79d8c
Compare
Fix userprofile dashboard url
0f79d8c to
f24de39
Compare
Add review_comments=False for default comment view for logged in user
…opdown in add form
Co-authored-by: Rajat Rajdeep <rajat.rajdeep@avasant.com>
* Update Devlopment setup docs * Instructions for setting up junction using Docker post junction upgrade. (#761) * Added instructions in the ReadMe file for setting up junction using Docker post junction upgrade. * Updated the psycopg version to resolve - SCRAM authentication requires libpq version 10 issue. --------- Co-authored-by: Rajat Rajdeep <rajat.rajdeep@avasant.com> --------- Co-authored-by: Ananya Maiti <Ananya_Maiti@epam.com> Co-authored-by: Rajat Rajdeep <46029666+RajatRajdeep@users.noreply.github.com> Co-authored-by: Rajat Rajdeep <rajat.rajdeep@avasant.com>
Contributor
|
@ananyo2012 - we could plan a sprint and complete open issues related to this PR. |
inovizz
approved these changes
Jun 15, 2023
Contributor
|
Great work @ananyo2012 as usual. 🚀 |
This was referenced Jun 15, 2023
Closed
Member
|
Really great work on this everyone! ❤️ |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR aims to resolve the long pending junction upgrade to Django LTS version and support Python3 in production
We have also Dockerized junction for enabling cross platform setup and using docker for production deployment.
Thanks to @Bhandari423, @inovizz, @rohitchopra-epam for their efforts for their constant efforts and completing this gigantic task
Closes #611, #614, #730