Skip to content

Vagrant-related configuration is outdated #333

@crwood

Description

@crwood

Gridsync's Vagrant-related configuration has become stale in various ways:

  • Due to Vagrant's added support for "multi-machine" configurations, the old vagrantfiles directory is no longer necessary and can be deleted in favor of using the single Vagrantfile already found at the top-level of the project
  • The top-level Vagrantfile contains configuration to spin up environments that are no longer supported (e.g., macOS 10.13)
  • The top-level Vagrantfile lacks configuration for newer environments that should be supported (e.g., Ubuntu 20.10)
  • Some versions of Vagrant/VirtualBox will throw an VERR_CFGM_VALUE_NOT_FOUND error when attempting to spin up multiple environments from the configuration file due to what appears to be improper nesting within the top-level Vagrantfile.

Because Vagrant/VirtualBox is used for smoke testing Gridsync binaries across different platforms, the above issues should be resolved before the next release.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions