The next instruction is actually getting Vagrant to work. And at a first pass the instructions are intimidating and look a lot like Greek to me.
So, deep breathe. Read all the instructions and take it one step at a time.
First command runs, no problem. Breathe a sigh of relief.
Second command – error can’t find the directory. Okay, let’s open up file explorer and see if its there. Found it. But I don’t think that it should actually live in System32. I think that’s going to cause me issues down the line.
Let’s go back three steps.
Run cd.. on Command Prompt. Thanks Dad. I remember you teaching me this before I went into standard 4. Go into my documents path. Now, let’s step forward to the first command again. Actually, before I do that let’s create a folder named PHPNinja. It will be neater that way. Try and switch to it in the cmd prompt. Get an error. Run dir *.* see that I actually named the folder PHPNovice (internal facepalm). Rename the directory. Re-run the change directory command. It works. Small sigh of triumph.
Now, I can really, run that first command again. Run through previous commands using arrows (such a cool trick). Success, again. Will I be able to get past the second step? Let’s see.
Yes success. In the my_project folder. Step 2b. Run mkdir -p Project/public. Get an error. “The syntax of the command is incorrect.” Ok let’s go two steps back again. Run the command exactly as it is in the instructions. Get an error “The system cannot find the path specified.” Let’s run dir *.* to see if my_project is there. The folder is there. Hmm?
Trying the first command again, appending number 2 to my_project. Let’s see if I can make it work.
No dice. I am relatively confident that I have followed the instructions precisely. Let’s switch over to the blog post referenced for more instructions. Same instructions. Same result. Okay, close cmd. Open Git Bash. Success.
Only problem is I am not entirely sure of where the files are now. That’s a problem for later. Let’s see if I can run the final command in the sequence. Success!
Now, background things have been done. Step 4 is to bring up the box. I enter the command and I press enter. And I wait. My cursor flickers. I wonder if anything is happening. After about 10 seconds (I am using an old machine) the command box begins to populate. I think it is now done. What’s the next instruction? I pause, and actually read the command box. It’s busy downloading. So, time to wait. … and wait … and wait some more… 20 minutes and counting (but for more than just the download).
So after lots of waiting, there’s a new error message: default: chown: cannot access ‘/home/vagrant/.composer/’: No such file or directory
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
A quick Google search shows that the issue should be resolved. I try my luck and re-run vagrant up. It seems to be running. Oops, false alarm. I call in technical support (aka Riaan) after running a vagrant status check. He recommends that I enable the Windows Linux Subsystem. We do that.
But I need to take a break and go and do grocery shopping.
I’m not going to lie. This is frustrating. But I am very grateful for my perspective and background. When this is happening and I have followed all of the instructions, I am not taking it personally or as an indictment of my capacity. And I know that the slowest thing about getting started with any coding project is setting up the environment.
To be continued…