People of Greenwood Discord app

For integration tests recommend using docker to stand up a Postgres instance.

docker-compose up -d

If not already added, you will need the musl target to build for AWS Lambda.

rustup target add x86_64-unknown-linux-musl

Then build and package the binary.

cargo build --target x86_64-unknown-linux-musl --release
cp target/x86_64-unknown-linux-musl/release/pog bootstrap
zip bootstrap.zip bootstrap

Application deployment

Bastion host

A Cloudformation template is provided for use in configuring a database, bastion host and the necessary infrastructure.

Database

Database migrations are found in the db directory and managed with Flyway. To update a migration:

flyway \
  -url="jdbc:postgresql://{HOST}:5432/{DATABASE}?user={USER}" \
  -locations="filesystem:./db/prod" \
  migrate

The user's password will be queried before running. To check the status of migrations without making any changes use the command info instead. Naming of migration scripts should follow the format:

V{migration number}__{descriptive name}.sql

Example: V1__create_wager_table.sql

For debugging within the database prefer psql.

psql -h {HOST} -U {USER} -W"

Serverless

The application is expected to be deployed as a Lambda instance with network security configured for the database.

Expected environment variables:

• DB_CONNECTION_STRING - connection string formatted for use by SQLx Postgres driver
• DISCORD_PUBLIC_KEY - the public key used for Ed25519 verification of inbound calls
• DISCORD_TOKEN - Discord access token for the application
• DISCORD_APPLICATION_ID - Discord application id

TODO

• check to ensure only one name is used
• search in /bets for non-discord users
• test InMemWagerRepo with the Postgres repo tests