Summary

Please add persistent server-side storage for runtime instance state so Rustatio can resume correctly after a container restart, host reboot, or NAS reboot.

What happens

Some state is written to /data/state.json, but after restarting the container or rebooting the host, Rustatio does not fully restore the previous runtime state.

In particular:

• Instance status is not remembered reliably
• Seed time / related runtime progress does not appear to be retained as expected

Environment

• Rustatio Docker image: ghcr.io/takitsu21/rustatio:latest
• Persistent mount: /data
• Running on TrueNAS SCALE / Docker
• Example config:
  • PUID=568
  • PGID=568
  • /mnt/ssd_pool/custom_docker_apps/rustatio/data:/data

What I verified

• /data is mounted correctly
• state.json exists and persists on the host
• The container can write to /data
• This does not look like a Docker volume or permission issue

Request

Please persist runtime state server-side so that after a restart/reboot Rustatio can restore:

• seed time / accumulated counters
• instance active/inactive status
• any other runtime state required to continue where it left off
• custom presets and default status

Why this would help

For self-hosted Docker/NAS deployments, restarts and reboots are normal. Without persistent runtime state, users lose continuity and the app behaves as if instances partially reset after restart.

Optional implementation idea

If some state is currently only stored in browser localStorage or only kept in memory, please consider moving or mirroring it into the server-side persisted state under /data/state.json (or another durable file/database path), then restoring it on startup.