mistercrunch opened a new pull request, #27953:
URL: https://github.com/apache/superset/pull/27953

   ### SUMMARY
   
   When firing the `docker-compose up` command, which is pretty much the first 
step
   of most developer workflows, we kick off up 2 chromium downloads: one
   for PLAYWRIGHT and one for PUPPETEER by default. Those are used for optional 
features
   like alerts/reports/thumbnails/ and for CI.
   
   For convenience, I'm also introducing support for defining
   environment variables overrides for docker-compose in `docker/.env-local` 
while
   adding this to `.gitignore`, which developers can use without the
   fear/confusion around committing local envrionment specific settings to
   the repo.
   
   -----------------
   
   About the core feature in this PR here,
   this saves minutes upon firing `docker-compose up`, and reduce confusion
   around "what the heck is it doing!?", in a phase where we should just be
   pulling and starting docker images.
   
   Most developer workflows don't require either of those, and if it
   were the case, we should bake this into the docker image as opposed to
   installing during the bootstrap phase. In any case, devs can switch those on
   easily by tweaking the env vars specified in `docker/.env`
   
   #### PUPPETEER
   About PUPPETEER: in https://github.com/apache/superset/pull/22623, I found 
that it is used by Applitool in two GHAs:
   - 
(superset-applitool-cypress)[https://github.com/apache/superset/blob/master/.github/workflows/superset-applitool-cypress.yml]
   - 
(superset-applitools-storybook)[https://github.com/apache/superset/blob/master/.github/workflows/superset-applitools-storybook.yml]
   
   Seems PUPPETEER is probably never really useful locally.
   
   #### PLAYWRIGHT 
   
   About PLAYWRIGHT, this is what powers alerts and reports as well
   thumbnail-generation. This is more common, and can be flipped on
   by setting `ENABLE_PLAYWRIGHT=true` in `docker/.env-local`
   


-- 
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.

To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to