fp/README.md

38 lines
1.3 KiB
Markdown
Raw Permalink Normal View History

2024-04-22 00:14:48 +00:00
# futureporn.net
2024-02-05 14:13:02 -08:00
2025-02-13 05:11:50 -08:00
![Tests Status](https://gitea.futureporn.net/futureporn/fp/actions/workflows/tests.yaml/badge.svg)
![Build Status](https://gitea.futureporn.net/futureporn/fp/actions/workflows/builder.yaml/badge.svg)
2025-02-13 12:49:05 -08:00
![Postgres](https://img.shields.io/badge/postgres-%23316192.svg?style=for-the-badge&logo=postgresql&logoColor=white)
2024-07-25 05:53:52 -08:00
Source Code for https://futureporn.net
2025-01-10 19:10:04 -08:00
See ./ARCHITECTURE.md for an overview of the infrastructure components.
2024-06-14 19:18:00 -08:00
2025-08-10 18:17:27 -08:00
## Dev notes
2024-07-25 05:53:52 -08:00
2025-08-10 18:17:27 -08:00
### backup/restore dev database
2024-07-25 05:53:52 -08:00
2025-01-11 04:47:23 -08:00
@see https://stackoverflow.com/a/29913462/1004931
2024-07-25 05:53:52 -08:00
2025-08-10 18:17:27 -08:00
#### backup
2025-01-11 04:47:23 -08:00
Use devbox helper script
devbox run backup
2025-08-10 18:17:27 -08:00
#### restore
2025-01-11 04:47:23 -08:00
cat ./backups/your-backup.sql | docker exec -i postgres_db psql -U postgres
2024-07-25 05:53:52 -08:00
2025-08-10 18:17:27 -08:00
### testing
there is some undesirable behavior when running tests because nektos/act mimicks github actions.
we are banned from github so we aren't using that. instead, we use gitea act_runner.
github actions Job runner runs on docker 'host' network.
gitea act_runner runs on a custom named bridge network. e.g. `GITEA-ACTIONS-TASK-974_WORKFLOW-ci_JOB-Tests-Checks-test_phoenix-network`
confusing, right? It totally is!
when we are working with gitea act_runner, we can use dns names, e.g. test-db.
when we are working with nektos/act, we must use the IP address of the service container.
WTF there must be a better way