can you use an external database to store dagster metadata when running dagster locally using

dagster dev

?

Yes, you can use an external database to store Dagster metadata when running Dagster locally using

dagster dev

. The documentation suggests setting up a cloud-based PostgreSQL database and configuring your local Dagster instance to reference this PostgreSQL as a backend for Dagster in the

dagster.yaml

file. This setup allows multiple developers to work with the same state of assets, and when one developer materializes an asset, others can see it materialized as well. However, it's important to note that if multiple daemons are running locally and pointing to the same metadata database, you may encounter error messages indicating that multiple daemons are sending requests to the PostgreSQL database. This is expected since PostgreSQL is being used as a shared storage, but it's important to understand the implications of this setup and ensure it aligns with your development practices.