Solved Debian deployment

[Sinas]

Hello everyone,

I have a situation at work and I haven't done this before. so we have a binary file(executable) which is our product. think of it as an API that listens on port 8080 and if you curl it on / it responds with hello world. I was tasked to deploy the application. previously I have done docker and k8s deployment and it is usually pretty smooth. but this time I have this restriction that I can not use containers. I'm thinking about running this API as systemd service. but here is the question:
what is the standard way to deploy such application, do I have to pack it in a .deb file and install it with dpkg? anisble? simple shell script to run on every server? run my own apt repo? is running it as a systemd even a good idea?

thanks, Best.

 

[nevola]

Hi!

If you're going to publish your software for Debian, the proper way will to provide a deb package to be ready to be installed with "dpkg". But, if dependencies are required, then it is a good idea to create a public APT repository where to maintain all the deb packages required, then the users could update easily with "apt-get upgrade".

This option allow as well to maintain deb files for each Debian version.

Hope that helps.

 

[Sinas]

Hi!

If you're going to publish your software for Debian, the proper way will to provide a deb package to be ready to be installed with "dpkg". But, if dependencies are required, then it is a good idea to create a public APT repository where to maintain all the deb packages required, then the users could update easily with "apt-get upgrade".

This option allow as well to maintain deb files for each Debian version.

Hope that helps.

thank you for the help, actually I have access to the Debian OS and the OS is customized to meet the requirements.
since the deployment happens internally, Public APT repo is not an option, and the dependencies are already installed on the OS.

I'm beginning to think it is best to ship only a .deb package to the OS and do a simple dpkg -i blah.deb to get the job done.

 

[KGIII]

Public APT repo is not an option

You can host your own private repo. Doing it the way they suggested makes good sense if you have more than a few computers that need this package and need to be updated when the software is updated. Automation of mundane tasks is what makes computers great.