English
Applications
The platform is not a single program but a dozen and a half separate services: one serves the API, another the interface, a third the database migrations, and so on. In PDM each of these services is called a platform application (the interface also calls them Service and Component).
On a stand all of these applications run side by side, and each one has its own version — the image currently deployed there. Working with applications in PDM comes down to two things: seeing what is deployed on a stand and at which version, and changing it.
What an application consists of
| What you see | What it means |
|---|---|
| Alias | A short technical name such as cs, api3, ui2. Configuration and logs identify the service by it |
| Version on the stand | The image tag currently deployed on that particular stand |
| Settings | A set of configuration parameters grouped by meaning |
| Actions | Operations you can run for this service: build an image, set a tag |
The set of applications is shared by the whole platform and maintained by an administrator. For an ordinary user applications are a given — they cannot be added or removed from the interface.
Which applications a stand has
PDM has no separate "list of applications" page — applications are always shown in the context of a specific stand, on the Services tab.
Every stand has its own list
The Services tab shows the services this stand has configuration values for. The list can therefore differ from stand to stand.
What an application version is
An application version is the tag of the built image deployed on the stand. As far as configuration is concerned, the version is just another settings field, only marked in a special way: PDM pulls it out into its own column and highlights changes with a badge.
A version reaches a stand in one of three ways:
- it was built — you started a branch build or a version build, the build produced a tag, and that tag became the value of the field;
- it was set by hand — you picked an existing image tag from a list;
- it came from a release — the platform-wide version was updated centrally.
Each of these is covered on the Application actions page.
Where to see the current versions
The main place is the Deployed version column on the Services tab of the stand page. It can hold up to three badges at once: the platform-wide value, the stand's own value and your unsaved edit. The rule for reading them is if an orange “Overridden” badge is there, that is what the stand runs; otherwise the blue one applies. The badges are explained in detail under Stand configuration.
The second place is the action form: there PDM shows a badge with the current version read from the service repository.
The version on the stand and the current version in the repository are different things
The current version in an action form is the version of the service source code that the next build will be counted from. The version in the Deployed version column is what is actually running on the stand. The two often do not match.
What's next
- Application actions — how to build a branch, bump a version or set an existing tag.
- Builds and pipelines — the CI Builds page, statuses and the link to GitLab.
- Stand configuration — how to change settings and versions and apply them.