This repository has been archived by the owner on Dec 31, 2022. It is now read-only.
Support arbitrary customization of webserver site configuration #100
Comments
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 25, 2017
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 25, 2017
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
1 task
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 28, 2017
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 29, 2017
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 29, 2017
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
nickmarden
added a commit
to RapidRiverSoftware/opsworks_ruby
that referenced
this issue
Aug 30, 2017
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
dotnofoolin
pushed a commit
to dotnofoolin/opsworks_ruby
that referenced
this issue
Nov 23, 2021
Allow the user to deploy multiple applications on a single server,
each listening on a distinct port:
`app['webserver']['port']` and `app['webserver']['ssl_port']` (default
80 and 443, respectively), as well as the corresponding `global` values,
will allow the user to override the port that the application listens to
in Apache2 or nginx.
Allow user to override which template is used to generate Apache2 or
nginx per-app webserver configurations (aka "site configs"):
`app['webserver']['site_config_template']` and
`app['webserver']['site_config_template_cookbook']` (defaults are
`appserver.#{webserver}.conf.erb` and `opswork_ruby`, respectively), as
well as the corresponding `global` values, will allow the user to
specify which template (from which cookbook) should be used to render
the webserver site configuration.
Fixes ajgon#100
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As an opsworks_ruby user, I would like to be able to override the port(s) used by each application that I am deploying, so that I can deploy multiple apps on the same server. I would also like the ability to choose which template is used to render the webserver site configuration stanza, so that I can apply complex customizations for my application that may not be easily implemented using the
extra_configtext blob approach.Implementation details:
app['webserver']['port']andapp['webserver']['ssl_port'](default 80 and 443, respectively), as well as the correspondingglobalvalues, will allow the user to override the port that the application listens to in Apache2 or nginx.app['webserver']['site_config_template']andapp['webserver']['site_config_template_cookbook'](defaults areappserver.#{webserver}.conf.erbandopswork_ruby, respectively), as well as the correspondingglobalvalues, will allow the user to specify which template (from which cookbook) should be used to render the webserver site configuration.The text was updated successfully, but these errors were encountered: