pagure

#3243 Explain async components lifecycle
Closed: Invalid Opened by abitrolly.

Closed: Invalid
Reopen Issue

From https://pagure.io/pagure/pull-request/3193#comment-53051

https://docs.pagure.org/pagure/overview.html?highlight=async - a lot of components. Looks like they are manually installed and managed and there is no plugin architecture with config and status monitoring.

Could be useful to get some explanations how to manage Pagure + components setup in a static way - kubernetes files or whatever.

The services are celery based, we do not manage them using kubernetes or whatever, they are installed and managed as systemd services (all services files being in the sources).

If you want to look into running pagure with kubernetes I would gladely review a PR to add your findings to the documentation and if you have more specific questions let's also add them to the documentation

Metadata Update from @pingou:
- Issue close_status updated to: Invalid
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.