Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 4.03 KB

os_publishing.md

File metadata and controls

51 lines (36 loc) · 4.03 KB
Raw

Contents:

Introduction

Ploutos produces O/S packages such as DEB and RPM files (contained within ZIP archives attached to GitHub Actions workflow runs), but it doesn't "publish" them for you.

Publishing of O/S packages is the process of making them available on a web server (your "online repository") somewhere in the correct directory structure with the correct accompanying metadata files such that standard O/S packaging tools like apt and yum can find and install packages from your "online repository".

Considerations

  • How much will it cost to host the packages? This will be influenced by the service you use to host the web server, the number of historical versions that you wish to keep, the package types you want to offer (e.g. DEB and/or RPM), and the number of specific O/S versions you intend to package for separately (unless your packages are usable on many/all O/S versions and such can be offered as a single O/S version independent package).
  • How much will it cost to serve the packages? This will be influenced by the service you use to host the web server, the size of your packages, the size of your expected audience, how often you expect to publish new versions, and whether you wish to pay extra to serve the packages closer to the end user by fronting your repository with something like a Content Distribution Network.
  • How many packages do you intend to publish? If only one or a few you may need a simpler setup than if you intend to publish many different software packages.
  • What kind of availability guarantees do you want? Does it matter if your repository is offline or slow or unreachable sometimes and/or to some clients?
  • How long do you expect to keep the repository? This can influence how much room you need for growth, or if you want the repository to also support additional package types later.
  • How do you want to manage the metadata? By invoking stock packaging tool commands manually, or by using some tooling to help you, or even by using a 3rd party service to do the work for you?
  • Who should have access to your package signing key?

Doing it yourself

There are many examples out there of how to do this yourself, e.g. to pick just a few:

Tools that can help

Just a few examples, there are likely many others out there:

3rd party services

Disclaimer: The services are listed in alphabetical order, there is no special meaning or priority to the order. We have NO relationship with these services nor experience with them and cannot recommend them, they were simply found via Google, use them at your own risk.