Alternatives
Products that do what Pre-configured Django project, Git repo, and virtualenv with 1 command does
- 1VM
2018 · docs.vespene.io
- 2AS
2012 · github.com
- 3MA
2015 · blog.tryolabs.com
- 4PR
2016 · github.com
- 5PV
2019 · github.com
- 6BD
2014 · github.com
- 7VA
2014 · pypi.python.org
- 8GT
2017 · gitorials.com
- 9HA
2017 · github.com
- 10ID
2013 · pythonhosted.org
- 11GG
2015 · github.com
- 12LP
2016 · github.com
- 13AA
2019 · github.com
- 14US
2020 · github.com
- 15CF
2017 · djangoappschecklist.com
- 16AA
2018 · arcamens.com
- 17DF
2017 · github.com
- 18GA
2018 · github.com
- 19WO
We had a lot of reasons we wanted to build our own help desk, the least of which (and easiest to mention) is that a three seat license to the top tier desk systems are well over $100/mo. Plus they were slowing us down quite a bit. Right now its only dependency is Django, it supports email alert for updates, has bundled style, a permission like public/private/internal status, optional anonymous questions/responses, categories, searching, and a few more I've missed. What I'd like to do is: extend tests, class based views, parse incoming emails as questions & response (this is important for…
2012
- 20IG
2021 · imagine.ai
- 21DK
After a decade of shipping Django to production, I got tired of solving the same setup problems on every new project. Environment-first settings. Sensible auth defaults. Structured logging. CI from day zero. Pre-commit hooks. Docker. Security hardening. Every project meant two days of boilerplate before writing business logic. So I built Django Keel: a production-ready Django starter that eliminates the yak-shaving. GitHub: https://github.com/CuriousLearner/django-keel *What you get*: - 12-factor config with environment-based secrets - Production-hardened security…
Oct 2025 · github.com
- 22GV
2016 · github.com
- 23GP
2013 · github.com
- 24GF
2013 · comparisign.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →