search

bugy / script-server

Web UI for your scripts with execution management
Other
1.55k stars 246 forks source link

Ability to backup history #600

Closed gautam-nutalapati closed 1 year ago

gautam-nutalapati commented 1 year ago

Hey Script-Server Team! For compliance and tracking purposes, it would be good to have ability to backup history. We loose the history today when script server restarts. Proposal:

bugy commented 1 year ago

Hi Gautam, script server stores history on a hard drive, so normal restarts won't delete the history. Are you using docker, and just restart a container, may be?

Gautam @.***> schrieb am Mo., 28. Nov. 2022, 22:07:

Hey Script-Server Team! For compliance and tracking purposes, it would be good to have ability to backup history. We loose the history today when script server restarts. Proposal:

  • [Manual] Download option for history
  • [Automated] Provide ability to access script history via scheduled job, so that users can write their own backup jobs (e.g. job that runs every X hrs and sends history file to AWs S3)

— Reply to this email directly, view it on GitHub https://github.com/bugy/script-server/issues/600, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJXPJK6AE3YUWVGS522YITWKUNKTANCNFSM6AAAAAASNYMC5A . You are receiving this because you are subscribed to this thread.Message ID: @.***>

gautam-nutalapati commented 1 year ago

Thanks for quick response! yep, I am using docker, and its restarted every time we make a change to our script server contents. If it is being stored in HDD, can we run a job that transfers this file as needed? Where is this file located?

bugy commented 1 year ago

Hi @gautam-nutalapati, you can bind logs directory to a host folder. Using smth like -v /host/path/to/logs/:/app/logs

gautam-nutalapati commented 1 year ago

@bugy Thank you for this info! I do see the history in the location /app/logs/processes. Closing this issue.