clintonb / cookiecutter-django Goto Github PK

https://www.django-rest-framework.org/

http://mypy-lang.org/

The Travis build will inevitably have memory issues. These have been fixed by openoakland/woeip#9 and openoakland/woeip#12. Incorporate those changes here.

https://docs.djangoproject.com/en/2.1/topics/auth/passwords/#using-argon2-with-django

Media files should go to a cloud provider (e.g. S3). django-storages should solve this problem.

If the application is behind a CDN (e.g. CloudFront), the webserver (nginx) can serve static files and rely on the CDN to cache them. While we can use S3 to store the files, doing so might be a bit more cumbersome at deployment time with the need to run collectstatic after each deployment. There is also no good way to cleanup old files over time.

Remaining Work

• Add django-storages to serve uploaded media files
• Add Terraform to put files behind CloudFront CDN

https://codecov.io/

https://docs.travis-ci.com/user/deployment/elasticbeanstalk/

We should use --deploy when calling pipenv install to ensure that Pipfile and Pipfile.lock are not out-of-sync. Make sure CI fails if these files are out-of-sync, too.

Description

Open Oakland attracts developers of all experience levels. Many, if not all, tools will be foreign to developers looking to use the cookiecutter template. There should be a way for new users to be guided through the technology behind the repository.

Solution

Create a wiki page that briefly describes core concepts, curates links to relevant tutorials, and provides more detailed command line instructions.

Add Terraform configuration for project hosting.

Consider using https://github.com/pennersr/django-allauth.

Description

It appears this project is intended to be a tool for Open Oaklanders to develop their projects. Volunteers should be able to find it in a location owned by the organization.

Request

Have the OpenOakland github organization contain either a base or forked version of the repository, once it has matured.