cn-quickstart icon indicating copy to clipboard operation
cn-quickstart copied to clipboard

Restartability for long-running instances

Open ghost opened this issue 6 months ago • 0 comments

Background

Quickstart needs to progress in it's ability to run a long-lived instance. Therefore it needs to persist it's onboarding configuration, and state in general.

The intent here is that this opens up Quickstart to be a playground for practicing longer term operations, such as domain migrations, network and application upgrades. Presently this is not possible due to the current ephemeral nature of the containers

Questions

  • What is the impact on Splice LocalNet to facilitate this?

Proposed Tasks

  • Ensure onboarding/startup processes idempotent
  • Enable persisted volumes that will survive a restart:
    • PostgreSQL data
    • Configuration
    • Anything else?
  • Consider startup orchestration/ordering that may be impacted by subsequent starts
  • Make command to "stop" all containers (if not already the case)
  • Make "clean-volumes" to remove all docker volumes (in order to start fresh again)
  • Make "clean" becomes "clean-build"?

Verification

Make sure that everything can be restarted (even docker/host), and things can be resumed again where they left off.

ghost avatar Jun 03 '25 23:06 ghost