Familiarize yourself with the greetings-api project
Lives at the repo root
Simple API written in Go which listens on http 8080 and returns a greeting message.
/main.go
The API endpoint and it's configuration. This contains the message that the API returns
/main_test.go
The unit test for the greeting function. It tests that the greeting is what it expects. If the greeting is changed, it should be changed here too or the test will fail. This is an easy way to demonstrate test failures.
Lives under /website/
Static site using Hugo, a static site generator written in Go.
website/partials/shortcodes/greeting.html
The partial included in the website which makes a call to the backend API
content/_index.md
The front page of the app which includes the greetings-api message
website/content/posts/my-first-post.md
Sample post which includes the greetings-api message
Lives under /ci/
The CI module has two main submodules: backend and frontend. Those are subdirectories of
./ci and focus on the specifics of the backend/frontend. The ci module itself pulls
those together for a single project entrypoint.
Run the unit tests for the project
dagger call test --source .
Build the project
dagger call build --source . --env dev export --path ./build
Run and serve the project
dagger call serve --source . up
This serves the backend at localhost:8080 and the frontend at localhost:8081. Once the
ports are tunneled, open localhost:8081 in a browser
Deploy the project
dagger call deploy --source . --fly-token $FLY_TOKEN --netlify-token $NETLIFY_TOKEN
This deploys the backend to fly.io at https://dagger-demo.fly.dev/ and the frontend to Netlify at https://dagger-demo.netlify.app/
Secrets are retrieved at runtime from Infisical, a SaaS Secret Manager
Create a release of the project
dagger call all --source . --release --infisical-token $TOKEN
Run the CI without even checking out a branch
dagger -m github.com/kpenfound/greetings-api call all --source https://github.com/kpenfound/greetings-api#main --release --infisical-token $TOKEN