balacij

Related to #2642 as well because we might need to rearrange some of our make targets to assist with this. I think there are a few things we can remove...

Mostly complete information on the dependencies (just need to check out `containers` a bit more): From Stackage: - composition - very small single file package, with no dependencies. - containers...

I don't believe there are pre-compiled libraries (or exes) from stackage. It seems it's always just source code that we build locally and cache it in `./.stack-work/` (for local projects)...

That's interesing. I don't know if we can. In this snippet, we setup the cache using `actions/cache@v2`, and it places a POST-hook at the end of the entire CI job...

Another issue that slows down deployment is that in the CI, the `Clean previous run` (which just runs `make clean`) will start updating the Cabal cache. Example run where this...

After reading around the GitHub Actions docs, it appears that we can only [upload artifacts and download them from within the same workflow](https://docs.github.com/en/actions/guides/storing-workflow-data-as-artifacts#about-workflow-artifacts). I guess the feature is only meant...

I think I've found one of the main culprits for the cache misses; caches aren't shared between workflows. Specifically, despite sharing the same keys, the caches in the `Build` and...

Regarding Lens, which is a fairly large dependency that takes a lot of time to compile, there is a variant of it by the same authors called "[microlens](https://hackage.haskell.org/package/microlens)" which claims...

Yes, we should have that meeting. Is tomorrow at 11am/4pm alright?

Sounds good.