MuckRock · Squarelet · DocumentCloud · DocumentCloud-Frontend
MuckRock is a non-profit collaborative news site that gives you the tools to keep our government transparent and accountable.
MuckRock depends on Squarelet for user authentication. As the services need to communivate directly, the development environment for MuckRock depends on the development environment for Squarelet - the MuckRock docker containers will join Squarelet's docker network. Please install Squarelet and set up its development environment first.
- Check out the git repository -
git clone [email protected]:MuckRock/muckrock.git - Enter the directory -
cd muckrock - Run the dotenv initialization script -
python initialize_dotenvs.pyThis will create files with the environment variables needed to run the development environment. - Set an environment variable that directs
docker-composeto use thelocal.ymlfile -export COMPOSE_FILE=local.yml - Set up the javascript run
inv npm "install"andinv npm "run build" - Start the docker images -
inv upThis will build and start all of the docker images using docker-compose. - Set
dev.muckrock.comto point to localhost -echo "127.0.0.1 dev.muckrock.com" | sudo tee -a /etc/hosts - Enter
dev.muckrock.cominto your browser - you should see the MuckRock home page. - In
.envs/.local/.djangoset the following environment variables:
SQUARELET_KEYto the value of Client ID from the Squarelet ClientSQUARELET_SECRETto the value of Client SECRET from the Squarelet Client
- You must restart the Docker Compose session (via the command
docker-compose downfollowed bydocker-compose up) each time you change a.djangofile for it to take effect.
You should now be able to log in to MuckRock using your Squarelet account.
The development environment is managed via docker and [docker compose][docker compose]. Please read up on them if you are unfmiliar with them. The docker compose file is local.yml. If you would like to run docker compose commands directly, please run export COMPOSE_FILE=local.yml so you don't need to specify it in every command.
The containers which are run include the following:
-
Django This is the Django application
-
PostgreSQL PostgreSQL is the relational database used to store the data for the Django application
-
Redis Redis is an in-memory datastore, used as a message broker for Celery as well as a cache backend for Django.
-
Celery Worker Celery is a distrubuted task queue for Python, used to run background tasks from Django. The worker is responsible for running the tasks.
-
Celery Beat The celery beat image is responsible for queueing up periodic celery tasks.
All systems can be brought up using inv up. You can rebuild all images using inv build. There are various other invoke commands for common tasks interacting with docker, which you can view in the tasks.py file.
The MuckRock development environment will join Squarelet's environments docker network, so that the services can coexist. Please see the README file from Squarelet for more information.
The application is configured with environment variables in order to make it easy to customize behavior in different environments (dev, testing, staging, production, etc). Some of this environment variables may be sensitive information, such as passwords or API tokens to various services. For this reason, they are not to be checked in to version control. In order to assist with the setup of a new development environment, a script called initialize_dotenvs.py is provided which will create the files in the expected places, with the variables included. Those which require external accounts will generally be left blank, and you may sign up for an account to use for development and add your own credentials in. You may also add extra configuration here as necessary for your setup.
Invoke is a task execution library. It is used to allow easy access to common commands used during development. You may look through the file to see the commands being run. I will go through some of the more important ones here.
inv prod will merge your dev branch into master, and push to GitHub, which will trigger CodeShip to release it to Heroku, as long as all code checks pass. The production site is currently hosted at https://www.muckrock.com/.
inv staging will push the staging branch to GitHub, which will trigger CodeShip to release it to Heroku, as long as all code checks pass. The staging site is currently hosted at https://muckrock-staging.herokuapp.com/.
inv test will run the test suite. To reuse the database, pass it the -r=1 option.
inv coverage will run the test suite and generate a coverage report at htmlcov/index.html.
The test suite will be run on CodeShip prior to releasing new code. Please ensure your code passes all tests before trying to release it. Also please add new tests if you develop new code.
inv pylint will run pylint. It is possible to silence checks, but should only be done in instances where pylint is misinterpreting the code.
inv format will format the code using the yapf code formatter.
Both linting and formatting are checked on CodeShip. Please ensure your code is linted and formatted correctly before attempting to release changes.
inv up will start all containers in the background.
inv runserver will run the Django server in the foreground. Be careful to not have multiple Django servers running at once. Running the server in the foreground is mainly useful for situations where you would like to use an interactive debugger within your application code.
inv shell will run an interactive python shell within the Django environment.
inv sh will run a bash shell within the Django docker comtainer.
inv dbshell will run a postgresql shell.
inv manage will allow you to easily run Django manage.py commands.
inv manage migrateto migrate databaseinv npmwill allow you to run NPM commands.inv npm "run build"should be run to rebuild assets if any javascript or CSS is changed. If you will be editing a lot of javascript or CSS, you can runinv npm "run watch".inv herokuwill open a python shell on Heroku.
Python dependencies are managed via pip-tools. This allows us to keep all of the python dependencies (including underling dependencies) pinned, to allow for consistent execution across development and production environments.
The corresponding files are kept in the pip folder. There are requirements and dev-requirements files. requirements will be installed in all environments, while dev-requirements will only be installed for local development environments. It can be used for code only needed during develpoment, such as testing. For each environment there is an .in file and a .txt file. The .in file is the input file - you list your direct dependencies here. You may specify version constraints here, but do not have to.
Running inv pip-compile will compile the .in files to the corresponding .txt files. This will pin all of the dependencies, and their dependencies, to the latest versions that meet any constraints that have been put on them. You should run this command if you need to add any new dependencies to an .in files. Please keep the .in files sorted. After running inv pip-compile, you will need to run inv build to rebuild the docker images with the new dependencies included.
FOIAMachine is our free FOIA filing tool, that allows you to track your requests while requiring you to manually handle all of the message sending and receiving. It is run off of the same code base as MuckRock. To access it, set dev.foiamachine.org to point to localhost - sudo echo "127.0.0.1 dev.foiamachine.org" >> /etc/hosts. Then pointing your browser to dev.foiamachine.org will take you to FOIAMachine - the correst page is shown depending on the domain host.
MuckRock uses watson for search. The index should stay updated. If a new model is registered with watson, then build the index (fab manage:buildwatson). This command should be run on any staging or production servers when pushing code that updates the registration.