Testing Gulp and Django integration
- License
MIT
Moved to settings.
- To create a normal user account, just go to Sign Up and fill out the form. Once you submit it, you'll see a "Verify Your E-mail Address" page. Go to your console to see a simulated email verification message. Copy the link into your browser. Now the user's email should be verified and ready to go.
To create an superuser account, use this command:
$ python manage.py createsuperuser
For convenience, you can keep your normal user logged in on Chrome and your superuser logged in on Firefox (or similar), so that you can see how the site behaves for both kinds of users.
To run the tests, check your test coverage, and generate an HTML coverage report:
$ coverage run manage.py test
$ coverage html
$ open htmlcov/index.html
$ py.test
Moved to Live reloading and SASS compilation.
In development, it is often nice to be able to see emails that are being sent from your application. If you choose to use MailHog when generating the project a local SMTP server with a web interface will be available.
Download the latest release https://github.com/mailhog/MailHog/releases Rename the executable to mailhog and copy it to the root of your project directory Make sure it is executable (e.g. chmod +x mailhog) Execute mailhog from the root of your project in a new terminal window (e.g. ./mailhog) All emails generated from your django app can be seen on
http://127.0.0.1:8025/
- Start django runserver and Mailog in different terminal windows
./mailhog python manage.py runserver
- Start the assets complilation flow from a MacOS environment:
gulp watch
It will open a new browser window with your site running Each change will trigger assets compilation, browser reload, if you don't want this behavior use gulp instead