On Wednesday, May 17, 2017 at 5:06:33 PM UTC-4, Poil wrote:
>
> I'm agree with "Debian is just by design stupid, thinks starting all
> services"
> All other integration are really fine, but auto-starting after install is
> terrible for all configuration management :
> Change a path (mysql binary
I'm agree with "Debian is just by design stupid, thinks starting all
services"
All other integration are really fine, but auto-starting after install
is terrible for all configuration management :
Change a path (mysql binary log for example), a mount point (a LV for
mysql) before installing : N
On Monday, May 15, 2017 at 8:16:38 AM UTC-4, R.I. Pienaar wrote:
>
>
> debian will not overwrite configs on package install - suggest you put a
> config down that does what you want first.
>
Or, I dunno, maybe he could could tie the service to the config file, and
restart apache when the config
Hi.
At the current moment I need bind the apache to localhost:80 and nginx
to external_ip:80.
I cannot change nginx config before it installed and debian start nginx
automatic after install package with default configuration (bind to
*:80) => conflict.
So first I stop the apache service, after
15.05.2017 15:16, R.I.Pienaar пишет:
> Debian is just by design stupid, thinks starting all services
> unconfigured on install is a good idea, suggest you use a OS designed to
> be used on servers and not peoples basements.
Yes this is true...
But I can't change OS at current time.
Question why
On Mon, May 15, 2017, at 13:52, Anton Gorlov wrote:
> Hi.
> At the current moment I need bind the apache to localhost:80 and nginx
> to external_ip:80.
> I cannot change nginx config before it installed and debian start nginx
> automatic after install package with default configuration (bind t
Hi.
At the current moment I need bind the apache to localhost:80 and nginx
to external_ip:80.
I cannot change nginx config before it installed and debian start nginx
automatic after install package with default configuration (bind to
*:80) => conflict.
So first I stop the apache service, after
It might be worth pointing out that puppetlabs/apache is a component module
that helps address some of these common issues, and using it instead of
writing your own apache module is probably worth considering in this case.
Rob Nelson
rnels...@gmail.com
On Sun, May 14, 2017 at 3:07 PM, Ramin K w
I'd guess that installing new modules are restarting the service. You
probably need something with better ordering.
class apache {
contain ::apache::install
contain ::apache::config
contain ::apache::service
Class['::apache::install'] ->
Class['::apache::config'] ~>
Class['::apache::
Why do you want to stop it ? I think you want to change the listen port.
So I think something like this will do the job :
package { 'apache2': ensure => installed, }
service { 'apache2':
ensure => running,
enable => true,
}
file { '/etc/apache2/conf.d/listen_port.conf':
content => "your_
Hi.
I need stop service (apache) after it install from puppet.
platform is debian 9 and puppet version is 4.8.2
I my class i wrote:
class webpackages {
exec { 'apachechk':
command => "/bin/systemctl stop apache2;",
onlyif => "/bin/grep -c 'Listen 80' /etc/apache2/ports.
11 matches
Mail list logo
