Docs Examples
From a photo to the site
A photo taken on the phone is converted, comes back to the app, and the site is rebuilt and published.
- A photo is taken in your appYour company's app, on the phone, sends the photo to the link of your image converter, with the service key in the request.
- The devices convert itThe converter, set to the size your site uses, runs on a device that has room at that moment.
- The version comes back to the appThe converted image comes back as the answer, or the app picks it up when it is ready.
- The app starts the pipelineWith the image saved where your site reads it, the app calls the link of your pipeline.
- Build and tests on the idle machinesThe steps that do not depend on each other run at the same time, on different devices.
- The site is updatedThe publishing step checks the site from outside and hands back the link.
Your services talk to your systems, and to each other through them. Here, a company’s app turns a photo taken in the field into a page on its site, with no one in between.
What each part uses
- The image converter, adjusted to the one size the site uses. See Image converter.
- The service key, sent in the header the app already knows how to send. See Connect your systems.
- The distributed CI/CD, which can be started by a call as well as by a change to the repository. See Distributed CI/CD.
Where the savings are
Converting images and building the site are bursts of heavy work. They run on devices that were already idle, so there is no server sitting waiting for the next photo, and nothing new to rent.