Below a list of some specific terms related to the Victhorious platform.
A project is the top level organizational object within the Victhorious platform. Before you can do anything else, you should create a project first.
By default you will start your project with only one environment "production". Consider an environment as a specific configuration store of environment variables. Environments allow you to reuse applications/stacks with different configuration values/parameters. Each set of configured environment variables relates to one specific stack item. Multiple HOME's related to the same stack item will share the same specific environment variables.
Each application in your project will be build up out of one or more stack items. You could see the term application more as a global application role, a meaningful collection of stack items. Often we use the term/alias "stack" for the concept application.
The term stack is merely an alias for the concept "application". A stack can consists out of one or more stack items.
A stack item is the lowest level organizational object and important in terms of provisioning. From provisioning perspective, each stack item is linked to the container base image being used for the HOME deploy. Because of this strict relation, each chosen stack item will have its own HOME. Note that is is also possible to distribute the load of a single stack item over multiple HOME's. Depending on the complexity of your environment, you can either have one or more HOME's running for your application or stack item.
The goal of the concept component is to make a stack item reusable. For certain software, it may happen that there is no appropriate stack item available for you. You can than spawn a generic image, install and configure the appropriate software and create a custom component. From that moment on your custom component can be used as reusable stack item in your current and new projects.
The component matrix defines which components (= stack items) can be used in combination with each other. Although the component matrix is not visible in the web interface, it will guide you to select compatible component/stack items for your application/stack. More specifically, the matrix defines which components can communicate with each other. In theory, you could combine any number of components in an application, however the matrix defines which components will be made accessible on the network from other HOME's.
A scenario is a deployment template that allows you to automate a number repeatable tasks on your HOME's. Scenarios can be executed on a single or a collection of HOME's. A scenario consists out of one or more tasks.
Before you can use your new scenario, you need to build it up from a number of tasks (= actions). The platform allows you to select from a default set of actions or you can create you own custom actions. A custom action can be written in almost any interpreted language (as long it is installed on your HOME). However the most common used choice is bash.
A blueprint is a project template that allows you to automatically rebuild new projects based on the configuration of an existing project. Blueprints allow you to quickly spawn complex projects with a lot of applications and HOME's involved. You can extract a usable blueprint from your first project once you finished configuring it. Blueprints are especially beneficial when you have a lot of similar projects.
HOME = Highly Optimized Micro Environment
HOMES are software containers and form the core of your application(s). Consider software containers as a form of light weight virtualization where a single kernel is being shared by isolated, resource managed groups of processes.
TEP = Traffic EndPoint
By default one TEP is being assigned per environment. The TEP is the public endpoint for all the applications spawn within your environment The TEP is an enhanced reverse proxy which provides:
- extra security (application containers are not directly accessible on the internet)
- better performance through HTTP caching
- easy horizontal scale-out (both TEP's and HOME's)
- SSL offloading
Important There is no TEP Limit per environment, we can spawn multiple TEP's on customer's request. However this is currently still a manual action.