Name |
Last commit
|
Last update |
---|---|---|
cloud_migrations | ||
cloudformation_templates | ||
doc | ||
git-hooks | ||
playbooks | ||
util | ||
vagrant | ||
.gitignore | ||
.travis.yml | ||
AUTHORS | ||
CHANGELOG.md | ||
LICENSE.TXT | ||
README.md | ||
requirements.txt |
0.7.0 is from May 2014 and lacks OAuth support and a number of other updates. Switch to having Flower use a config file, enable OAuth Google OAuth requires an additional 4 command line args or environment variables, so it was time for Flower to get a proper config file. The broker configuration remains a command line argument because it is consumed by Celery's configuration parser, not Flower's configuration parser. I can't think of a reason our oauth keys need to be world readable Move templates to live in our new directory layout Paths under templates/ should mirror their default installation path on disk to make it easier to correlate deployed files back to source templates.
Name |
Last commit
|
Last update |
---|---|---|
cloud_migrations | Loading commit data... | |
cloudformation_templates | Loading commit data... | |
doc | Loading commit data... | |
git-hooks | Loading commit data... | |
playbooks | Loading commit data... | |
util | Loading commit data... | |
vagrant | Loading commit data... | |
.gitignore | Loading commit data... | |
.travis.yml | Loading commit data... | |
AUTHORS | Loading commit data... | |
CHANGELOG.md | Loading commit data... | |
LICENSE.TXT | Loading commit data... | |
README.md | Loading commit data... | |
requirements.txt | Loading commit data... |