-
Notifications
You must be signed in to change notification settings - Fork 67
PMM-7925: Add SystemD service with podman to run PMM #355
base: main
Are you sure you want to change the base?
Conversation
DISABLE_UPDATES=1 | ||
|
||
# Enable DBaaS feature | ||
#ENABLE_DBAAS=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we split environment variables between this file and service?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
service has environment for systemd/podman and env file is passed to pmm.
It is not split, it just another file to pass to env to pmm
|
||
* Tue May 31 2022 Denys Kondratenko <[email protected]> - 2.29.0-2 | ||
- PMM-7925 add systemd service with podman support | ||
|
||
* Mon May 16 2022 Nikita Beletskii <[email protected]> - 2.29.0-1 | ||
- PMM-10027 remove useless packages | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we use this spec? We use this spec for internal pmm-server package (it contains some js files) and I'm not sure that we need systemd service in container :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it was easier for PoC to use existing spec. And actually it fits it well in term that is a part of pmm-server. We don't need it in container for sure, but probably after build we need to sync it into some repo that available for everyone.
https://jira.percona.com/browse/PMM-7925
percona/pmm-doc#759
ToDo: