Release on CPAN

[wbraswell]

This issue is a version-neutral continuation of https://github.com/denny/ShinyCMS/issues/46

[wbraswell]

I believe all of the following functionality can (and should) be made available directly via the cpan ShinyCMS or cpanm ShinyCMS commands:

"... 'install wizard' script so that people could install and configure by pasting a one liner into a terminal - something like 'curl -sf https://shinycms.org/install/install.sh | sh' that will install Catalyst etc from CPAN if needed, ask where to put the CMS support files, and then ask questions to populate an initial shinycms.conf for them." https://github.com/denny/ShinyCMS/issues/46#issuecomment-490281356

The only time I've seen a curl-style "install wizard" script used in Perl is for boostrapping local::lib or Perlbrew, both of which need to be installed before you run the cpan or cpanm commands...

https://github.com/wbraswell/lampuniversity.org/blob/master/bin/LAMP_installer.sh#L1341 'curl -L cpanmin.us | perl - -l $HOME/perl5 App::cpanminus local::lib'

https://github.com/wbraswell/lampuniversity.org/blob/master/bin/LAMP_installer.sh#L1403 'curl -L http://install.perlbrew.pl | bash'

Since Shiny is not a prerequisite for cpan or cpanm themselves, I believe it is considered "best practices" to use CPAN as the primary installation mechanism, with other options such as OS-specific packages and curl-style install wizards used as secondary alternatives.

[wbraswell]

I know how to make CPAN releases when using ExtUtils::MakeMaker... but we aren't using that for Shiny, are we?