- Acquia won't let us compile assets on their machines
- We can't have separate dev and prod configs, because people might check in development builds
- Release automation is v desirable
- There's a story for this!
- whichcountry blows up mktg build time
- To see ANY changes locally, devs need to wait 1-2 minutes (!!!!!!!!!!!!!!!!)
- Default command for compiling sass updates all themes
- Takes a long time to build on sandboxes
- compile_sass watches filesystem, but only the files it knows about. Doesn't update themes.
- How can one watcher manage files across all our Django apps?
- Top priority: sass watcher that understands themes, but still is fast
- Scope watcher to particular areas of the codebase?
- Target one file & one theme
- Discovery: will webpack make this faster/smarter?
- Caching issues with webpack, tests need to be re-run - 20-30s delay
- Should just be able to rerun tests and not worry about rebuilding assets
- changing webpack config should restart webpack dev server (this is doable via webpack dev server plugins)
- Still not especially clear the best way to use docker devstack
- Can we lean on docker hackers for a lunch & learn?
- pdb/pudb to get into running containers
- How to rebuild a container?
- make dev.reset (resets all repos back to master though)
- And when to rebuild a container?
- Read the Docker docs
