Uploaded image for project: 'GPII - Global Public Inclusive Infrastructure'
  1. GPII - Global Public Inclusive Infrastructure
  2. GPII-2170

Migrate to using vagrant-vmenv as a local dependency...

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Quality Infrastructure
    • Labels:
      None

      Description

      I have been using the global vagrant scripts Alfredo Matas designed. In a PR comment in one of the packages where I used his boilerplate Vagrantfile, Antranig commented:

      Seems problematic to me. We should just install the module locally as a result of npm install - as well as avoiding the failure due to faulty use of "require" this will also remove the requirement for the funny message. This approach may well of course lead to problems if the "node_modules" directory ends up being aliased inside and outside the VM. One solution to this may be to perform the activity inside a "monorepo" style nested project which simply holds the vagrant-vmenv dependency itself. Either way, this dependency needs to be installed locally, not globally.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              amatas Alfredo Matas
              Reporter:
              the-t-in-rtf Tony Atkins
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: