Skip to content
The library to power Playdoh, Mozilla's Django template. File issues in playdoh: https://github.com/mozilla/playdoh
Python Shell
Find file
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
funfactory
tests
.gitignore
LICENSE
MANIFEST.in
README.rst
setup.py
tox.ini

README.rst

funfactory is what makes playdoh fun. You import it within a Django manage.py file and it sets up the playdoh environment and configures some settings.

Any substantial part of playdoh's core should be contained within funfactory. However, it is not a collection of standalone apps. Check out the playdoh docs for a complete user guide.

Hacking

To develop new features for playdoh core, you'll want to hack on funfactory! To run the test suite, first install tox then cd into the root dir and type the tox command. The tox.ini will handle the rest.

Note

if you supply a different playdoh remote URL or a different branch or something, remember to delete the .playdoh/ directory between tests for a clean slate.

To try out cutting edge funfactory features in a real playdoh app, you can use the develop command to install a link to the files within your virtualenv:

workon the-playdoh-clone
pushd ~/your/path/to/funfactory
python setup.py develop
popd

Test Suite Environment

Here are some environment variables that are acknowledged by the test suite:

FF_DB_USER
MySQL db user to run manage.py test. Defaults to root.
FF_DB_PASS
MySQL user password for manage.py test. Defaults to an empty string.
FF_DB_NAME
MySQL db name for manage.py test. Defaults to _funfactory_test.
FF_PLAYDOH_REMOTE
Git qualified URL for playdoh repo. Defaults to git://github.com/mozilla/playdoh.git.
FF_PLAYDOH_BRANCH
Default branch to pull and update. Defaults to base.
Something went wrong with that request. Please try again.