Multiplex

CI status

Attribution

This project is based on Luca Palmieri's book Zero to Production in Rust. The source code in this repository contains minor modifications, mostly related to naming and overall code aesthetics. The original code, serving as the basis for this project, was sourced from Zero to Production in Rust and corresponds to the code available in Luca Palmieri's GitHub Repository.

Modifications to the original code include:

Project, trait, variable, parameter, argument, enum, struct, function, method names.
Location of function/method parameters and arguments.
Location of different pieces of code may be different.
Configuration variables and values.
Changes in the wordings for some comments.
Addition of some comments to clarify my own understanding of the Rust language and the structure of the project.
Addition of my own code for further experimentation.

The original code was licensed under the Apache 2.0 and MIT licenses. This project is licensed under the same terms. See the LICENSE-APACHE and LICENSE-MIT file in this repository for the full license text.

My notes

Note: Some shell commands in the book, especially the environment setting commands are based on non-Windows OS (presumably MacOS or Linux). Since this project (multiplex) is developed under Windows 11 (Terminal w/ PowerShell v7.x), some commands that I am keeping as notes for myself below apply to Windows PowerShell.

Do this whenever modifying `spec.yaml`.

Retrieve app ID with command:
```
doctl apps list --format ID
```
Set the APP_ID env:
```
$env:APP_ID="<APP-ID>"
```

Update DigitalOcean's app with the updated spec:

doctl apps update $env:APP_ID --spec spec.yaml

Do this whenever doing `sqlx` migration.

Confirm that sqlx CLI installed on your system:

cargo install --version="~0.6" sqlx-cli --no-default-features --features rustls,postgres

Run sqlx prepare to create or update sqlx-data.json:
```
cargo sqlx prepare
```
Push the change to GitHub to trigger new DigitalOcean deployment.
Now, migrate the database on DigitalOcean. Retrieve DigitalOcean connection string from your DigitalOcean database's connection details.
```
sqlx migrate run --database-url "digitalocean-db-connection-string"
```

Consequence of not syncing `sqlx-data.json` with DigitalOcean

You may see an error similar to below on DigitalOcean build logs when it tries to build the app:

2023-06-20T23:48:12.361939011Z [34m│[0m [36mINFO[0m[0403] RUN cargo build --release --bin multiplex
2023-06-20T23:48:13.674296186Z [34m│[0m [36mINFO[0m[0404] Cmd: /bin/sh
2023-06-20T23:48:13.674331182Z [34m│[0m [36mINFO[0m[0404] Args: [-c cargo build --release --bin multiplex]
2023-06-20T23:48:13.674335744Z [34m│[0m [36mINFO[0m[0404] Running: [/bin/sh -c cargo build --release --bin multiplex]
2023-06-20T23:48:14.535293674Z [34m│[0m    Compiling multiplex v0.1.0 (/app)
2023-06-20T23:48:15.012673167Z [34m│[0m error: failed to find data for query
2023-06-20T23:48:15.012710993Z [34m│[0m                INSERT INTO subscriptions (id, email, name, created_at, status)
2023-06-20T23:48:15.012732736Z [34m│[0m                VALUES ($1, $2, $3, $4, $5)
2023-06-20T23:48:15.012736422Z [34m│[0m
2023-06-20T23:48:15.012739258Z [34m│[0m    --> src/routes/subscriptions.rs:91:5
2023-06-20T23:48:15.012742746Z [34m│[0m     |
2023-06-20T23:48:15.012746126Z [34m│[0m 91  | /     sqlx::query!(
2023-06-20T23:48:15.012748870Z [34m│[0m 92  | |         r#"
2023-06-20T23:48:15.012751799Z [34m│[0m 93  | |         INSERT INTO subscriptions (id, email, name, created_at, status)
2023-06-20T23:48:15.012758810Z [34m│[0m 94  | |         VALUES ($1, $2, $3, $4, $5)
2023-06-20T23:48:15.012761857Z [34m│[0m ...   |
2023-06-20T23:48:15.012764724Z [34m│[0m 100 | |         "pending_confirmation"
2023-06-20T23:48:15.012767482Z [34m│[0m 101 | |     )
2023-06-20T23:48:15.012770251Z [34m│[0m     | |_____^
2023-06-20T23:48:15.012773064Z [34m│[0m     |
2023-06-20T23:48:15.013224490Z [34m│[0m     = note: this error originates in the macro `$crate::sqlx_macros::expand_query` which comes from the expansion of the macro `sqlx::query` (in Nightly builds, run with -Z macro-backtrace for more info)
2023-06-20T23:48:15.013526986Z [34m│[0m
2023-06-20T23:48:15.090388933Z [34m│[0m warning: unused import: `chrono::Utc`
2023-06-20T23:48:15.090407269Z [34m│[0m  --> src/routes/subscriptions.rs:2:5
2023-06-20T23:48:15.090411326Z [34m│[0m   |
2023-06-20T23:48:15.090414710Z [34m│[0m 2 | use chrono::Utc;
2023-06-20T23:48:15.090418239Z [34m│[0m   |     ^^^^^^^^^^^
2023-06-20T23:48:15.090421084Z [34m│[0m   |
2023-06-20T23:48:15.090423884Z [34m│[0m   = note: `#[warn(unused_imports)]` on by default
2023-06-20T23:48:15.090426772Z [34m│[0m
2023-06-20T23:48:15.090429634Z [34m│[0m warning: unused import: `uuid::Uuid`
2023-06-20T23:48:15.090432418Z [34m│[0m  --> src/routes/subscriptions.rs:4:5
2023-06-20T23:48:15.090435238Z [34m│[0m   |
2023-06-20T23:48:15.090438030Z [34m│[0m 4 | use uuid::Uuid;
2023-06-20T23:48:15.090440834Z [34m│[0m   |     ^^^^^^^^^^
2023-06-20T23:48:15.090443640Z [34m│[0m
2023-06-20T23:48:15.602861181Z [34m│[0m warning: `multiplex` (lib) generated 2 warnings
2023-06-20T23:48:15.602887778Z [34m│[0m error: could not compile `multiplex` (lib) due to previous error; 2 warnings emitted
2023-06-20T23:48:15.614469236Z [34m│[0m error building image: error building stage: failed to execute command: waiting for process to exit: exit status 101
2023-06-20T23:48:15.695522300Z [34m│[0m
2023-06-20T23:48:15.695877711Z [34m│[0m command exited with code 101
2023-06-20T23:48:15.696188071Z [34m│[0m
2023-06-20T23:48:16.029894861Z [34m│[0m [31m ✘ build failed[0m

Docker notes

To pull a docker image for postgresql v15.3, execute:
```
docker pull postgres:15.3
```
To run the postgres docker image with dev config (for newsletter DB).
```
docker run -d -e POSTGRES_USER=postgres -e POSTGRES_PASSWORD=password -e POSTGRES_DB=newsletter -p 8090:5432 postgres:15.3
```
- -d flag means to detach the docker run process from the shell and run in the background.
- -e sets up the environment variables for the docker container.
- -p is the port mapping from local->docker.
- postgres in postgres:15.3 is the name of the docker image and 15.3 is the image's tag.

Reference

To get the current timestamp into an environment variable:

$timestamp = (Get-Date -Format yyy-MM-dd_HH-mm-ss.fff)
$env:CURRENT_TIMESTAMP=$timestamp

To let dbg!() output to show up in Terminal:
```
cargo test -- --nocapture
```
Execute following command for tracing:
```
$env:RUST_LOG="trace"
```
For Rust backtrace:
```
$env:RUST_BACKTRACE=1
```

For tracing crate logging with pretty print.

cargo install bunyan

first, and then:

cargo watch -x check -x test -x run | bunyan

For watching, checking, and running tests in realtime:
```
cargo watch -x check -x test -x run
```
Install bunyan log prettier.
```
cargo install bunyan
```

Running Docker.

docker build --tag multiplex --file Dockerfile .

docker run -p 8000:8000 multiplex | bunyan

sqlx logs can be wordy - we can reduce the noise.

$env:RUST_LOG="sqlx=error,info"

$env:TEST_LOG="true"

When running cargo test, be sure to set TEST_LOG to true.

This is essentially the same as above.
```
$env:RUST_LOG="sqlx=error,info"
```
```
$env:TEST_LOG="true"
```

Testing endpoints with `curl`

curl http://127.0.0.1:8000/health_check -v

curl -i -X POST -d "email=thomas_mann@hotmail.com&name=Tom" http://127.0.0.1:8000/subscriptions

Cargo testing

Note that at this time running test cases directly from vscode's editor by clicking the "Run Test" link on top of the function signature doesn't output the logs that use tracing crate.

To output logs in testing.

$env:TEST_LOG="true"

To de-noise sqlx logs.

$env:RUST_LOG="sqlx=error,info"

To unset an environment variable:

Remove-Item Env:<variable_name>

To run a test for a specific test case and to output only specific lines, with bunyan style.

cargo test --quiet --release [test-case-name] | find "HTTP REQUEST" | bunyan

Running Redis on a development machine

Store the current timestamp in an environment variable.

$timestamp = (Get-Date -Format yyy-MM-dd_HH-mm-ss.fff)
$env:CURRENT_TIMESTAMP=$timestamp

Run the following Docker command.

docker run -p "6379:6379" -d --name "redis_$($env:CURRENT_TIMESTAMP)" redis:7

To terminate currently running Redis docker container.

$env:RUNNING_CONTAINER=$(docker ps --filter 'name=redis' --format '{{.ID}}')
docker kill $env:RUNNING_CONTAINER

`cargo-deny` advisories

cargo install --locked cargo-deny && cargo deny init

Write advisories output to a text file.

Some unicode characters may look gibberish. A unicode character ┌─ may look something like Γö£ΓöÇΓöÇ. This can be alleviated by enabling "Beta: Use Unicode UTF-8 for worldwide language support".
```
cargo deny check advisories *> advisories.txt
```

What to do when you see an advisory from `cargo deny check advisories`.

Run cargo update. It may update the crates to new versions with fixes.

jpnws/multiplex