Combined wagon and composition repository for the Bienenschweiz Hitobito instance
| Branch | Domain | Deployment |
|---|---|---|
| develop | https://bienenschweiz-hitobito-develop.renuoapp.ch | auto |
| main | TODO | release |
See ./hitobito/doc/developer/local_setup.md
bin/setup tries to automate this as much as possible.
The development seeds create an OAuth application and an API key (service token)
named KAS, both with randomly generated credentials. To instead reuse the
credentials a local KAS checkout already has in its config/application.yml
(HITOBITO_OAUTH_ID, HITOBITO_OAUTH_SECRET and HITOBITO_API_KEY), point
KAS_PROJECT_PATH at it via .envrc:
bundle exec rails db:seed wagon:seedThe seed is idempotent, so it can be re-run to switch between generated and KAS-provided credentials. It prints both at the end.
nctl exec app hitobito-develop -p renuo-bienenschweiz bin/rails r 'InspectionReminderJob.new.enqueue!'
The output will be sent to the logs. If some mails fail, it will log an error to Sentry and print out the indexes. The error will also be printed in the logs so you can also inspect the logs.
The separate tasks can be run with
nctl exec app hitobito-main -p renuo-bienenschweiz bin/rails r 'InspectionService.new.retry_failed_inspection_reminder({{INDEX}})'
The index and command can be found in the logs or also Sentry (as extra argument failed_index).
cd hitobito_bienenschweiz
bin/rspecto reset the wagon test database, run
cd hitobito
rails db:drop db:create db:schema:load db:migrate wagon:migrate RAILS_ENV=test RAILS_TEST_DB_NAME=hit_bienenschweiz_test