CJ_Clippy ea6c5b5bd7
Some checks are pending
ci / build (push) Waiting to run
ci / test (push) Waiting to run
fix funscript selector
2025-09-02 18:53:26 -08:00
2025-08-25 12:19:36 -08:00
2025-08-27 16:29:55 -08:00
2025-07-19 11:47:22 -08:00
2025-08-16 02:58:13 -08:00
2025-03-05 03:03:52 -08:00
2025-07-19 11:47:22 -08:00
2025-09-02 18:53:26 -08:00
2025-07-19 11:47:22 -08:00
2025-01-11 09:38:19 -08:00
2024-08-07 11:30:29 -08:00
2025-08-25 20:18:56 -08:00
2025-07-19 11:47:22 -08:00
2025-08-29 21:52:35 -08:00
2024-08-07 11:30:29 -08:00
2025-01-10 19:10:04 -08:00
2025-08-10 18:17:27 -08:00
2025-03-22 19:40:16 -08:00
2024-04-18 20:51:09 +00:00
2025-07-18 03:50:29 -08:00
2025-07-19 07:18:48 -08:00
2025-07-19 11:47:22 -08:00
2025-08-10 18:17:27 -08:00
2025-08-25 12:19:36 -08:00

futureporn.net

Tests Status Build Status Postgres

Source Code for https://futureporn.net

See ./ARCHITECTURE.md for an overview of the infrastructure components.

Dev notes

backup/restore dev database

@see https://stackoverflow.com/a/29913462/1004931

backup

Use devbox helper script

devbox run backup

restore

cat ./backups/your-backup.sql | docker exec -i postgres_db psql -U postgres

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

Description
Languages
Rust 39.2%
JavaScript 24.2%
TypeScript 16.8%
Python 8.7%
Handlebars 5.6%
Other 5.3%