| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
On an initial clone, the Vagrantfile would check and make sure that the
submodule was present (and usable inside and outside the box), but on a
subsequent provisioning it wasn't making sure it was up to date.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- Adds is_superuser flag to User
- Logged-in user must be a superuser or have from_body set in order to access
anything within /admin
- has_permission_to on a superuser will always return true
- Only superusers can create/grant superusers
- New `createsuperuser` command for creating superusers
|
| |
|
|
|
|
| |
It should now show a failure message on failure, rather than always show
the success message, and not show a confusing error about general.yml if
something went wrong before creating that file.
|
| |
|
|
| |
Fixes #1197. Thanks to Dave Arter for helping out with this.
|
| |
|
|
|
| |
Call the necessary boilerplate in each script so you can call them
directly. Remove boilerplate from files that don't need it.
|
|
|
This makes it easier to set up, as you can do:
$ git clone --recursive https://github.com/mysociety/fixmystreet
$ cd fixmystreet
$ vagrant up --no-color
|
