Skip to content

Cloud and DevOps

Cloud and DevOps

Where the system runs, and how a change gets there. AWS or Azure when that is already where the company lives.

Talk about this
A small server cabinet beside a desk

The useful question is not which logo is on the server. It is whether a person can restore last night’s database, and whether a failed job tells someone before a user does. We set that up for Odoo and for the web or mobile apps that talk to it. If you already pay for AWS or Azure, we use that estate. If you do not, we pick a small setup that matches the size of the system.

DevOps is the path a change takes. It is reviewed, it runs in a non-production environment, and it reaches live on purpose. Docker keeps that environment repeatable. A pipeline is only useful if someone can see that it failed. The goal is a release you can explain, and a rollback when the platform allows it.

Included

What the work includes

Hosting for Odoo and custom applications

Separate environments for review and production

Backups and a restore you can rehearse

CI/CD from the repository to a reviewed environment

Monitoring for failed jobs, full disks, and integration errors

In practice

Pick a part of the work.

Where it runs

A small, named setup. Production is not where we experiment.

  • A production environment and a separate place to review changes
  • AWS or Azure when the company is already there
  • Database backups on a schedule, stored away from the server itself
  • A restore tried on a copy, not only a green tick in the console
  • Access limited to the people who need it

Fit

A good fit when

The system is still on a laptop or a single shared server

Releases are copied onto a server by hand

A broken nightly job is found by a user

Tell us the job. We will say whether this is the right shape, and what the first release should leave out.

Start a project

Related