{"_id":"58fe142d180afa25006c7985","version":{"_id":"58fe142d180afa25006c7974","project":"54e7fca9e6e77d1900ed11f0","__v":2,"createdAt":"2017-04-24T15:05:17.571Z","releaseDate":"2017-04-24T15:05:17.571Z","categories":["58fe142d180afa25006c7975","58fe142d180afa25006c7976","58fe142d180afa25006c7977","58fe142d180afa25006c7978","591f725ffc05d30f00488267"],"is_deprecated":false,"is_hidden":false,"is_beta":true,"is_stable":true,"codename":"","version_clean":"1.1.0","version":"1.1"},"category":{"_id":"58fe142d180afa25006c7975","version":"58fe142d180afa25006c7974","project":"54e7fca9e6e77d1900ed11f0","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-02-21T03:34:02.028Z","from_sync":false,"order":0,"slug":"documentation","title":"Documentation"},"parentDoc":null,"__v":1,"project":"54e7fca9e6e77d1900ed11f0","user":"54e7ffdc6a7b0e2300d90d4c","updates":["591c30632b798519001d2884"],"next":{"pages":[],"description":""},"createdAt":"2017-01-29T00:56:38.251Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":6,"body":"As Scales is no longer actively developed and has many issues with the codebase and design, we have chosen to switch to pufferd for our new daemon.\n[block:callout]\n{\n  \"type\": \"danger\",\n  \"title\": \"WARNING\",\n  \"body\": \"Note that pufferd is a new daemon, and that the following steps will render your Scales instance inoperable. **Please backup your data prior to upgrading.** \"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Installing pufferd\"\n}\n[/block]\nTo install pufferd, you can follow the standard installation procedure like any other node. \n\nYou can use the auto-deploy to re-deploy the new configuration to pufferd without deleting the previous Scales installation.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"OVH Servers Warning\"\n}\n[/block]\nYou should check your partitioning scheme to see how it is laid out. Some default OVH partition setups give most of the available disk space to /home. If this is the case, prior to migration please find the following line in /etc/pufferd/config.json\n`\"serverfolder\": \"/var/lib/pufferd/servers\",`\n\nand change it to\n`\"serverfolder\": \"/home/pufferd/servers\",`\n\nand run the following commands\n\n`mkdir /home/pufferd`\n`chown -R pufferd:pufferd /home/pufferd`\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Importing Scales data\"\n}\n[/block]\npufferd features a (beta) import system to bring your server data over to pufferd.\n**If you have an OVH server, please see the information below prior to running this.**\n\nTo use this, run the following commands:\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"cd /srv/pufferd\\nmkdir -p /srv/pufferd/data/servers/\\n./pufferd --config=/etc/pufferd/config.json --migrate\\nchown -R pufferd:pufferd /var/lib/pufferd\",\n      \"language\": \"shell\"\n    }\n  ]\n}\n[/block]\nThis will move the relevant server folders to the new daemon directories and update the configurations to the best of their ability. Any customized settings will NOT be copied over, only standard settings such as memory, IP, port, and similar.","excerpt":"How to change to pufferd for the new version","slug":"migrating-to-pufferd","type":"basic","title":"Migrating to pufferd from Scales"}

Migrating to pufferd from Scales

How to change to pufferd for the new version

As Scales is no longer actively developed and has many issues with the codebase and design, we have chosen to switch to pufferd for our new daemon. [block:callout] { "type": "danger", "title": "WARNING", "body": "Note that pufferd is a new daemon, and that the following steps will render your Scales instance inoperable. **Please backup your data prior to upgrading.** " } [/block] [block:api-header] { "type": "basic", "title": "Installing pufferd" } [/block] To install pufferd, you can follow the standard installation procedure like any other node. You can use the auto-deploy to re-deploy the new configuration to pufferd without deleting the previous Scales installation. [block:api-header] { "type": "basic", "title": "OVH Servers Warning" } [/block] You should check your partitioning scheme to see how it is laid out. Some default OVH partition setups give most of the available disk space to /home. If this is the case, prior to migration please find the following line in /etc/pufferd/config.json `"serverfolder": "/var/lib/pufferd/servers",` and change it to `"serverfolder": "/home/pufferd/servers",` and run the following commands `mkdir /home/pufferd` `chown -R pufferd:pufferd /home/pufferd` [block:api-header] { "type": "basic", "title": "Importing Scales data" } [/block] pufferd features a (beta) import system to bring your server data over to pufferd. **If you have an OVH server, please see the information below prior to running this.** To use this, run the following commands: [block:code] { "codes": [ { "code": "cd /srv/pufferd\nmkdir -p /srv/pufferd/data/servers/\n./pufferd --config=/etc/pufferd/config.json --migrate\nchown -R pufferd:pufferd /var/lib/pufferd", "language": "shell" } ] } [/block] This will move the relevant server folders to the new daemon directories and update the configurations to the best of their ability. Any customized settings will NOT be copied over, only standard settings such as memory, IP, port, and similar.