roots / roots-example-project.com Goto Github PK

I followed the instructions but ran into this error after running vagranut up:

==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
NFS is reporting that your exports file is invalid. Vagrant does
this check before making any changes to the file. Please correct
the issues below and execute "vagrant reload":

exports:5: path contains non-directory or non-existent components: /Users/alexburi/Projects/dianaweymar/site
exports:5: no usable directories in export entry
exports:5: using fallback (marked offline): /

I'm fairly new to using virtual servers so I'm not sure if I'm doing something wrong here or not...

Fyi, the site right now isn't working for travelers that come across it.

INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: D:/HashiCorp/Vagrant/embedded/gems/gems/vagra
nt-1.8.7/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
INFO global: Loading plugins!
INFO manager: Registered plugin: vagrant-share
INFO vagrant: vagrant invoked: ["--debug"]
DEBUG vagrant: Creating Vagrant environment
INFO environment: Environment initialized (#Vagrant::Environment:0x21e9c28)
INFO environment: - cwd: D:/roots/roots-example-project.com/trellis
INFO environment: Home path: D:/d/.vagrant.d
DEBUG environment: Effective local data path: D:/roots/roots-example-project.com
/trellis/.vagrant
INFO environment: Local data path: D:/roots/roots-example-project.com/trellis/.
vagrant
DEBUG environment: Creating: D:/roots/roots-example-project.com/trellis/.vagrant

INFO environment: Running hook: environment_plugins_loaded
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: environment_plugins_loaded #<Vagrant::Action::Buil
der:0x284fc70>
INFO environment: Running hook: environment_load
INFO runner: Preparing hooks for middleware sequence...
INFO runner: 1 hooks defined.
INFO runner: Running action: environment_load #<Vagrant::Action::Builder:0x277e
fd8>
INFO cli: CLI: [] nil []
INFO interface: Machine: cli-command ["box"]
INFO interface: Machine: cli-command ["connect"]
INFO interface: Machine: cli-command ["destroy"]
INFO interface: Machine: cli-command ["global-status"]
INFO interface: Machine: cli-command ["halt"]
INFO interface: Machine: cli-command ["help"]
INFO interface: Machine: cli-command ["init"]
INFO interface: Machine: cli-command ["login"]
INFO interface: Machine: cli-command ["package"]
INFO interface: Machine: cli-command ["plugin"]
INFO interface: Machine: cli-command ["port"]
INFO interface: Machine: cli-command ["powershell"]
INFO interface: Machine: cli-command ["provision"]
INFO interface: Machine: cli-command ["push"]
INFO interface: Machine: cli-command ["rdp"]
INFO interface: Machine: cli-command ["reload"]
INFO interface: Machine: cli-command ["resume"]
INFO interface: Machine: cli-command ["share"]
INFO interface: Machine: cli-command ["snapshot"]
INFO interface: Machine: cli-command ["ssh"]
INFO interface: Machine: cli-command ["ssh-config"]
INFO interface: Machine: cli-command ["status"]
INFO interface: Machine: cli-command ["suspend"]
INFO interface: Machine: cli-command ["up"]
INFO interface: Machine: cli-command ["version"]
INFO interface: info: Usage: vagrant [options] []

-v, --version                    Print the version and exit.
-h, --help                       Print this help.

Common commands:
box manages boxes: installation, removal, etc.
connect connect to a remotely shared Vagrant environment
destroy stops and deletes all traces of the vagrant machine
global-status outputs status Vagrant environments for this user
halt stops the vagrant machine
help shows the help for a subcommand
init initializes a new Vagrant environment by creating a Vagrant
file
login log in to HashiCorp's Atlas
package packages a running vagrant environment into a box
plugin manages plugins: install, uninstall, update, etc.
port displays information about guest port mappings
powershell connects to machine via powershell remoting
provision provisions the vagrant machine
push deploys code in this environment to a configured destinatio
n
rdp connects to machine via RDP
reload restarts vagrant machine, loads new Vagrantfile configurati
on
resume resume a suspended vagrant machine
share share your Vagrant environment with anyone in the world
snapshot manages snapshots: saving, restoring, etc.
ssh connects to machine via SSH
ssh-config outputs OpenSSH valid configuration to connect to the machi
ne
status outputs status of the vagrant machine
suspend suspends the machine
up starts and provisions the vagrant environment
version prints current and latest Vagrant version

For help on any individual command run vagrant COMMAND -h

Additional subcommands are available, but are either more advanced
or not commonly used. To see all subcommands, run the command
vagrant list-commands.

Usage: vagrant [options] []

-v, --version                    Print the version and exit.
-h, --help                       Print this help.

Common commands:
box manages boxes: installation, removal, etc.
connect connect to a remotely shared Vagrant environment
destroy stops and deletes all traces of the vagrant machine
global-status outputs status Vagrant environments for this user
halt stops the vagrant machine
help shows the help for a subcommand
init initializes a new Vagrant environment by creating a Vagrant
file
login log in to HashiCorp's Atlas
package packages a running vagrant environment into a box
plugin manages plugins: install, uninstall, update, etc.
port displays information about guest port mappings
powershell connects to machine via powershell remoting
provision provisions the vagrant machine
push deploys code in this environment to a configured destinatio
n
rdp connects to machine via RDP
reload restarts vagrant machine, loads new Vagrantfile configurati
on
resume resume a suspended vagrant machine
share share your Vagrant environment with anyone in the world
snapshot manages snapshots: saving, restoring, etc.
ssh connects to machine via SSH
ssh-config outputs OpenSSH valid configuration to connect to the machi
ne
status outputs status of the vagrant machine
suspend suspends the machine
up starts and provisions the vagrant environment
version prints current and latest Vagrant version

For help on any individual command run vagrant COMMAND -h

Additional subcommands are available, but are either more advanced
or not commonly used. To see all subcommands, run the command
vagrant list-commands.
INFO environment: Running hook: environment_unload
INFO loader: Set :root = ["#<Pathname:D:/roots/roots-example-project.com/trelli
s/Vagrantfile>"]
DEBUG loader: Populating proc cache for #<Pathname:D:/roots/roots-example-projec
t.com/trellis/Vagrantfile>
DEBUG loader: Load procs for pathname: D:/roots/roots-example-project.com/trelli
s/Vagrantfile
INFO interface: warn: Installing plugin vagrant-bindfs
Installing plugin vagrant-bindfs
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BundlerError: Bundler, the underlying system V
agrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

Could not fetch specs from https://gems.hashicorp.com/

Warning: this Gemfile contains multiple primary sources. Using source more tha
n once without a block is a security risk, and may result in installing unexpect
ed gems. To resolve this warning, use a block to indicate which gems should come
from the secondary source. To upgrade this warning to an error, run bundle con fig disable_multisource true.Retrying fetcher due to error (2/4): Bundler::HTTP
Error Could not fetch specs from https://gems.hashicorp.com/Retrying fetcher due
to error (3/4): Bundler::HTTPError Could not fetch specs from https://gems.hash
icorp.com/Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetc
h specs from https://gems.hashicorp.com/>
ERROR vagrant: Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

Could not fetch specs from https://gems.hashicorp.com/

Warning: this Gemfile contains multiple primary sources. Using source more tha
n once without a block is a security risk, and may result in installing unexpect
ed gems. To resolve this warning, use a block to indicate which gems should come
from the secondary source. To upgrade this warning to an error, run bundle con fig disable_multisource true.Retrying fetcher due to error (2/4): Bundler::HTTP
Error Could not fetch specs from https://gems.hashicorp.com/Retrying fetcher due
to error (3/4): Bundler::HTTPError Could not fetch specs from https://gems.hash
icorp.com/Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetc
h specs from https://gems.hashicorp.com/
ERROR vagrant: D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant
/plugin/manager.rb:87:in rescue in install_plugin' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/plugin/manager .rb:44:in install_plugin'
D:/roots/roots-example-project.com/trellis/lib/trellis/vagrant.rb:21:in block i n ensure_plugins' D:/roots/roots-example-project.com/trellis/lib/trellis/vagrant.rb:13:in each'
D:/roots/roots-example-project.com/trellis/lib/trellis/vagrant.rb:13:in ensure_ plugins' D:/roots/roots-example-project.com/trellis/Vagrantfile:18:in <top (required)>'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader.
rb:207:in load' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader. rb:207:in block in procs_for_path'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config.rb:53:i
n block in capture_configures' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config.rb:48:i n synchronize'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config.rb:48:i
n capture_configures' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader. rb:205:in procs_for_path'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader.
rb:191:in procs_for_source' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader. rb:67:in block in set'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader.
rb:61:in each' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/config/loader. rb:61:in set'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb
:441:in config_loader' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb :746:in vagrantfile'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb
:492:in host' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb :214:in block in action_runner'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/runner.
rb:33:in call' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/action/runner. rb:33:in run'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb
:479:in hook' D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/environment.rb :728:in unload'
D:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:192:in `

Could not fetch specs from https://gems.hashicorp.com/

Warning: this Gemfile contains multiple primary sources. Using source more tha
n once without a block is a security risk, and may result in installing unexpect
ed gems. To resolve this warning, use a block to indicate which gems should come
from the secondary source. To upgrade this warning to an error, run bundle con fig disable_multisource true.Retrying fetcher due to error (2/4): Bundler::HTTP
Error Could not fetch specs from https://gems.hashicorp.com/Retrying fetcher due
to error (3/4): Bundler::HTTPError Could not fetch specs from https://gems.hash
icorp.com/Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetc
h specs from https://gems.hashicorp.com/
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

Could not fetch specs from https://gems.hashicorp.com/

Warning: this Gemfile contains multiple primary sources. Using source more tha
n once without a block is a security risk, and may result in installing unexpect
ed gems. To resolve this warning, use a block to indicate which gems should come
from the secondary source. To upgrade this warning to an error, run bundle con fig disable_multisource true.Retrying fetcher due to error (2/4): Bundler::HTTP
Error Could not fetch specs from https://gems.hashicorp.com/Retrying fetcher due
to error (3/4): Bundler::HTTPError Could not fetch specs from https://gems.hash
icorp.com/Retrying fetcher due to error (4/4): Bundler::HTTPError Could not fetc
h specs from https://gems.hashicorp.com/
INFO interface: Machine: error-exit ["Vagrant::Errors::BundlerError", "Bundler,
the underlying system Vagrant uses to install plugins,\nreported an error. The
error is shown below. These errors are usually\ncaused by misconfigured plugin i
nstallations or transient network\nissues. The error from Bundler is:\n\nCould n
ot fetch specs from https://gems.hashicorp.com/\n\nWarning: this Gemfile contain
s multiple primary sources. Using source more than once without a block is a s
ecurity risk, and may result in installing unexpected gems. To resolve this warn
ing, use a block to indicate which gems should come from the secondary source. T
o upgrade this warning to an error, run bundle config disable_multisource true
.Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs f
rom https://gems.hashicorp.com/Retrying fetcher due to error (3/4): Bundler::HTT
PError Could not fetch specs from https://gems.hashicorp.com/Retrying fetcher du
e to error (4/4): Bundler::HTTPError Could not fetch specs from https://gems.has
hicorp.com/"]

D:\roots\roots-example-project.com\trellis>.editorconfig

Ansible task failing

TASK: [php | Start php5-fpm service]

Also effects NOTIFIED: [common | reload php-fpm]

Oddly, starting the service manually works fine.

[DEPRECATION WARNING]: The comma separated role spec format, use the yaml/explicit format instead.. This feature will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

Since sage/lib/config.php adds soil functions by default I suggest to activate the plugin also by default (not just installing it), what do you think?

Mac 10.7.5
NPM v3.8.6
Node v5.10.1

[email protected] install /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/fsevents
node-pre-gyp install --fallback-to-build

[fsevents] Success: "/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/fsevents/lib/binding/Release/node-v47-darwin-x64/fse.node" is installed via remote

[email protected] install /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/node-sass
node scripts/install.js

Binary downloaded and installed at /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/node-sass/vendor/darwin-x64-47/binding.node

[email protected] postinstall /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/spawn-sync
node postinstall

[email protected] postinstall /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/node-sass
node scripts/build.js

/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/node-sass/vendor/darwin-x64-47/binding.node exists.
testing binary.
Binary is fine; exiting.

[email protected] postinstall /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/pngcrush-bin
node lib/install.js

⚠ The /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/optipng-bin/vendor/optipng binary doesn't seem to work correctly
⚠ optipng pre-build test failed
ℹ compiling from source
✔ optipng built successfully

[email protected] postinstall /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/jpegtran-bin
node lib/install.js

⚠ The /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/jpegtran-bin/vendor/jpegtran binary doesn't seem to work correctly
⚠ jpegtran pre-build test failed
ℹ compiling from source
✖ Error: touch configure.ac aclocal.m4 configure Makefile.am Makefile.in && ./configure --disable-shared --prefix="/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/jpegtran-bin/vendor" --bindir="/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/jpegtran-bin/vendor" && make install
Command failed: ./configure --disable-shared --prefix="/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/jpegtran-bin/vendor" --bindir="/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/jpegtran-bin/vendor"
configure: error: installation or configuration problem: assembler cannot create object files.

at ChildProcess.exithandler (child_process.js:202:12)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at maybeClose (internal/child_process.js:850:16)
at Socket.<anonymous> (internal/child_process.js:323:11)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at Pipe._onclose (net.js:475:12)

[email protected] postinstall /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/gifsicle
node lib/install.js

⚠ The /Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/gifsicle/vendor/gifsicle binary doesn't seem to work correctly
⚠ gifsicle pre-build test failed
ℹ compiling from source
✖ Error: autoreconf -ivf && ./configure --disable-gifview --disable-gifdiff --prefix="/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/gifsicle/vendor" --bindir="/Users/samiam/Sites/roots-example-project.com/site/web/app/themes/sage/node_modules/gifsicle/vendor" && make install
Command failed: autoreconf -ivf
/bin/sh: autoreconf: command not found

at ChildProcess.exithandler (child_process.js:202:12)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at maybeClose (internal/child_process.js:850:16)
at Socket.<anonymous> (internal/child_process.js:323:11)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at Pipe._onclose (net.js:475:12)

Running ansible-playbook -i hosts/production server.yml a second time leads to:

TASK: [mariadb | Set root user password] ************************************** 
failed: [104.xxx.xxx.xx] => (item=Raven) => {"failed": true, "item": "Raven"}
msg: (1396, "Operation CREATE USER failed for 'root'@'raven'")
ok: [104.xxx.xxx.xx] => (item=127.0.0.1)
ok: [104.xxx.xxx.xx] => (item=::1)
ok: [104.xxx.xxx.xx] => (item=localhost)

FATAL: all hosts have already failed -- aborting

I need to delete the root@Raven user in MariaDB in order to proceed. Is there a way to skip this user creation on subsequent runs?

Bug reports and feature requests

• I've read the guidelines for Contributing to Roots Projects
• This is a bug report for the roots-example-project.com repo and not for Trellis, Bedrock, Sage or Soil
• I've read the docs for Trellis, Bedrock, Sage and Soil (if applicable) and followed them
• This is not a personal support request that should be posted on the Roots Discourse forums

What is the current behavior?

Ancient version of mailhog (1.0.5 (February), 1.0.6 3 days later, 1.1.0(April), 2.0.0 (July)), produces Ansible Deprecation warning due to outdated syntax.:

 mailhog was installed successfully
[DEPRECATION WARNING]: The comma separated role spec format, use the yaml/explicit format instead..
This feature
will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in
 ansible.cfg.

What is the expected or desired behavior?

No deprecation warnings, current compatible versions of tools to take advantage of latest features, bug fixes, etc.

Bug report

Following setup instructions:

ansible-galaxy install -r requirements.yml

Deprecation warning shown above.

Please describe your local environment:

Ansible version: ansible 2.1.1.0

OS: OS X 10.11.6

Vagrant version: Vagrant 1.8.5

Where did the bug happen? Development or remote servers?

Dev system initial setup.

Here is the error: ERROR! Unexpected Exception: (setuptools 1.1.6 (/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python), Requirement.parse('setuptools>=11.3'))

Here is how to fix it: 'pip install --upgrade setuptools --user python'

Might want to update the Readme.

The config here seems to create a local directory with permissions drwx------ and upload that to the server with those same permissions which the web user is not able to access.

SSHing into the server and running

chmod -R 755 /srv/www/example.com/current/web/app/themes/sage/dist

fixes the 404s.

• [x ] I've read the guidelines for Contributing to Roots Projects
• [ x] This request isn't a duplicate of an existing issue
• [ x] I've read the docs and followed them (if applicable)
• [x ] This is not a personal support request that should be posted on the Roots Discourse community

Description

Started up Roots example project which first needed a yarn update and a couple of fixes to the node-sass in order to build.

Finally once I got to the vagrant part I get an Ansible error. So I add the shared file fix into the config.yml. And it runs. But there is no website? There is no localhost, the url https://roots-example-project.test/

Gives a This site can’t be reached roots-example-project.test’s server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN

Has anyone had a similar bug?

This is the only stack trace I’m getting all looks good but nothing is happening.

trellis % vagrant up
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Checking if box ‘bento/ubuntu-18.04’ version ‘202010.24.0’ is up to date…
==> default: Clearing any previously set forwarded ports…
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports…
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running ‘pre-boot’ VM customizations…
==> default: Booting VM…
==> default: Waiting for machine to boot. This may take a few minutes…
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM…
==> default: Setting hostname…
==> default: Configuring and enabling network interfaces…
==> default: Exporting NFS shared folders…
==> default: Preparing to edit /etc/exports. Administrator privileges will be required…
Password:
==> default: Mounting NFS shared folders…
==> default: Mounting shared folders…
default: /vagrant => /Users/benjaminwaye/Sites/roots-example-project.com/trellis
==> default: Machine already provisioned. Run vagrant provision or use the --provision
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running action triggers after up …
==> default: Running trigger…
==> default: Adding vagrant ssh-config for roots-example-project.test to ~/.ssh/config

==> default: Machine ‘default’ has a post vagrant up message. This is a message
==> default: from the creator of the Vagrantfile, and not from Vagrant itself:
==> default:
==> default: Your Trellis Vagrant box is ready to use!
==> default: * Composer and WP-CLI commands need to be run on the virtual machine
==> default: for any post-provision modifications.
==> default: * You can SSH into the machine with vagrant ssh.
==> default: * Then navigate to your WordPress sites at /srv/www
==> default: or to your Trellis files at /home/vagrant/trellis.

Steps to reproduce

1. Follow instructions.
2. Fix all the errors that pop up
3. Pray to whatever diety you hold dear

Expected behavior:

It would work and let me access root-example-project.test

Actual behavior:

The above stack trace and no error and no site.

Reproduces how often: Every time

Versions

Mac OS Catalina 10.15.7
latest version of the project

When trying to run the 'composer require roots/soil' command, It's returning this error:

vagrant@example:/srv/www/example.com/current$ composer require roots/soil
No command 'composer' found, did you mean:
 Command 'compose' from package 'mime-support' (main)
composer: command not found

If I check the folder, there is a composer.json file.

vagrant@example:/srv/www/example.com/current$ ls
CHANGELOG.md  composer.json  composer.lock  config  CONTRIBUTING.md  LICENSE.md  README.md  ruleset.xml  vendor  web  wp-cli.yml

If you have two or more roots-example-project type projects on your machine you might run into:

/Users/austinpray/DEV/project/project.com/Vagrantfile:6: warning: already initialized constant ANSIBLE_PATH
/Users/austinpray/DEV/roots.io/Vagrantfile:4: warning: previous definition of ANSIBLE_PATH was here

when running vagrant global-status --prune

Edit: Just realized that this also a trellis bug.

Hey, just setting this up as a quick tryout. You've got roles missing in the ansible provisioner.

• php5-xdebug
• logrotate

If following the instructions on a fresh server, under Sage/Theme

Add Soil: $ cd site && composer require roots/soil

Composer doesn't exist as it's not listed under requirements to continue, nor is i listed in Sage/Theme requirements, so continuing is not possible. Could you please update the requirements?

https://getcomposer.org/doc/00-intro.md or to globally install:

curl -sS https://getcomposer.org/installer | php
mv composer.phar /usr/local/bin/composer

I want to start a discussion about making this repo a programmatically generated repo.

Problem

Our projects move fast. This process will fail us as roots-example-project diverges further and further from the base bedrock, sage, and trellis repos.

Proposed solution

We should make a program that takes a set of static transforms and combines and transforms the base repos accordingly. The transforms can be defined in perhaps a yaml file or something.

Design Considerations

Be able to specify versions of each repo

versions:
  trellis: stable
  sage: stable
  bedrock: stable

versions:
  trellis: HEAD
  sage: 8.2.1
  bedrock: stable

For this repo we would probably use stable. Stable is the latest release according to GitHub.

Merge ansible yaml files

Given an ansible yaml file like this: https://raw.githubusercontent.com/roots/roots-example-project.com/06c7f6abf84d58babaeef6a583469611cdd9b6ac/ansible/group_vars/development

If the repo source is this:

mysql_root_password: devpw

web_user: vagrant

wordpress_sites:
  example.com:
    site_hosts:
      - example.dev
    local_path: ../site # path targeting local Bedrock site directory (relative to Ansible root)
    repo: [email protected]:roots/bedrock.git
    site_install: true
    site_title: Example Site
    admin_user: admin
    admin_password: admin
    admin_email: [email protected]
    multisite:
      enabled: false
      subdomains: false
    ssl:
      enabled: false
    cache:
      enabled: false
      duration: 30s
    system_cron: true
    env:
      wp_home: http://example.dev
      wp_siteurl: http://example.dev/wp
      wp_env: development
      db_name: example_dev
      db_user: example_dbuser
      db_password: example_dbpassword

php_error_reporting: 'E_ALL'
php_display_errors: 'On'
php_display_startup_errors: 'On'
php_track_errors: 'On'
php_mysqlnd_collect_memory_statistics: 'On'
php_opcache_enable: 0

xdebug_install: false
php_xdebug_remote_enable: true
php_xdebug_remote_connect_back: true
php_xdebug_remote_host: localhost
php_xdebug_remote_port: 9000
php_xdebug_remote_log: /tmp/xdebug.log
php_xdebug_idekey: XDEBUG
php_max_nesting_level: 200

and my transform looked like this:

wordpress_sites:
  roots-example-project.com:
    site_hosts:
      - roots-example-project.dev

My output would be

mysql_root_password: devpw

web_user: vagrant

wordpress_sites:
  roots-example-project.com:
    site_hosts:
      - roots-example-project.dev
    local_path: ../site # path targeting local Bedrock site directory (relative to Ansible root)
    repo: [email protected]:roots/bedrock.git
    site_install: true
    site_title: Example Site
    admin_user: admin
    admin_password: admin
    admin_email: [email protected]
    multisite:
      enabled: false
      subdomains: false
    ssl:
      enabled: false
    cache:
      enabled: false
      duration: 30s
    system_cron: true
    env:
      wp_home: http://example.dev
      wp_siteurl: http://example.dev/wp
      wp_env: development
      db_name: example_dev
      db_user: example_dbuser
      db_password: example_dbpassword

php_error_reporting: 'E_ALL'
php_display_errors: 'On'
php_display_startup_errors: 'On'
php_track_errors: 'On'
php_mysqlnd_collect_memory_statistics: 'On'
php_opcache_enable: 0

xdebug_install: false
php_xdebug_remote_enable: true
php_xdebug_remote_connect_back: true
php_xdebug_remote_host: localhost
php_xdebug_remote_port: 9000
php_xdebug_remote_log: /tmp/xdebug.log
php_xdebug_idekey: XDEBUG
php_max_nesting_level: 200

Benefits

Easier to maintain this repo

This would keep our project easy to maintain because we are not manually making and merging changes. Also the transforms needed on top of our base repos are declared explicitly. No git cherry picking. No merge conflicts. Also a clear audit trail of what needs to happen to create the stack. The more transforms we have to do the more indications of low cohesion between our products.

Easier to start projects

On top of making this repo easy to maintain: this could also be used by us as a standalone tool to generate private projects.

Integration testing

versions:
  trellis: HEAD
  sage: HEAD
  bedrock: HEAD

or

versions:
  trellis: 4fff69497270305966d0e9456a546e12def148cb
  sage: HEAD
  bedrock: HEAD

Is basically an integration test. We need to make sure our projects have high cohesion. Again: our projects move so fast that doing this manually is not feasible. I should be able to test the full stack of roots projects easily. What is good for our users is good for us as maintainers. This allows us to easily determine whether a change to a particular repo (bedrock, bedrock-ansible) is a breaking change. It also allows us to go back in time and check for incompatibilities.

Questions

Yaml format?

Not quite sure what would be better:

versions:
  trellis: stable
  sage: stable
  bedrock: stable

repos:
  trellis: roots/trellis
  sage: roots/sage
  bedrock: roots/bedrock

or

sources:
  trellis:
    version: stable
    repo: roots/trellis

or

trellis:
  version: stable
  repo: roots/trellis

The later looks pretty good. Dunno.

Contents of this repo?

This repo is would just be the latest compiled output of the generator. I don't think there is anything wrong with this. That way people can have a consistent static reference as to what the latest and greatest looks like.

Sage generator

How would this interact with our idea of a sage generator? If a sage generator existed this would definitely use that generator instead of manually transforming the repo. Although the generator would have to comply with the design considerations of this project.

Trellis-cli

How would this interact with the trellis CLI? Probably little to no affect.

Implementation language?

Maybe ruby or python? Those are generally pretty easily available to users on the *nix computers. Ruby has lots of really useful yaml gems and such. Go is also an option 😎. Leaning towards ruby so @swalkinshaw could sling some loc with me.

Split CLI and lib

It might be a good idea to split the project into roots-project-generator and roots-project-generator-cli. That way we could perhaps expose roots-project-generator as a web application and keep roots-project-generator-cli as a CLI interface for the library. This will also help in writing tests.

Is there any reason why there's no vault.yml file in this repo?

Hello,
When i clone Trellis: $ git clone --depth=1 [email protected]:roots/trellis.git && rm -rf trellis/.git
i have this :
Cloning into 'trellis'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Thank you for your help !!

I get

There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /Users/viktor/sites/example.com/Vagrantfile
Message: ./group_vars/development file not found. Please set ANSIBLE_PATH in Vagrantfile

If you move the Vagrantfile to root directory (#5 in instructions) you'll have to update the ANSIBLE_PATH from '' to 'ansible' (the ansible directory name)

Terms

• I have read the guidelines for Contributing to Roots Projects
• This request is not a duplicate of an existing issue
• I have read the docs and followed them (if applicable)
• I have seached the Roots Discourse for answers and followed them (if applicable)
• This is not a personal support request that should be posted on the Roots Discourse community

Description

What's wrong?

When trying to install the composer dependencies using composer v2 (which recent Trellis also does, hence it also causes a deployment error there), composer fails to install the dependencies because the composer.json expects composer-plugin-api v1.x while composer v2 has the composer-plugin-api v2.x.

What have you tried?

composer install inside the site/ directory of this repository.

What insights have you gained?

Incompatibilities with composer v2 which is the current version and also used in recent Trellis.

Possible solutions

Update the composer dependencies / update the composer.lock lockfile.

Temporary workarounds

Steps To Reproduce

A.

1. Use this repository as a Trellis site (repo: [email protected]:roots/roots-example-project.com.git).
2. Deploy the site, note that Trellis deployment fails.

B.

1. Clone this repository (e.g. git clone [email protected]:roots/roots-example-project.com.git).
2. Go into the site/ directory (cd roots-example-project.com/site.
3. Invoke composer install.
   Note the error that occurs.

Expected Behavior

No composer errors when installing the dependencies using composer install.

Actual Behavior

composer error when using composer install.

Relevant Log Output

composer install
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Your lock file does not contain a compatible set of packages. Please run composer update.

  Problem 1
    - composer/installers is locked to version v1.6.0 and an update of this package was not requested.
    - composer/installers v1.6.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.
  Problem 2
    - roots/wordpress-core-installer is locked to version 1.1.0 and an update of this package was not requested.
    - roots/wordpress-core-installer 1.1.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.
  Problem 3
    - composer/installers v1.6.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api[2.3.0] but it does not match the constraint.
    - roots/wp-password-bcrypt 1.0.0 requires composer/installers ~1.0 -> satisfiable by composer/installers[v1.6.0].
    - roots/wp-password-bcrypt is locked to version 1.0.0 and an update of this package was not requested.

Versions

• Update to WordPress 5.2 (#432)

When i am running this command : composer require --dev phpunit/phpunit ^7.0

Then it's showing these error:

No command 'composer' found, did you mean:
Command 'compose' from package 'mime-support' (main)
composer: command not found

please look at this
Thanks in advance

I get following error message –

failed:` [default] (item=roots-example-project.com) => {"changed": false, "item": {"key": "roots-example-project.com", "value": {"admin_email": "[email protected]", "cache": {"enabled": false}, "local_path": "../site", "multisite": {"enabled": false}, "site_hosts": [{"canonical": "roots-example-project.test", "redirects": ["www.roots-example-project.test"]}], "ssl": {"enabled": false, "provider": "self-signed"}}}, "msg": "Composer could not find a composer.json file in /srv/www/roots-example-project.com/current To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ \"Getting Started\" section", "stdout": "Composer could not find a composer.json file in /srv/www/roots-example-project.com/current\nTo initialize a project, please create a composer.json file as described in the https://getcomposer.org/ \"Getting Started\" section\n", "stdout_lines": ["Composer could not find a composer.json file in /srv/www/roots-example-project.com/current", "To initialize a project, please create a composer.json file as described in the https://getcomposer.org/ \"Getting Started\" section"]}

Why oh why is the entry level so difficult on trellis/bedrock? :(

Hi there - I have run through the setup on the Readme and all of that went fine, until I try to view the site but I am getting a page not found error.... I have added an entry to my hosts file, as:

192.168.50.5 roots-example-project.dev

But no luck - what could I be missing? What am I doing wrong?

Thanks,

Nick

Bug reports and feature requests

• I've read the guidelines for Contributing to Roots Projects
• This is a bug report for the roots-example-project.com repo and not for Trellis, Bedrock, Sage or Soil
• I've read the docs for Trellis, Bedrock, Sage and Soil (if applicable) and followed them
• This is not a personal support request that should be posted on the Roots Discourse forums

Replace any X with your information.

Bug report

• Cloned this repo as of today
• ran ansible-galaxy install -r requirements.yml in roots-example-project.com/trellis
• ran npm install & bower install & gulp in roots-example-project.com/site/web/app/themes/sage
• When running vagrant up in roots-example-project.com/trellis it can't find 'bento/ubuntu-16.04'

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'bento/ubuntu-16.04' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
The box 'bento/ubuntu-16.04' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/bento/ubuntu-16.04"]
Error:

Please describe your local environment:

Ansible version: 2.2.0.0
OS: MacOS X 10.12.1 (Sierra)
Vagrant version: 1.8.7
VirtualBox: 5.1.8
vagrant-bindfs: 0.4.11
vagrant-hostmanager: 1.8.5

Where did the bug happen? Development or remote servers?

During development

What is the current behavior?

When calling vagrant up, the following message gets returned:

This Vagrant environment has specified that it requires the Vagrant
version to satisfy the following version requirements:

  >= 1.8.5

You are running Vagrant 1.8.1, which does not satisfy
these requirements. Please change your Vagrant version or update
the Vagrantfile to allow this Vagrant version. However, be warned
that if the Vagrantfile has specified another version, it probably has
good reason to do so, and changing that may cause the environment to
not function properly.

Please describe your local environment:

Ansible version: 2.1.2.0

OS: 10.11.6

Vagrant version: 1.8.1

Do I need to update Ansible, or edit the min requirements?

Based on our conversation on Roots Discourse I'm opening a ticket here about the outdated documentation/project files. Trellis now uses different hook names/structure so it would be good to update this project or release a new version with the new standards.

Thanks

I'm getting a error:

fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

and it's specifically in the ansible bit.

Clone Trellis: $ git clone --depth=1 [email protected]:roots/trellis.git ansible && rm -rf ansible/.git

• I've read the guidelines for Contributing to Roots Projects
• This request isn't a duplicate of an existing issue
• I've read the docs and followed them (if applicable)
• This is not a personal support request that should be posted on the Roots Discourse community

Description

[Description of the issue]
I've followed the steps and tried plenty of different versions, configurations etc. with no luck on getting the dev site up and running properly on WSL2

Steps to reproduce

1. Clone repo
2. install theme
3. vagrant up

Expected behavior: [What you expect to happen]
The site is expected to be available at the local address

Actual behavior: [What actually happens]
I'm sent to a google search of the web url as nothing loads

Reproduces how often: [What percentage of the time does it reproduce?]
Every time

Versions

You can get this information from referencing CHANGELOG.md. Also, please include the OS and what version of the OS you're running.

Additional information

Any additional information, configuration or data that might be necessary to reproduce the issue.

https://github.com/roots/roots-example-project.com/blob/master/README.md#bedrock says:

here's only one custom option set in this example: WP_DEFAULT_THEME

but I can´t find it in the application.php file and sage is not the default theme.

Under Instructions it says Here's how this example project was created. So is that part of the set up process?

Because after running through the steps under Local development setup I seem to end up with a folder structure as described under Instructions.

The only problem is when I visit roots-example-project.com I get IP address could not be found.

I had to install the Ansible roles from Ansible Galaxy with ansible-galaxy install -r requirements.yml. After this the vagrant start with vagrant up succeeded.
This could be part of the provision process or just a hint for the Readme?

When trying to clone the trellis repo, I get:

➜  trekkingpartners  git clone --depth=1 [email protected]:roots/trellis.git ansible && rm -rf ansible/.git
Cloning into 'ansible'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Is there something I'm doing wrong?

• [x ] I've read the guidelines for Contributing to Roots Projects
• [ x] This request isn't a duplicate of an existing issue
• [ x] I've read the docs and followed them (if applicable)
• [ x] This is not a personal support request that should be posted on the Roots Discourse community

Description

yarn fails with below error

Cannot download "https://github.com/sass/node-sass/releases/download/v4.9.4/linux-x64-72_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

  export HTTP_PROXY=http://example.com:1234

Steps to reproduce

1. Do fresh windows setup as mentioned in https://roots.io/getting-started/docs/development-environment-recommendations/
2. Clone repository
3. Run composer install
4. run yarn

Expected behavior:
No error

Actual behavior:
Error as mentioned above

Reproduces how often:
Always

I had problems with getting bedrock-ansible to work so I decided see if I could get this project up and running but it fails at the same point.

The Vagrant provisioning fails on starting php5-fpm:

TASK: [php | Start php5-fpm service] ******************************************
failed: [default] => {"failed": true}

FATAL: all hosts have already failed -- aborting

PLAY RECAP ********************************************************************
           to retry, use: --limit @/Users/harald/dev.retry

default                    : ok=29   changed=13   unreachable=0    failed=1

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Even with the debug flag in vagrant I cant find out why it fails. Any suggestions?

• I've read the guidelines for Contributing to Roots Projects
• This is a bug report for the roots-example-project.com repo and not for Trellis, Bedrock, Sage or Soil
• I've read the docs for Trellis, Bedrock, Sage and Soil (if applicable) and followed them
• This is not a personal support request that should be posted on the Roots Discourse forums

What is the current behavior?

The demo installation instructions fail with an error message on the TASK [wordpress-install : Install Dependencies with Composer] step:

failed: [default] (item={'value': {u'multisite': {u'enabled': False}, u'cache': {u'enabled': False}, u'ssl': {u'enabled': True, u'provider': u'self-signed'}, u'local_path': u'../site', u'site_hosts': [u'roots-example-project.dev'], u'admin_email': u'[email protected]'}, 'key': u'roots-example-project.com'}) => {"changed": true, "cmd": ["composer", "install"], "delta": "0:00:00.085437", "end": "2016-06-16 18:42:44.447055", "failed": true, "item": {"key": "roots-example-project.com", "value": {"admin_email": "[email protected]", "cache": {"enabled": false}, "local_path": "../site", "multisite": {"enabled": false}, "site_hosts": ["roots-example-project.dev"], "ssl": {"enabled": true, "provider": "self-signed"}}}, "rc": 1, "start": "2016-06-16 18:42:44.361618", "stderr": "You are running composer with xdebug enabled. This has a major impact on runtime performance. See https://getcomposer.org/xdebug\nRunning composer as root/super user is highly discouraged as packages, plugins and scripts cannot always be trusted\nComposer could not find a composer.json file in /srv/www/roots-example-project.com/current\nTo initialize a project, please create a composer.json file as described in the https://getcomposer.org/ \"Getting Started\" section", "stdout": "", "stdout_lines": [], "warnings": []}

Destroying the vagrant image and retrying consistently produces the same error.

What is the expected or desired behavior?

The demo instructions should work, and I should be able to view the example project.

Bug report

Please provide steps to reproduce, including full log output:

Follow the instructions in the README of this repo exactly as laid out.

Please describe your local environment:

Ansible version: 2.1.0.0
OS: 10.11.5
Vagrant version: 1.8.4

Where did the bug happen? Development or remote servers?

Development server setup

Please provide a repository or your wordpress_sites config (if possible):

N/A

Is there a related Discourse thread or were any utilized (please link them)?

There is a Discourse thread that seems related https://discourse.roots.io/t/stderr-composer-could-not-find-a-composer-json-file-in-var-www-localhost-current/4698/8

# git clone --depth=1 [email protected]:roots/bedrock-ansible.git ansible && rm -rf ansible/.git Cloning into 'ansible'...
The authenticity of host 'github.com (192.30.252.131)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,192.30.252.131' (RSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.

System info:
Ansible 2.7.5; Linux
Trellis 1.0.1: January 16th, 2019

SSH Error: data could not be sent to remote host "roots-example-project.com".
Make sure this host can be reached over ssh
fatal: [roots-example-project.com]: UNREACHABLE! => {"changed": false, "unreachable": true}
to retry, use: --limit @/home/username/roots-example-project.com/trellis/deploy.retry

PLAY RECAP ***********************************************************************************************************************************
localhost : ok=0 changed=0 unreachable=0 failed=0
roots-example-project.com : ok=1 changed=0 unreachable=1 failed=0

Bug reports and feature requests

• I've read the guidelines for Contributing to Roots Projects
• This is a bug report for the roots-example-project.com repo and not for Trellis, Bedrock, Sage or Soil
• I've read the docs for Trellis, Bedrock, Sage and Soil (if applicable) and followed them
• This is not a personal support request that should be posted on the Roots Discourse forums

Bug report

git clone --depth=1 --branch sage-8 [email protected]:roots/sage.git site/web/app/themes/sage && rm -rf site/web/app/themes/sage/.git fails.

When trying to clone the trellis repo, I get:

➜  trekkingpartners  git clone --depth=1 [email protected]:roots/trellis.git ansible && rm -rf ansible/.git
Cloning into 'ansible'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Is there something I'm doing wrong?