-
stable v0.2.0 -
- Create a server from a backup archive alone: https address of a Wings backup (.tar.gz), settings file or manual egg, owner, node, address and limits; the new server's Wings downloads, unpacks and deletes the archive. Same progress, retry and stop as a clone.
- Settings file in every server (
.texus-server.json, hidden, a few KB): written hourly when the settings changed, so every Wings backup carries egg, image, startup command, variables and limits. No owner, e-mail, tokens or passwords. Can be switched off, eggs can be excluded, the last run and failed writes are shown. - Export settings of a server as JSON, and use such a file in the clone form instead of the source's settings.
- After unpacking an archive created without a settings file, a button applies the variables and limits from the file found in it.
- Address checks: https only, no private or reserved IPs, length limit; presigned links are stored encrypted and never shown or logged in full.
-
stable v0.1.0 -
- First release: clone a server into a new one with the same egg, image, startup command, variables and limits, with its current files or the files of one of its backups (local or S3). Choose name, owner, node, address and limits, see the plan, then clone. The files are copied node to node by Wings; progress, error messages, retry, stop and deleting the new server on the admin page.
- Update notice: when a newer version is out, Admin > Extensions and the licence box on the admin page show it, with what is new. With the optional update helper (set up once as root), the update runs with one click after a backup of the panel files and the database.