You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make this more immediately useful, it would be nice if the script could run in a mode where it would run regularly. Perhaps even setting the frequency, and length of time it should run.
$ npm start --length indefinite --frequency 6000
The text was updated successfully, but these errors were encountered:
Actually I think this should be done in the parent repository, since this repo will soon become just the engine that backs up volumes to snapshots. It is the responsibility of the parent repository to run this thing forever/when it wants.
@Dermah I agree, if there is a parent orchestrator, it should manage the scripts. But there could be a circumstance where an admin doesn't want to setup the orchestration. Do we want to support that case?
To make this more immediately useful, it would be nice if the script could run in a mode where it would run regularly. Perhaps even setting the frequency, and length of time it should run.
The text was updated successfully, but these errors were encountered: