scotch-io / scotch-box-pro

Scotch Box Pro is a preconfigured Vagrant Box with a full array of LAMP Stack features to get you up and running with Vagrant in no time.

Scotch Box Pro

Just a Dead-Simple Local LAMP/LEMP Stack for Vagrant. Making Vagrant EASY AS EATING CAKE for developers.

Scotch Box is a pre-configured Vagrant Box with a full array of features to get you up and running with Vagrant in no time.

NGINX version: https://github.com/scotch-io/scotch-box-pro-nginx

License Required?

This is a paid version of the original Scotch Box. Go Pro Now! to get access to documentation and new tutorials!

Pro Features

• NEW OS: Ubuntu-17.10!
• NEW PHP: PHP 7.2!
• NEW APACHE: 2.4.29
• NEW NGINX: 1.13.8
• NEW RUBY via RVM: 2.5.0
• NEW NODE via NVM: 8.9.4
• NEW BUILD SCRIPTS
• Fixes a MongoDB and PHP bug
• Makes Laravel routing finally work out of the box with NGINX version
• Adds Drush (Launcher) even though you should do this through Composer these days
• Updated WP-CLI version
• Generally WAY higher versions of everything else

Documentation

• Check out the official docs at: box.scotch.io
• Read the getting started article
• Read the 2.0 release article
• Read the 2.5 release article
• Read the 3.0 release article
• Read the 3.5 release article

More Information

Check-out box.scotch.io to learn more.

scotch-box-pro's Issues

Vagrant up issues

$ vagrant init scotch/box-pro
A Vagrantfile has been placed in this directory. You are now
ready to vagrant up your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
vagrantup.com for more information on using Vagrant.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'scotch/box-pro' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'scotch/box-pro'
default: URL: https://vagrantcloud.com/scotch/box-pro
==> default: Adding box 'scotch/box-pro' (v1.5) for provider: virtualbox
default: Downloading: https://vagrantcloud.com/scotch/boxes/box-pro/versions/1.5/providers/virtualbox.box
default: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
==> default: Successfully added box 'scotch/box-pro' (v1.5) for 'virtualbox'!
==> default: Importing base box 'scotch/box-pro'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'scotch/box-pro' version '1.5' is up to date...
==> default: Setting the name of the VM: scotchBoxPro_default_1599681806762_57459
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2201 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2201
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
[default] GuestAdditions versions on your host (5.2.32) and guest (5.2.6) do not match.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-3ubuntu3).
The following NEW packages will be installed:
linux-headers-4.13.0-21 linux-headers-4.13.0-21-generic
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 11.6 MB of archives.
After this operation, 83.1 MB of additional disk space will be used.
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.142 80]
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.142 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.142 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.142 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21_4.13.0-21.24_all.deb 404 Not Found [IP: 91.189.88.142 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21-generic_4.13.0-21.24_amd64.deb 404 Not Found [IP: 91.189.88.142 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Ign:1 http://security.ubuntu.com/ubuntu artful-security InRelease
Ign:2 http://archive.ubuntu.com/ubuntu artful InRelease
Ign:3 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 InRelease
Get:4 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
Ign:5 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu artful InRelease
Get:6 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release [3,462 B]
Err:7 http://security.ubuntu.com/ubuntu artful-security Release
404 Not Found [IP: 91.189.88.142 80]
Ign:8 http://archive.ubuntu.com/ubuntu artful-updates InRelease
Get:9 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release.gpg [801 B]
Err:4 https://dl.yarnpkg.com/debian stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
Ign:10 http://archive.ubuntu.com/ubuntu artful-backports InRelease
Err:9 http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release.gpg
The following signatures were invalid: EXPKEYSIG D68FA50FEA312927 MongoDB 3.2 Release Signing Key [email protected]
Err:11 http://archive.ubuntu.com/ubuntu artful Release
404 Not Found [IP: 91.189.88.152 80]
Get:12 http://ppa.launchpad.net/ondrej/apache2/ubuntu artful InRelease [20.7 kB]
Err:13 http://archive.ubuntu.com/ubuntu artful-updates Release
404 Not Found [IP: 91.189.88.152 80]
Err:14 http://archive.ubuntu.com/ubuntu artful-backports Release
404 Not Found [IP: 91.189.88.152 80]
Get:15 http://ppa.launchpad.net/ondrej/php/ubuntu artful InRelease [20.8 kB]
Err:16 http://ppa.launchpad.net/longsleep/golang-backports/ubuntu artful Release
404 Not Found [IP: 91.189.95.83 80]
Reading package lists...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
E: The repository 'http://security.ubuntu.com/ubuntu artful-security Release' no longer has a Release file.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.2 Release: The following signatures were invalid: EXPKEYSIG D68FA50FEA312927 MongoDB 3.2 Release Signing Key [email protected]
E: The repository 'http://archive.ubuntu.com/ubuntu artful Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu artful-updates Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu artful-backports Release' no longer has a Release file.
E: The repository 'http://ppa.launchpad.net/longsleep/golang-backports/ubuntu artful Release' does not have a Release file.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-3ubuntu3).
The following NEW packages will be installed:
linux-headers-4.13.0-21 linux-headers-4.13.0-21-generic
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.6 MB of archives.
After this operation, 83.1 MB of additional disk space will be used.
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21_4.13.0-21.24_all.deb 404 Not Found [IP: 91.189.88.152 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21-generic_4.13.0-21.24_amd64.deb 404 Not Found [IP: 91.189.88.152 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
==> default: Checking for guest additions in VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

apt-get install -y linux-headers-uname -r dkms

Stdout from the command:

Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-3ubuntu3).
The following NEW packages will be installed:
linux-headers-4.13.0-21 linux-headers-4.13.0-21-generic
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.6 MB of archives.
After this operation, 83.1 MB of additional disk space will be used.
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.152 80]

Stderr from the command:

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21_4.13.0-21.24_all.deb 404 Not Found [IP: 91.189.88.152 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21-generic_4.13.0-21.24_amd64.deb 404 Not Found [IP: 91.189.88.152 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

[ISSUE] No HTTPS, Feature missing!

Hi,

I purchased a pro version in order to run an Application which relies heavily on HTTPS in authentication process, I don't found anything related to HTTPS.

Could you please add this feature for apache2 and Nginx?

Thanks

Issue with updating packages and web server

if you apt-get update and upgrade, suddenly the symbolic link in the /var/www mapped to your clone dir stops working.

PHP version is still 5.5

I bought ScotchBox Pro after spending hours trying and failing to get php7 up and running. That was the main reason I bought it because I figured there was something in the build scripts that I was missing.

However, after setting up the box, php -v still reports 5.5. What's the deal? Any help would be greatly appreciated.

Multiple active instances at the same time

Scotch Box Pro uses 127.0.0.1 for MySQL Host and SSH Host, so when starting 2 projects using Scotch Box Pro, I am unable to go to the both databases because of some conflict (same IP).

How can this be solved?
Also: Are there are conflicts using two active projects at the same time?

vhost multiple domains old code not working

The code here to use multiple domains on vagrant pro is not working the one from here

https://scotch.io/bar-talk/announcing-scotch-box-2-0-our-dead-simple-vagrant-lamp-stack-improved#toc-multiple-domains-virtual-hosts

How can we get this on this version?

Add a Free and Open Source License to Scotch Box Pro

Given that Scotch Box appears to no longer be receiving updates, and Scotch.io has announced they are closing, please consider explicitly adding a FOSS-compatible license to the relevant repos (Scotch Box Free, Scotch Box Pro, the builder scripts, and the nginx varations) so that anyone still interested in using it can feel comfortable repackaging and updating. I'd be happy to put a little time into updating it for 2021 and posting the corresponding build scripts and boxes if there's still interest out there.

No longer able to install Scotbox - Self Signed Certificate Issue

The box I use for all my local development is no longer working.

Maybe the most frequent non git and vagrant commands I run on my box is : "git clone https://github.com/scotch-io/scotch-box-pro . "

Up until today it has always worked without fail. But now I get the following error:

"Cloning into 'scotch-box-pro'...
fatal: unable to access 'https://github.com/scotch-io/scotch-box-pro/': SSL certificate problem: self signed certificate in certificate chain"

I'll look for a solve on my end to bypass that warning, but is there something the Scotchbox team can help with?

Vagrant up hangs on "Setting up grub-pc"

When I execute the vagrant up command, the process hangs on:

==> default: Generation complete.
==> default: Setting up libpam-systemd:amd64 (229-4ubuntu17) ...
==> default: Setting up udev (229-4ubuntu17) ...
==> default: addgroup:
==> default: The group `input' already exists as a system group. Exiting.
==> default: update-initramfs: deferring update (trigger activated)
==> default: Setting up libfreetype6:amd64 (2.6.1-0.1ubuntu2.3) ...
==> default: Setting up grub-common (2.02~beta2-36ubuntu3.11) ...
==> default: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
==> default: Setting up grub2-common (2.02~beta2-36ubuntu3.11) ...
==> default: Setting up grub-pc-bin (2.02~beta2-36ubuntu3.11) ...
==> default: Setting up grub-pc (2.02~beta2-36ubuntu3.11) ...
==> default:

My Vagrantfile looks like:

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
    config.vm.box = "bento/ubuntu-16.04"
    config.vm.hostname = "TestBox"

    config.vm.network "forwarded_port", guest: 80, host: 8080

    config.vm.network "private_network", ip: "192.168.33.10"

        config.vm.provider "virtualbox" do |v|
             v.memory = 2048
             v.cpus = 2
        end

    config.vm.synced_folder "public", "/var/www", :nfs => { :mount_options => ["dmode=777","fmode=666"] }
    config.ssh.insert_key = false
    config.vm.provision "shell", path: "install.sh", privileged: false
end

Torubles with the Pro

Hi, thank you for your vagrant boxes.
I've used the free version of scotch box for years. I purchased the pro, I'm trying to switch but I'm getting strange bugs during configuring the Pro version.

After the first vagrant up the ssh key doesn't work anymore, I don't know why.

    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

vagrant provision output

Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.

After the first vagrant reboot, I'm getting this, I can't get into the box anymore. I don't change anything regarding the ssh things at all. I've tried to destroy the machine and start again, I'm getting this all the time. This is not happening with the free version on the same PC in the same time, I think this is some kind of bug in PRO version.

Mailhog doesn't work with CLI

Mailhog isn't configured to work with CLI.
Free scotch-box had the same issue (scotch-io/scotch-box#322 (comment)).
It can be annoying as Magento sends transactional emails with CRON/CLI.

Add possibility to fall back to PHP 5.6

Some older websites are not compatible with PHP 7. I would appreciate the possibility of having PHP 5.6 for those.

fmode and the executable bit on shared folder files

In case anyone runs into this, I was unable to change the executable bit on files (e.g. using "chmod 755 filename") in the shared folder. I'm running MacOS Sierra. The solution I used was to change "fmode=666" in the Vagrantfile to "fmode=766" (and then executing "vagrant reload").

Newer Version of PHP?

Are there plans for moving Scotch Box to PHP 7.1 or 7.2? I am starting to find there are things that will not run on 7.0

cp command fails for filesize > 32768 bytes

Hi all,

I recently upgraded to the new PRO box (v1.5) and SSH'd into the machine. Once in, I discovered that I can only copy files smaller than 32768 bytes (obviously an important number!) - anything larger throws a cp: failed to close 'myfilename.md': Input/output error error.

This if a real pain of course since build scripts can't output files and resource managers like yarn can't create node_modules dirs if they contain files larger than this.

I reverted back to the v1.0 box and everything is working fine once again.

Environment Notes:
Host Machine: Windows 10
Vagrant Version: 2.0.1_x86_64
Virtualbox Version: 5.1.30 r118389
Vagrant plugins: winNFSd (with binary installed on Windows)

Also have symlinks active on Host machine to get around "--no-bin-links" with yarn. The combo of winNFSd and symlinks works great and gives no issues at all on the older PRO version.

Anyway, pretty odd issue and just thought I'd put it out there here incase anybody has encountered it before or the specific 32768 filesize rang any bells!

Sequel Pro not working like instructions for Mysql

I can manually get onto SSH with vagrant ssh command line, I can do any command line for MySQL, but when I try the suggested software to manage the database as mentioned on https://box.scotch.io/common-questions/:

WHY NO PHPMYADMIN?

You'll need to download either Sequel Pro or Navicat or some other desktop database client. Switching to one of these from phpMyAdmin will be a life changing experience so just do it already.

No matter what I do I keep getting this message:

The SSH Tunnel has unexpectedly closed.

has any setting need to be done since the last update it use to work with scothbox version 2 but having so many issues with version 3 now.

Composer problem

I'm trying to install Userfrosting using composer but am running into a problem. I get the following message when running "composer install":

[RuntimeException]
Can not clone https://github.com/userfrosting/installers.git to access package information. The "/home/vagrant/.composer/cache/vcs" directory is not writable by the current user.

Current user is "vagrant"

/home/vagrant/.composer/cache/vcs/ is owned by root.

Is it ok to just change the ownership of /home/vagrant/.composer/cache/vcs/ to "vagrant"?

Thanks.

Guest additions outdated, cannot load box

bah wrong box

Drupal 8 issues

CLEAN URLS
Disabled
Your server is capable of using clean URLs, but it is not enabled. Using clean URLs gives an improved user experience and is recommended. Enable clean URLs
PHP OPCODE CACHING
Not enabled
PHP OPcode caching can improve your site's performance considerably. It is highly recommended to have OPcache installed on your server.

404 Error when while resolving dependences on vagrant up

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

apt-get install -y linux-headers-uname -r dkms

Stdout from the command:

Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-3ubuntu3).
The following NEW packages will be installed:
linux-headers-4.13.0-21 linux-headers-4.13.0-21-generic
0 upgraded, 2 newly installed, 0 to remove and 5 not upgraded.
Need to get 11.6 MB of archives.
After this operation, 83.1 MB of additional disk space will be used.
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.161 80]
Ign:1 http://archive.ubuntu.com/ubuntu artful-updates/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
Err:2 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21-generic amd64 4.13.0-21.24
404 Not Found [IP: 91.189.88.161 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main amd64 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.161 80]
Err:1 http://security.ubuntu.com/ubuntu artful-security/main i386 linux-headers-4.13.0-21 all 4.13.0-21.24
404 Not Found [IP: 91.189.88.161 80]

Stderr from the command:

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21_4.13.0-21.24_all.deb 404 Not Found [IP: 91.189.88.161 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-headers-4.13.0-21-generic_4.13.0-21.24_amd64.deb 404 Not Found [IP: 91.189.88.161 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Magento 1 doesn't work

Can't log into the backend of any Magento site. Works in scotchbox not pro, in pro it just says "Invalid Form Key. Please refresh the page." every time you try to log in to the admin backend.

sass --watch not updating when i change my sass Files

Hey guys,

i would like to use sass on my scotchbox pro. The installation has worked fine and i can start the sass watcher by using sass --watch scss:css. But when i make changes in my sass files, the watcher doesn't update the css files in my css directory automaticly. After chaning a sass file i have to start the watcher again.

Has somebody the same issues with scotch-box? I hope somebody can help me.

Thanks!

MailHog incompatibility with Symfony

Symfony uses Swiftmailer, which will try to call /usr/sbin/sendmail by default.

/usr/sbin/sendmail is not symlinked by ScotchBox, but even if you manually add the link it doesn't work. Swiftmail will default the sendmail flag to -bs, which is currently unsupported by mhsendmail. I've opened an issue in the mhsendmail repo, but in the meanwhile this fix worked for me:

$ cat /usr/sbin/sendmail

#!/usr/bin/python

import sys
import subprocess

args = sys.argv[1:]
if '-bs' in args: args.remove('-bs')
cmd = ['/usr/bin/sendmail'] + args;
subprocess.call(cmd)


$ sudo cmhod +x /usr/sbin/sendmail

curl - http2 support is missing

Hi,
I love scotch box pro, using from the very start, thx!

I'm surprised that curl doesn't support http2 requests. How should I enable it?

Peter

Database gone

I created a new instance of Scotch Box Pro about 1 week ago. I then installed WordPress and started working on a website. When I launched the box again tonight, my entire database was gone. I used Sequel Pro to check the database and it was completely empty. Any ideas?

Crashes

I had Scotch Pro running fine for the last couple of days, then suddenly today while working on a design it shut down. When trying to get it back up again, it produces the E_FAIL message at the bottom.

I've tried removing the folder and checking the repo out into another folder and start a new server there but it's not really working.

Vagrant version: 2.0.2
Virtualbox version: 5.2.6

PS D:\users\Nadeko\Documents\GitHub\server> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'scotch/box-pro'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'scotch/box-pro' is up to date...
==> default: Setting the name of the VM: server_default_1518713099502_19141
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: "int __cdecl handleCreate(struct HandlerArg *,int,int *)" at line 66 of file VBoxManageHostonly.cpp
PS D:\users\Nadeko\Documents\GitHub\server>