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

Dockerize Junction and related components #680

Closed
3 tasks
palnabarun opened this issue Jun 5, 2020 · 7 comments
Closed
3 tasks

Dockerize Junction and related components #680

palnabarun opened this issue Jun 5, 2020 · 7 comments

Comments

@palnabarun
Copy link
Member

palnabarun commented Jun 5, 2020

Services to be run

  1. Postgres 12
  2. Redis 6
  3. Web application on Python 3
  4. Celery workers on Python 3

Additional system-wide config

  1. Nginx rule to reverse proxy traffic to the containers
  2. Co-ordinate config management for production

Follow Up

  • Remove Python 2.7 from CI
  • Remove other sunsetted Python versions from support (if any)
  • Upgrade to Django 2.2 LTS and fix all dependency issues (Django version bump #684)
@onlinejudge95
Copy link

onlinejudge95 commented Jun 5, 2020

I can take it if it helps ease the burden. I have experience doing dockerization in python

@palnabarun
Copy link
Member Author

palnabarun commented Jun 5, 2020

@onlinejudge95 -- Thanks for the help! You can get started with the port to Django 2.2 LTS.

There will some major breaking changes though. Please feel free to create a new umbrella issue for tracking the work.

@onlinejudge95
Copy link

Will raise a PR by weekend

@onlinejudge95
Copy link

onlinejudge95 commented Jun 6, 2020

@palnabarun meanwhile can you provide clarity on Remove other sunsetted Python versions from support (if any). This can go independent(to some extent, corner cases being the dependencies in this project having a hard limit) just like 2.7 one.

As far as upgrade goes I will be removing the Draft PR and starting from scratch. WIll ping about the same in the issue #684

@palnabarun
Copy link
Member Author

meanwhile can you provide clarity on Remove other sunsetted Python versions from support (if any).

By that I mean 3.5 is going to be EOL on 2020-09-13, IIRC. We should target 3.6+ for CI and production.

As far as upgrade goes I will be removing the Draft PR and starting from scratch. WIll ping about the same in the issue #684

Sure.

@pradyunsg
Copy link
Contributor

TBH, given that there's only 1 deployment that we know of, it might be a good idea to to push for 3.8+ compatibility.

@ananyo2012
Copy link
Contributor

This is complete now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants