We are multiple developers working on the a dagster codebase. Does dagster support some variety of dump/restore that would allow us to "hot start" one developer with all the materializations of another by e.g. copying the second developers SQLite database and his storage folders? Are there likely to be absolute paths or the like in the database that would make this inconvenient? Even better if we could hot start a development session with the latest production materializations.

Might be worth a look here ? The guide explains how you can set code and data versions on an asset to avoid re-materialising but I've not tried it myself

hm, this is more about whether I can physically set up a copy of my materialization history on another computer, I guess caching would only help if it had a record of existing materializations?

If you copy across the sqlite DB I imagine you will have? Maybe not though - there could be some local ID used somewhere that could cause a conflict.

yeah, that's what I was worried about