Le 1 déc. 2012 à 09:19, James Pic <[email protected]> a écrit :

> - would it be useful to mention that if the app lives in a separate (ie. open 
> source) repo, it will need the repo to contain a test_project to run 
> `./manage.py test theapp` in CI systems ?

Yes, it's a good practice to include required files and to document how to run 
the tests.

In practice a settings file, and often a URLconf, are enough. See 
https://github.com/aaugustin/django-resto/blob/master/Makefile#L1 for an 
example. 

The concept of a "Django project" doesn't help developers structure their apps 
properly and take advantage of pluggable apps and packaging tools, let's avoid 
it!

> - would it be useful to add an example .travis.yml and some info about 
> setting up travis-ci (if the app is open source of course)

Travis builds are very hard to debug, making the first experience daunting even 
for experienced developers. I wouldn't recommend it to beginners in a tutorial. 
Besides, Django's docs don't recommend external services until they're well 
established.

-- 
Aymeric.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to