Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/hackoregon/team-budget

Repo for the Budget team's backend code
https://github.com/hackoregon/team-budget

backend budget

Last synced: 3 days ago
JSON representation

Repo for the Budget team's backend code

Awesome Lists containing this project

README 

        
# Running the APIs in Docker

You can develop and test against the entire set of dependencies for the Django APIs using a Docker container.



This reduces the amount of software you'll have to install and keep running correctly on your system, and improve your ability to stay current with your fellow developers.



## Prerequisites

You'll need to install two pieces of software:

- Docker

- Docker Compose



### Mac Users

If you're running Mac OS X on a MacBook from 2010 or later, the install for both of these is simple:

- download the Docker DMG file [here](https://docs.docker.com/docker-for-mac/install/)

- install and you're ready to go!



### Windows Users (and ancient Macs)

If you're running an older MacBook, or running Windows, see [here](https://github.com/hackoregon/devops-17/blob/master/HOWTO%20Guides/HOWTO-Docker-on-OSX-with-Docker-Toolbox.md) for instructions on using the Docker Toolkit and still get the same basic experience.



### Linux Users

If you're running a friendly Linux:

- installing Docker - try one of these links [here](https://www.docker.com/community-edition) (Note: we've never tried this - send us feedback on the #dev-ops channel)

- installing Docker Compose - use the `curl` command you'll find [here](https://github.com/docker/compose/releases)



Ping us if you need instructions on installing Docker on Linux.



## Build the Docker container

At present, each developer builds the Docker container on their own computer.  (In the future, based on demand, we may pre-build the container image and enable developers to download the latest stable image.)



Here's how:



1. clone the current repo to your local system (or `git pull` if you already have it cloned and just need to update to latest code)

2. run `cd team-budget` (i.e. into the folder where you find the repo)

3. run `source budget_proj/bin/env.sh` to initialize environment variables needed by the build scripts.

4. run `cp budget_proj/budget_proj/project_config_template.py budget_proj/budget_proj/project_config.py`

    - The default values in that new `budget_proj/budget_proj/project_config.py` file that you just created are for running with an embedded SQLite database for development. But we do not use that database for deployments, so you need to set the connection parameters for some other database running outside of the Docker container that you are about to build.

    - For example, use the connection parameters for the integration database or the production database. Both of those are hosted on AWS EC2 instances. You will need to get those connection parameters from the team's devops people.

5. run `./budget_proj/bin/start-proj.sh -l`

    - This builds the image and starts it running in a container.

    - Note: this script already includes the `--build` parameter for `docker-compose`, so if you have made changes to the Django code or anything else used by Docker to build the container, Docker will include the changes made since the last start (build) of the container.

6. When you want to stop the Docker container, you can either:

    - type `[Control-C]` in the window where you are running the `start-proj.sh` script; or

    - run `docker stop [container id or name]` in another window.



Once the container is running, you can browser or query the API endpoints at http://127.0.0.1:8000/budget/.  If you are using [Docker Toolbox](https://www.docker.com/products/docker-toolbox), the endpoints will be available at http://192.168.99.100:8000/budget/ instead.



## How can you troubleshoot the app or other bits in the container?



Sometimes you will have to troubleshoot the server - look at log files, look for a missing file, whatever.



This is when you can use the [Docker CLI](https://docs.docker.com/engine/reference/commandline/cli/):



```

docker exec -it [container_id or name] /bin/bash

```



Getting the container_id or name for the running Docker container is easy - just run `docker ps`.



## Further info

[Tips for Docker Toolbox on OS X](https://github.com/hackoregon/devops-17/blob/master/HOWTO%20Guides/HOWTO-Docker-on-OSX-with-Docker-Toolbox.md)

[Cleaning up Docker Containers and Images](https://github.com/hackoregon/devops-17/blob/master/HOWTO%20Guides/HOWTO%20Cleanup%20Docker%20Containers%20and%20Images.md)