Tredly was created to cater to make software development and sysadmin as easy as possible. Tredly caters to developers of all shapes and sizes, from the weekend warrior all the way up to the large enterprise deployment and everyone in-between. With that in mind Tredly has many features to streamline software development and automate server administration by allowing you to leverage the flexibility of containers.

The easiest way to manage your Tredly containers and use the features of Tredly is to use Tredly Command Center, learn more about Tredly Command Center here.

Core Features

Tredly has three core features on which all other features are built on:

  1. Containers
  2. Platoons
  3. Squads

Containers

Tredly Containers are in essence, scriptable virtual machines. Tredly Containers are configured through the use of a Tredlyfile, which you can learn more about here

Platoons

A Platoon is a group of containers. Platoons are a great way of organizing your containers and doing actions on all containers within the Platoon.

Platoons are particularly useful for development environments e.g. production, staging, integration.

Platoons have the following features:

  • Their own storage area where files and folders can be stored for use by Containers created within the Platoon. This is particularly useful for storing credentials and files that containers within the Platoon reference upon creation (onCreate)
  • Restricting incoming traffic to containers in a Platoon
  • Perform actions on all containers within a Platoon
  • Replicate all containers within a Platoon
  • Environment configurations so variables within a Container's Tredlyfile can be interpreted differently based on the Platoon and/or environment you are running them in.

Squads

A Squad is a group of containers which operate as a single unit.

Squads are particularly useful for:

  1. When you want to use a piece of software that does not have any authentication mechanism (eg. php-fpm) but need to interface another piece of software with it and do not want to run the software from within the same container.
  2. When the software you are using has wildly differing abilities to cope with connections e.g. nginx and php-fpm.