See Production for information on how to deploy for production.
Getting started:
docker compose pull
docker compose up --detach --remove-orphans
docker compose exec phpfpm composer install
docker compose exec phpfpm bin/console doctrine:migrations:migrate --no-interactiondocker compose exec phpfpm composer fixtures-loadIf you run the fixtures, the following user will be available:
| Username | Password | Roles | API token |
|---|---|---|---|
| [email protected] | password | ROLE_ADMIN | |
| [email protected] | password | ROLE_USER_ADMIN | |
| [email protected] | password | ROLE_USER | |
| [email protected] | password | ROLE_API | this-is-not-a-very-secret-token |
For creating more users, run the following command
docker compose exec phpfpm bin/console app:user:add EMAIL PASSWORDdocker compose exec phpfpm composer coding-standards-applyOr perhaps:
docker compose exec phpfpm composer coding-standards-checkAPI documentation is available on /api/v1/docs:
open "http://$(docker compose port nginx 8080)/api/v1/docs"A user must authenticate to actually use the API:
curl --header 'Authorization: Bearer this-is-not-a-very-secret-token' "http://$(docker compose port nginx 8080)/api/v1/routes"docker compose exec phpfpm composer update-api-specUpdate translations
docker compose exec phpfpm composer update-translationsUpdate Danish translations (translations/*.da.xlf), e.g. using Poedit:
open translations/admin.da.xlfTo help the translation
extractor
find some translations, we have some translation expressions in templates/admin/_messages.html.twig.
We use Symfony's AssetMapper for asset management. Furthermore, as suggested by AssetMapper, we use BiomeJsBundle for linting assets.
See Serving Assets in dev vs
prod for details on how to
handle assets for the prod environment.
Apply and check coding standards for assets:
task coding-standards:assets:checkWe use Console Commands for command in the console.
List the app commands with
task console -- list app