Commit graph

5 commits

Author SHA1 Message Date
James Mason
6d31dfeef4 Add frozen_string_literal magic comment
re: https://www.rubydoc.info/gems/rubocop/RuboCop/Cop/Style/FrozenStringLiteralComment
2018-05-09 06:54:26 -07:00
AEtherC0r3
bf7e890739 Update vagrant box image to openSUSE 42.2
And fix dependencies
2017-06-23 11:00:44 +03:00
Rob Smith
6f260d14fa Fix shared directory mounting on provisioning
Due to how the opensuse/openSUSE-42.1-x86_64 box is, there is no vagrant group
by default. When the shared folder is attemtped to mount, it fails with the
following

```
==> default: Mounting shared folders...
    default: /vagrant => /Users/kormoc/Projects/osem
Vagrant was unable to mount VirtualBox shared folders. This is usually
because the filesystem "vboxsf" is not available. This filesystem is
made available via the VirtualBox Guest Additions and kernel module.
Please verify that these guest additions are properly installed in the
guest. This is not a bug in Vagrant and is usually caused by a faulty
Vagrant box. For context, the command attemped was:

set -e
mount -t vboxsf -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant /vagrant
mount -t vboxsf -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant

The error output from the command was:

No such file or directory
```

This change will fix this issue to allow a single `vagrant up` to work correctly

To test this, you can run `vagrant destroy;vagrant up`. This will destroy your current environment and rebuild it from scratch.
2016-09-17 19:31:59 -07:00
Carlos Coelho
99ce0411bc Updated vagrant box to official Leap release
related to openSUSE/osem#824

Signed-off-by: Carlos Coelho <carlos@pencillabs.com>
2016-03-04 13:14:29 -03:00
Christian Bruckmayer
f3549a21d9 Setup vagrant file for development 2015-12-07 15:06:04 +01:00