aleksa
a9b8e7bc9e
All checks were successful
E2E Tests with Cypress / cypress (push) Successful in 3m12s
31 lines
1.8 KiB
Markdown
31 lines
1.8 KiB
Markdown
# aleksa.sh
|
|
|
|
|
|
|
|
my personal website and a sandbox to practice react/next.js and setting up + deploying relevant projects.
|
|
|
|
## running
|
|
|
|
requires docker and docker compose (optionally node + yarn to use cypress without docker)
|
|
|
|
run dev (w/ hot reload) with `docker compose up app-dev`
|
|
|
|
run prod with `docker compose up app-prod`
|
|
|
|
for e2e, run the app in test mode with `docker compose up app-test`, then start a native cypress run with `yarn e2e`. for a docker cypress run instead, use a tarball with custom build context to circumvent the default .dockerignore file like in the ci example.
|
|
|
|
test expansion is planned for the future.
|
|
|
|
## ci/cd
|
|
|
|
forgejo runner used (labelled `ubuntu-host-docker`) is a host passthrough runner that has access to an ubuntu host machine with docker and docker compose installed. refer to this [forgejo actions documentation](https://forgejo.org/docs/latest/admin/actions/#host) for more info.
|
|
|
|
make sure to always have a cleanup task at the end to prevent piling up containers on the host machine.
|
|
|
|
the ci workflow syntax and tasks may undergo frequent changes due to forgejo actions being wip.
|
|
|
|
future commits will introduce auto-deployment in cd.
|
|
|
|
## contact
|
|
|
|
feel free to reach out to me for any purpose on aleksa@aleksa.sh :)
|