Roots Discourse

Root example project not running

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.

Now noticed that I still have the Ansible issue. Following the instructions here: https://www.vagrantup.com/docs/provisioning/ansible_local gives me the following error:

benjaminwaye@MacBook-Pro trellis % vagrant provision

==> default: Running provisioner: ansible_local…
default: Installing Ansible…
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

            add-apt-repository ppa:ansible/ansible -y &&                 apt-get update -y -qq &&                 DEBIAN_FRONTEND=noninteractive apt-get install -y -qq ansible --option "Dpkg::Options::=--force-confold"

Stdout from the command:

Hit:1 LINK InRelease
Ign:2 LINK focal InRelease
Hit:3 LINK focal InRelease
Hit:4 LINK InRelease
Err:5 LINK focal Release
404 Not Found [IP: 91.189.95.83 80]
Hit:6 LINK InRelease
Reading package lists…

Stderr from the command:

E: The repository ‘http://ppa.launchpad.net/ansible/ansible/ubuntu focal Release’ does not have a Release file.

Hade to remove links as new users can only post 4 links