Updated: March 2, 2021
Due to the relevance of the topic, nowadays market has a rich selection of tools intended to serve various stages of the application lifecycle. Technically it is not difficult for people to use Google to find information about this topic and follow documentation pages: but it is not that easy at the same time to get a general idea based on granular information. This article will try to fill in the voids and understand basic concepts about today's cloud applications' lifecycle.
Updated: November 6, 2020
Also known as "Specific Runners", they are required for projects which use secrets or other data which is supposed to remain safe. Read more about it
Updated: November 5, 2020
The acronym CI/CD (sometimes CI/CT/CD or CI/CDD) stands for Continuous Integration, Continuous Testing, Continuous Delivery and Continuous Deployment. CI/CD represents processes and tools around constantly integrating, delivering and deploying new code (features, bug fixes, patches). It involves continuously building, testing, and deploying code changes at every small iteration - reducing the chance of developing new code based on bugged or failed previous versions - to end users.
Updated: October 23, 2020
In this section you will learn the basics about running a CI/CD Pipeline and what steps must be taken to automate integration and deployment.
Updated: October 20, 2020
This is an example or best practice of automated strategy leading your application through all stages of onboarding — dev, QA, staging, production
Updated: October 20, 2020
Lifecycle Management enables you to perform automated operations on your application such as deployment, scaling, healing, upgrade, migration, termination and so on. We went through a lot of brainstorming sessions and we were trying a lot of options in Pan-Net to find the best software which will manage lifecycle operations or orchestrate application according our needs and conditions. And this journey is not finished yet.
Updated: October 19, 2020
To start an application deployment we should understand the resources demand (number of nodes (VMs or pods), CPU, RAM, etc.) of the application based on the information obtained from the application owner/vendor, taking availability requirements into account (Disaster Recovery, High-Availability, Geo-Redundancy, etc.).
Updated: October 15, 2020
Before you take a deep dive into our documentation, please take a moment to learn some basic information about the technology and tools we are using. It might help you to understand the documents better and faster.