Add persistence flag for all services #305
Conversation
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
@fastlorenzo any update on this? |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
@Deltachaos thanks for the PR, could you please rebase with master and push it back so we can do some testing before merging? |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
Deltachaos
force-pushed
the
feature/persistence
branch
from
e486b1a to
f5dd3ea
Compare
|
@fastlorenzo i updated the PR. I would be very happy if we could get some progress on #304 and #303 as well, as i think the discussion there got stuck at some point. I am happy to rebase those PRs as soon as we found an agreement in the discussion. |
|
This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
For testing environments it is very useful to disable persistence. Also some of the service only require persistence if you use specific features, and otherwise can simplify deployment if you are able to disable it for certain services.