puffrfish wrote at Jan 2 2018 16:43:52 UTC:

This marks the release of PufferPanel and pufferd v1.2, which implements docker container usage!

To upgrade PufferPanel to v1.2.0, please follow the guide found here.

To upgrade pufferd to v.1.2.0, please follow the guide found here.

Docker

PufferPanel previously supported docker with Scales, but when were planning on bringing support to pufferd, we wanted to make sure it was far more flexible, easy, and reliable than it had been previously.

Docker can be enabled per-server, so you can have some servers that run in containers, while others do not.

This is a basic implementation of the container structure, and should not be relied on for complete security, however is acceptable for file-level isolation.

Note, this release does not include resource limitations on the containers, nor does it block any network related functions. All containers will bind to the host interface for ease of use.

Our implementation uses our base images where applicable, which you can view on this repo: https://github.com/PufferPanel/dockerfiles

pufferd will attempt to use an existing container if the container is named with the UUID of the server, so you are able to create and alter containers to your liking and pufferd will use them. Otherwise, pufferd will create the container when needed, and destroy it once the process is done. This allows for a much more flexible configuration, without leaving a bunch of maintenance or junk around.

To use Docker with PufferPanel, please follow the guide located here after upgrading to v1.2.

Now that pufferd supports Docker, Scales has been officially deprecated and will no longer be supported.

pufferd Packages

This release also marks the shift to using package managers to handle the installation and updates of pufferd. Our repo is hosted via https://packagecloud.io and offers support for Debian, Ubuntu, and CentOS installations.

This means that once you install our repo, updates are handled by your package manager:

apt upgrade pufferd

Any new nodes you create using v1.2 will use the repos, existing installations should follow the guide found here.

Note that when updating the pufferd package, pufferd will restart, which will cause your servers to stop and (if enabled in the server's definition file) start back up.

Updates to v1.2 follow our usual major version upgrade documentation, which you can view here:

Changelog:

• BREAKING: Stop API will now by default not wait for the server to stop before returning. Passing in ?wait will now be a blocking call.
• BREAKING: Console and log API now use the same scope.
• BREAKING: pufferd will no longer start unless --run is given. This avoids accidentally running the binary and causing collisions.
• CHANGED: pufferd is now installed via repos. Existing installations can follow the guidefound here.
• CHANGED: Installer will now ask for credentials if no config is found
• CHANGED: pufferd will now log where the config specified through "logPath", default is "log" if not provided.
• CHANGED: "pre" section is now properly supported. This follows the syntax that "install" uses.
• FIXED: Settings users as an admin will properly create rights if they were not an admin prior.
• REMOVED: --installService is no longer supported by the daemon, using repos is recommended.

Known caveats:

• Editing a user who is an admin may cause a 500. Workaround would be removing admin, making changes, then setting back as admin.