[
https://issues.apache.org/jira/browse/VCL-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273292#comment-13273292
]
Larry Burton commented on VCL-587:
----------------------------------
How best to proceed? Two things are necessary for an automated installation:
scripts and custom data. Scripts could be put into an RPM to make installation
of VCL just a "yum install". The custom data is by necessity external to the
script. We could have just a file to edit. This is simplle and makes security
a local matter. We could have a web site with an interactive page that
generates a parameters file. This is perhaps easier for users. We could have an
in-between approach of a downloadable script to emulate an interactive web
page. To me, the web page on the VCL project page is most appealing. A second
issue is the starting point of the host OS. What level of completeness of a
LAMP server is assumed? With some work, an RPM could likely bring an OS to a
common starting point.
> Automated install script/tools
> ------------------------------
>
> Key: VCL-587
> URL: https://issues.apache.org/jira/browse/VCL-587
> Project: VCL
> Issue Type: New Feature
> Reporter: Aaron Peeler
> Attachments: create_new_self_signed_ca.sh, https_setup.sh,
> install_vcl.sh, vcl_parameters_13.sh, vcl_pre_commands_13.sh
>
>
> Placeholder for Dr. Larry Burton's automated install
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
