Public | Automated Build

Last pushed: 3 years ago
Short Description
Short description is empty for this repo.
Full Description


FAR Ain't Reach

Quick Setup

$ virtualenv python_env
$ . python_env/bin/activate
$ pip install -r requirements.txt
$ bower install
$ ./
$ python
$ ./bin/far

Running in gunicorn

You'll want to configure MongoDB sessions when running more than 1 worker,
since memory sessions are not shared. The --limit-request-line is necessary
because SAML SSO interactions often send the entire encoded request as a GET
parameter, and this can be quite long.

$ cd src/far
$ gunicorn -e FAR_CONFIG=$FAR_CONFIG_DIR/config.json -k eventlet -w N -b --limit-request-line=8190 far:app

Common development tasks

  • Setting up the development environment before first use

    > python
    > export PATH=$PWD/bin:$PATH
        (in Windows: set PATH=%CD%\bin;%PATH%)
    > buildout
  • Running tests
    Tests are kept in the tests directory and are run using

    > py.test
  • Creating Sphinx documentation

    (Fill in the values, edit documentation, add it to version control)
    (Generate documentation by something like "cd docs; make html")

    (See this guide for more details)

  • Specifying dependencies for your package
    Edit the install_requires line in src/far/ by listing all the dependent packages.

  • Producing executable scripts
    Edit the console_scripts section of entry_points in src/far/ Then run buildout. The corresponding scripts will be created in the bin/ subdirectory. Note that the boilerplate project already contains one dummy script as an example.

  • Debugging the code manually
    Simply run bin/python. This generated interpreter script has the project package included in the path.

  • Publishing the package on Pypi

     > cd src/far
     > python register sdist upload
  • Creating an egg or a windows installer for the package

     > cd src/far
     > python bdist_egg
     > python bdist_wininst
  • Travis-CI integration
    To use the Travis-CI continuous integration service, follow the instructions at the Travis-CI website to register an account and connect your Github repository to Travis. The boilerplate code contains a minimal .travis.yml configuration file that might help you get started.

  • Other tools
    The initial buildout.cfg includes several useful code-checking tools under the [tools] section. Adapt this list to your needs (remember to run buildout each time you change buildout.cfg).

  • Working with
    If you are working on a small project you might prefer to drop the whole buildout business completely and only work from within the package directory (i.e. make src\far your project root). In this case you should know that you can use

     > python develop

    to include the package into the system-wide Python path. Once this is done, you can run tests via

     > python test

    Finally, to remove the package from the system-wide Python path, run:

     > python develop -u
  • Developing multi-package projects
    Sometimes you might need to split your project into several packages, or use a customized version of some package in your project. In this case, put additional packages as subdirectories of src/ alongside the original src/far, and register them in buildout.cfg. For example, if you want to add a new package to your project, do:

     > cd src/
     > cookiecutter
     > paster create <new_package_name>

    Then add src/<new_package_name> to version control and add the directory src/<new_package_name> to the develop list in buildout.cfg. Also, if necessary, add <new_package_name> to the [main] part of buildout.cfg and mention it in the [pytest] configuration section of setup.cfg.

Copyright & License

  • Copyright 2015, Ken Sheedlo
  • License: MIT
Docker Pull Command
Source Repository