Welcome to the Cloud 66 Changelog. These are the changes that have gone out this month:
Rails Default Node Version UpdateRails
As announced two weeks ago (on 10th August), we have now changed the default Node version installed on newly created Rails/Rack servers to v10.x. Although this isn't the latest Node version, it still caters best to users with older Rails applications. For newer (or older) Node versions, users can still use their manifest to specify the version they require.
For more information and examples of this, see the help page on controlling your Node version. Don't hesitate to drop us a message on slack or email if you have any questions or feedback about this!
Maestro Service Node AllocationMaestro
We're happy to announce that Maestro now supports service node allocation. You can now specify which servers you want your service to run on using your
service.yml configuration. This is useful when servers in your cluster are not all equal, or you need to separate specific services.
You can choose to specify a list of server names, or matching server tags, to allocate the servers. The default behavior is unchanged and, if not specified, services will still run on any/all of the available servers. If no servers match your required constraints, the service will not be scheduled. For more information and to get started, the best place is the help documentation!
AWS ELB/ALB SSL PolicyGeneral
We're pleased to announce that any AWS ELBs/ALBs created from now onward will use a more secure set of SSL protocols and ciphers by default (when performing SSL termination). Existing ALB/ELBs can have their policies manually modified via the AWS UI. In the unlikely case that you need to specify a less secure protocol or cipher, you can use your manifest to specify the policy you want.
Updated Linode RegionsGeneral
We've just added two more regions to Linode (Sydney and Mumbai). If you were waiting for these, wait no longer!