Apache starting but disabled in puphpet

10 views
Skip to first unread message

Milton DC

unread,
Sep 16, 2015, 9:34:18 AM9/16/15
to Vagrant
I am a new vagrant user.  I am using it with virtual box 5.   Even though apache is disabled in the yaml file, it starts anyway.  This interferes with nginx.  Can someone explain what is launching apache?  The apache part of the puphpet yaml looks like this.  It took me weeks to figure out why you spelled puphpet this way ;)    I omitted the vhosts: part.

apache:
    install: '0'
    settings:
        user: www-data
        group: www-data
        default_vhost: false
        manage_user: false
        manage_group: false
        sendfile: 0
    modules:
        - rewrite

Alvaro Miranda Aguilera

unread,
Sep 18, 2015, 12:02:23 AM9/18/15
to vagra...@googlegroups.com
probably the base box got apache installed and the service is auto starting.

Can you run an script to stop apache before starting nginx?
> --
> This mailing list is governed under the HashiCorp Community Guidelines -
> https://www.hashicorp.com/community-guidelines.html. Behavior in violation
> of those guidelines may result in your removal from this mailing list.
>
> GitHub Issues: https://github.com/mitchellh/vagrant/issues
> IRC: #vagrant on Freenode
> ---
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/aa9238a3-71da-4c5c-a444-52d3e5b98195%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages