Vagrant does not bind my site folder on "vagrant resume" or "vagrant up"

trellis
1

i am able to bind the the folder when i first do a provision, but after a while vagrant up or vagrant resume does not help.

here is my wordpress_sites.yaml

wordpress_sites:
  intentaware:
    site_hosts:
      - example.dev
    local_path: "../site" # path targeting local Bedrock site directory (relative to Ansible root)
    site_install: true
    site_title: example
    admin_user: hansolo
    admin_password: nogoodpassword
    admin_email: admin@example.dev
    multisite:
      enabled: false
      subdomains: false
    ssl:
      enabled: false
    cache:
      enabled: false
      duration: 30s
    env:
      disable_wp_cron: true
      wp_home: http://example.dev
      wp_siteurl: http://example.dev/wp
      wp_env: development
      db_name: example
      db_user: example
      db_password: nogoodpassword

what i could be doing wrong that it fails to run?

2

so i did vagrant ssh and did a nginx log inspection, because my folder were being bind correctly.

i got this

2015/12/04 10:30:22 [warn] 827#0: conflicting server name "example.dev" on 0.0.0.0:80, ignored

went out and deleted /etc/sites-available/example.com

problem solved.

3 Likes