potiuk commented on issue #4932: [AIRFLOW-3611] Simplified development workflow 
[Depends on multi-staging]
URL: https://github.com/apache/airflow/pull/4932#issuecomment-478020135
 
 
   @ashb @fokko -> I pushed latest version that is much improved:
   
   * mysql installation is now simplified, no more server-specific 
configuration (thanks @ashb for the hint)
   * parameters for the database are now spread across various docker-compose 
files. I found it easiest to have separate compose file for each database and 
"compose" the files when running - so for example when you run it locally you 
compose : docker-compose.yml + docker-compose-postgres.yml + 
docker-compose-local.yml (the last one adds source bind mounts for local 
development). 
   
   It's nicely modular but you might not like it. so if you don't let me know 
(and why) - I might try to find another solution.
   
   Also after @ashb hangout I've decided to implement a small improvement in 
the 'run-test' script - now the database is initialized only the first time you 
run test in the container, subsequent times the database is not initialized 
(unless you specify --with-db-init switch). This is a nice automation for the 
pattern you explained in your hangout, where you mentioned you rarely use 
run_unit_tests.sh because database initialisation is slow. With the approach I 
suggest, you do not have to copy&paste things but can run the tests with the 
scripts. Combined with auto-complete, I think it's really helpful (especially 
to onboard new people). 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to