⠋ Ranko ⣠

A tool to upload and review documents.

How to code

Master is always deployable (github-flow). Make a branch! Don't directly commit to master.

Unit tests:

nosetests --with-coverage --cover-package=app

Coverage is nice but not absolute. A metric that becomes an objective is not a metric anymore.

UI tests are ran with:

casperjs test tests.coffee

Linters are available but not enforced: pep8, coffeelint.

ensure that unit tests are OK.
deploy master to a vagrant VM (vagrant up + scripts/deploy --to=test should do this).
test upgrade using scripts/deploy --to=test --branch=YOURBRANCH.
If everything is fine, merge the branch (no FF):
- git checkout master
- git merge --no-ff YOURBRANCH
- git push origin master :YOURBRANCH
- git branch -d YOURBRANCH
Deploy master to prod: scripts/deploy.

Name		Name	Last commit message	Last commit date
Latest commit History 514 Commits
app		app
conf		conf
devops		devops
docs		docs
fixtures		fixtures
instance		instance
migrations		migrations
scripts		scripts
static		static
templates		templates
tests		tests
vendor		vendor
.ackrc		.ackrc
.buildpacks		.buildpacks
.gitignore		.gitignore
.travis.yml		.travis.yml
Gruntfile.js		Gruntfile.js
Procfile		Procfile
README.md		README.md
Vagrantfile		Vagrantfile
coffeelint.json		coffeelint.json
manage.py		manage.py
package.json		package.json
requirements.txt		requirements.txt
run.py		run.py
wsgi.py		wsgi.py
wsgi_heroku.py		wsgi_heroku.py