Skip to content
This repository has been archived by the owner on Feb 14, 2025. It is now read-only.

Commit

Permalink
fix docs
Browse files Browse the repository at this point in the history
  • Loading branch information
alejandroroiz committed Aug 6, 2024
1 parent ab8c2ce commit 807e0fc
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 7 deletions.
4 changes: 4 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# Changelog

## 6.5.8

* Migrated to docker compose v2

## 6.4.0

* Updated client with a new logo and updated CSS to match design style guide. The new CSS coloring should
Expand Down
4 changes: 2 additions & 2 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -5,10 +5,10 @@ clean:
find . -name "*.pyc" -delete

up:
docker-compose up
docker compose up

down:
docker-compose down
docker compose down

docker_build: clean
docker build -t lyft/confidant .
Expand Down
10 changes: 5 additions & 5 deletions docs/root/contributing.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,19 +29,19 @@ Our only method of accepting code changes is through github pull requests.
## Development guide

This guide assumes you're using docker desktop, which includes docker, and
docker-compose.
docker compose.

A full developer configuration is available, using compose, which uses
local dynamodb, local kms, and a local simplesamplephp. We have quick make
aliases, so it's not necessary to learn the details of docker-compose.
aliases, so it's not necessary to learn the details of docker compose.

### Starting confidant

To start: `make up`

To test code changes:

1. Kill docker-compose (ctrl-c)
1. Kill docker compose (ctrl-c)
1. `make docker_build`
1. `make up`

Expand All @@ -50,11 +50,11 @@ and the password is `confidant`.

All configuration settings for this environment are in the `config/development`
directory. If you wish to change any settings, kill the docker compose, make the
change, and start the docker-compose environment back up.
change, and start the docker compose environment back up.

### Running tests

The easiest way to run the tests is through docker-compose as well, as both unit
The easiest way to run the tests is through docker compose as well, as both unit
and integration test suites can be run via compose.

To run the full test suite (minus pre-commit):
Expand Down

0 comments on commit 807e0fc

Please sign in to comment.