DevOps

DevOps is an artificial term made up of Development + Operations. The emergence of and need for DevOps can be explained by the fact that the cycles for delivering new software (or changes to a website) have become shorter and shorter over time. Operations and development have become interlinked and a new genre of DevOps has emerged.

More releases, better quality

With DevOps, development and IT operations gradually grow together. Changes can be implemented practically seamlessly and indefinitely during ongoing operations. At the same time, DevOps minimizes the risk of failure.

We would be happy to explain this admittedly new and difficult topic to you personally. In our infographic, you can see what the DevOps cycle looks like for us.

Operation only without further development

If you have a more static project, the DevOps Cycle will run less frequently. I.e. it only rotates on the right-hand side: follow the orange dashed, rotated arrow in the infographic.

DevOps is not user support, by the way. We also offer SLA and hosting to match our DevOps service.

The DevOps Cycle at Tojio:

plan:
Further development / feature development
Updates [security updates (core & contributed modules) + other updates (minor versions)]

code:
Docker Container
Local IDE
JetBrains PhpStorm IDE
Visual Studio Code

build:

GitLab Runner: Composer, NPM, Code Tests

test:
Staging system (DEV) for tests

release:
Administration in GIT, merge into the master branch

deploy:
GitLab Runner: Composer, NPM, code tests
Deployment to production system (LIVE)

operate:
Hosting (web server / DB)
Server maintenance

monitor:
Server System Monitoring
Project Uptime Monitoring
Performance Monitoring
SSL Monitoring
(DoS) Attack Monitoring & Prevention