initial scaffolding for a ci pipeline. there aren't that many tests yet, but this will enable writing and running them later.
rust: backend, batch
cargo build
cargo test
cargo clippy
cargo doc
cargo fmt --check
typescript: frontend
npm build
npm test
eslint
flyctl deploy
the frontend gets deployed to fly.io but is currently not fully functional as i deliberately do not add an env var for the backend location. this works as a proof-of-concept deployment process, but actual functionality shall wait until i have better backend validation, rate limiting, user authorization, etc in place.
later on, backend could get deployed to fly.io too as a separate application.
additionally, batch will most likely only be deployed to a high-power dedicated server (hetzner), either manually or with an rsync script or some such.
initial scaffolding for a ci pipeline. there aren't that many tests yet, but this will enable writing and running them later.
rust: backend, batch
cargo buildcargo testcargo clippycargo doccargo fmt --checktypescript: frontend
npm buildnpm testeslintflyctl deploythe frontend gets deployed to
fly.iobut is currently not fully functional as i deliberately do not add an env var for the backend location. this works as a proof-of-concept deployment process, but actual functionality shall wait until i have better backend validation, rate limiting, user authorization, etc in place.later on, backend could get deployed to
fly.iotoo as a separate application.additionally, batch will most likely only be deployed to a high-power dedicated server (hetzner), either manually or with an
rsyncscript or some such.incidentally, this PR also solves exercises 11.20 - 11.21 of full stack open: ci/cd