Deployment is the definition of all activities that make a system available for use. The present information will describe our deployment organization concerning this repository. Also important to follow, more information is available on both deployer and env-files repositories.

• Deployment Servers

  • Introduction

  • Information

• Deployment Environments

  • Tiers

Our Deployment Servers infrastructure is a collection of configured clusters, servers, and middleware that collaborate to provide hosting of our several modules, testing and production scenes. Deployment servers vary significantly, but, broadly, the tiers are bookended by starting at local (local), development (dev), internal (internal) or integration (integration) and ending at stage (stage), test (test) or production (prod). A common 4-tier architecture is: (i) development; (ii) testing; (iii) staging; or (iv) production. However, we are using a more extended architecture from the common deploy architecture. Further information regarding our several Deployment Environments is detailed.

Integration means that part of the server's software is delivered to the source as a whole, in order to discover the problems of development as early as possible: deployment is the delivery of code as soon as possible to the operational development/testing servers for early testing. Delivery means that the source is delivered to the stakeholder as soon as possible. In order to find out early issues in the production environment.

If we wait until all things have been completed before we deliver them to the next link, all the problems will only erupt at the end and the cost of the solution will be enormous or even impossible to solve. The so-called continuation, that is, each completed a complete part, delivered to the next link, found that the problem can be adjusted immediately. The problem is not amplified to other parts and the following links. To better understand the definitions of Deployment Environment follow the article on Wikipedia.

Before getting into the Deployment Environment, itself, we first have to understand the definition of Deployment. A Deployment is defined in our project as follows.

Twofold list of our Deployment definition:

1. The set of repeatable, quantifiable and measurable activities that are performed within a specific operating Environment to successfully construct, deliver, and prepare a versioned of the project, so that we can deliver an Environment for test or use by its targeted Stakeholders or End Users, in our case, the last are Clinicians.

2. The logistical act of testing, delivering or releasing a Release to targeted Stakeholders or End Users in a specific Environment.

Our finely-divided list of tiers:

While the actual frequency of Deployments by Environment may differ for different stages of the project, the following graph, shows an interesting pattern of our source. We use a Deployment Server to distribute content and configurations per each Deployment Environment, grouped into server classes. Our Deployment Environment can be full-fledged Environments or they can be just simple groups of configurations.