Just curious where exactly is the challenge in this setup ? It can't be in apache supporting real certificates - neither can it be in setting up reverse proxy internally...
On Sun, Dec 20, 2020 at 11:19 AM Tom Browder <tom.brow...@gmail.com> wrote: > > > On Sun, Dec 20, 2020 at 09:33 Steven Lembark <lemb...@wrkhors.com> wrote: > >> On Tue, 4 Aug 2020 18:05:28 -0700 >> jbiskofski <jbiskof...@gmail.com> wrote: >> >> > I had a hard time accepting this was a good configuration because for >> > 20 years I had thought of webservers as big giant compiled systems >> > (apache), but apparently you can now create something just as fast in >> > Perl. >> >> And a helluva lot easier to install, manage, develop on, and maintain. > > > Steven, I have met you at a couple of Perl conferences and know you know > Raku as well. One thing that has always bothered me about PSGI, Catalyst, > mod_fcgi, etc., is that I could never find a practical cookbook solution > for a simple but working dynamic and publicly available https website on a > real, modern Apache 2.4 server on a Linux bare-metal, sole user remote > server. > > I would love to be able to have something similar for Raku, and there is > Cro, but it so far cannot handle auto-generation of Let's Encrypt TLS > certificates with a reverse proxy on Apache. > > As an alternative, I would be happy to run with a Perl solution iif it > could handle my TLS requirement. Any suggestions will be greatly > appreciated. > > BTW, I have publicly documented my current Apache setup (non-dynamic > except for limited CGI use on a couple of sites). The Apache uses nearly > the latest Apache and OpenSSL compiled from source. It includes multiple > (15 or so at last count) virtual hosts (using macros for extremely easy > deployment). It was last updated mid-2020 and I'll be looking to update it > next year. It's on Github and I'll send the reference if anyone wants it. > > Blessings, > > -Tom >
