CAUTION: if you put 1997-era software on the public-facing internet then you have 25 years of known security bugs to worry about. In 1997 I worked on a commerc

CAUTION: if you put 1997-era software on the public-facing internet then you have 25 years of known security bugs to worry about. In 1997 I worked on a commercial/intranet web app using Perl 5, with CGI.pm, behind Apache httpd, on a Unix box. I think we supported Dec Alpha, Solaris, and IRIX? These all (well, not really the OSes) still exist in modern forms, mostly unchanged, so if you really want to make it public, at least have a modern Apache facing the world. If you use a late 1990s Linux distro like https://archive.org/details/debian_1.3.1 https://archive.org/details/debian_1.3.1 you'll be using effectively the same environment. What I did in 1997 was to implement my own template language, so I could have Perl process it to add the header/footer. It was something like "$$ insert filename.html $$" or something else dead simple like that. I used xemacs as my development environment, though of course many used vi back then too, and I used NEdit for a while in the mid-1990s, which is more like Notepad. We used CVS for version control. To publish content now, using your home computer, get your router to forward external connections for a given port to the M1 Mac. Then use a dynamic DNS service so others can connect to your machine by name. I haven't done this last step for about 12 years and don't know how it's done these days. Back then I could set it up with DynDNS but they stopped free hostname services back in 2014. Also back then I could use the built-in Dynamic DNS tooling in my router.