lila bc38137a12 feat: add production deployment config

- Add docker-compose.prod.yml and Caddyfile for Caddy reverse proxy
- Add production stages to frontend Dockerfile (nginx for static files)
- Fix monorepo package exports for production builds (dist/src paths)
- Add CORS_ORIGIN env var for cross-origin config
- Add Better Auth baseURL, cookie domain, and trusted origins from env
- Use VITE_API_URL for API calls in auth-client and play route
- Add credentials: include for cross-origin fetch requests
- Remove unused users table from schema

2026-04-14 11:38:40 +02:00

3.1 KiB

Raw Blame History

notes

tasks

pinning dependencies in package.json files
rethink organisation of datafiles and wordlists

problems+thoughts

docker credential helper

WARNING! Your credentials are stored unencrypted in '/home/languagedev/.docker/config.json'. Configure a credential helper to remove this warning. See https://docs.docker.com/go/credential-store/

vps setup

monitoring and logging (eg via chrootkit or rkhunter, logwatch/monit => mails daily with summary)

cd/ci pipeline

forgejo actions? smth else? where docker registry, also forgejo?

postgres backups

how?

try now option

there should be an option to try the app without an account so users can see what they would get when creating an account

resolve deps problem

﬌ pnpm --filter web add better-auth WARN 2 deprecated subdependencies found: @esbuild-kit/core-utils@3.3.2, @esbuild-kit/esm-loader@2.6.5 Progress: resolved 577, reused 0, downloaded 0, added 0, done WARN Issues with peer dependencies found . └─┬ eslint-plugin-react-hooks 7.0.1 └── ✕ unmet peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.0": found 10.0.3 . | +3 + Done in 5.6s using pnpm v10.33.0

env managing

using env files is not uptodate, use a modern, proper approach

add option to login with apple accounts

add option to login with email+pw

credentials are saved in Downloads/lila/ json file

app publication/verification:

Branding and Data Access (Scope) Verification

In addition to brand verification, your app may also need to be verified to use certain scopes. You can view and track this on the Verification Center page:

Branding status: This tracks the verification of your app's public-facing brand (name, logo, etc.).
Data access status: This tracks the verification of the specific data (scopes) your app is requesting to access.

Note: You must have a published branding status before you can request verification for data access (scopes). Manage App Audience Configuration Publishing Status Manage your app publishing status in the Audience page of the Google Auth Platform. User Type Manage your app audience in the Audience page of the Google Auth Platform.

link

tipps

backend advice: backend
openapi
bruno for api testing
tailscale
husky/lint-staged
musicforprogramming.net

openwordnet

download libraries via

python -c 'import wn; wn.download("omw-fr")';

libraries:

odenet:1.4 omw-es:1.4 omw-fr:1.4 omw-it:1.4 omw-en:1.4

upgrade wn package:

pip install --upgrade wn

check if wn is available, eg italian:

python -c "import wn; print(len(wn.words(lang='it', lexicon='omw-it:1.4')))"

remove a library:

python -c "import wn; wn.remove('oewn:2024')"﬌ python -c "import wn; wn.remove('oewn:2024')"

list all libraries:

python -c "import wn; print(wn.lexicons())"

3.1 KiB Raw Blame History Unescape Escape