Closed himadrisingh closed 6 days ago
- This looks incorrect. I'd expect it to pull
cloud-e2e.env
.
Fixed
- I ran
rill devtool start e2e
and I see that it's connected to the same Postgres database asrill devtool start cloud
. I'd likerill devtool start e2e
to always start with a fresh Postgres database (and for myrill devtool start cloud
Postgres database to remain untouched). Can we do that? (This comment may be resolved if this behavior is due to point 1.)
Created an ephemeral postgres for e2e only, will get cleaned up everytime we restart.
- Also, it'd be nice to have the option to run
rill devtool seed e2e
to seed the e2e database in the same way asrill devtool seed cloud
.
not able to make it work for cloud too :(
Created an ephemeral postgres for e2e only, will get cleaned up everytime we restart.
Wondering – what specifically do you mean by this? Locally, on a subsequent run, I only was able to reset the db via rill devtool start e2e --reset
. When I didn't pass --reset
, my state was retained (which is fine; the semantics are clear).
Created an ephemeral postgres for e2e only, will get cleaned up every time we restart.
Wondering – what specifically do you mean by this? Locally, on a subsequent run, I only was able to reset the db via
rill devtool start e2e --reset
. When I didn't pass--reset
, my state was retained (which is fine; the semantics are clear).
So essentially if u restart docker then the volume is gone :)
dev is persisted to disk under dev-cloud-state
but not of e2e. So yeah we need to reset or restart the docker.
we can change the behavior i believe.
rill devtool start e2e