pteropackages / wingflow Goto Github PK

Currently WingFlow creates an archive of the current files in the server before uploading the new files, but this defeats the purpose of server backups. WingFlow should instead prefer creating a backup and resort to creating an archive if backups are unavailable.

Side note: process should continue on both failures, --guard stops the process if both fail, --fail-fast stops the process if the backup fails. Maybe this should be part of the configuration?

Hi there,

Would it be possible for the CLI package to migrate all the servers in one node to another automatically?

Kind regards, TheH2SO4.

The configuration file has been a bit of a confusing mess for a while, the following changes should make it clearer and easier to use:

• Repo:
• • Address: the repository address
• • The authorization token for the repository
• Panel:
• • URL: the panel URL
• • Key: the account API key
• • ID: the target server ID
• Files:
• • Include: a list of file paths or patterns to include
• • Exclude: a list of file paths or patterns to exclude
• • Backup: whether a backup of the current files should be made
• • Truncate: whether the current files should be removed
• Signal:
• • Kill: whether the server should be killed or stopped
• • Timeout: the amount of time in milliseconds to wait after sending the signal

The pre_run and post_run hooks will no longer be used. Repository authentication is still experimental.

WingFlow should have proper support for use in GitHub Actions, and it technically can be used in actions now. However, security is a concern here, specifically with the WingFlow configuration file, which would likely need to be integrated into GHA's action model (?) for it to work securely.