[Chicago-talk] When to Dockerize a perl program

[Richard Reina]

Hello perl faithful of the WIndy City,

 I have a perl program that effectively works as an API that I have
developed over the years for use for myself and an employee or two that
mainly allows us to update company databases and create some file so that
they can be emailed. The program depends on about a dozen CPAN perl modules
and a few dozen linux packages that are listed below. The installation
process is not something that I dread, in fact I've developed another
program I call machine_builder.pl that automates most of the installation
and configuration so that I can get everything installed and configured on
a new machine in about a couple hours. I've played around a bit with Docker
in order to run Frigate IVR for my home security cameras and have heard
that it may be "the wave of the future". What I am wondering is should I be
looking to make my perl API program a Dockerized app for my office or stay
the course with my tried and true system of setting up a machine to run my
app?

Perl Modules: Test::More Barcode::Code128 Fatal GD Curses
Lingua::EN::Numbers Module::Build Cmenu Date::Manip
DateTime::Event::Holiday::US

Linux Packages: ntp gpm emacs cpanminus alsa alsa-lib alsa-lib-devel
obexpushd smartmontools net-tools gcc build-essential setuptool
mysql-client nis libmysql++-dev libdbd-mysql-perl cups php5-gd sharutils
imagemagick zlibc tetex-base libncurses5 bsdmainutils acpi libcurses-perl
enscript libgd-gd2-perl libncurses5-dev perl-tk cl-gd hylafax-client ncftp
sox ypbind rpcbind portmap nis perl-DateManip libgd-dev libterm-readkey-perl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.pm.org/pipermail/chicago-talk/attachments/20220904/f4ceb0b8/attachment.html>