I have successfully configured Meteor on my Windows machine via vagrant along with running the sample app in the browser by following the tutorial given at https://gist.github.com/ahoereth/2607d2ee99103a0a9bc9.
For the last two hours, I have explored all of the Window's directories in search of the code created by meteor create sampleapp command, but I can't find any clue where the code is. As vagrant claims that code is in the Windows directory not the VM box, can anyone give me a hint where it could be hiding?
The directory that's shared with the Windows host is the /vagrant directory. In the VM, the home directory might be different, and won't be visible from Windows.
However, if you want to run the Meteor app from the shared directory, be prepared for a world of pain whenever you install a package that has a : in its name, as Windows won't support that character in the filename, and you'll get a cryptic error in the VM.
Since packages in Meteor 0.9+ regularly have : in their names, developing Meteor apps in the VM/Windows shared directory is a no-go.
Related
I am trying to develop Laravel app using WSL 2 and Docker. I have followed official Laravel instructions for Windows development (https://laravel.com/docs/9.x/installation#getting-started-on-windows).
in WSL console I run:
curl -s https://laravel.build/example-app | bash
cd example-app
./vendor/bin/sail up
Everything seems to be fine (example-app is running on http://localhost), except I don't know how to do the actual development, i.e. edit the sources to see changes in the app.
I believe I have to somehow 'mount' directory sources from inside WSL/Docker into my Windows file system, but I don't know how.
I don't want to use VSCode (Laravel docs suggest that), I want to use IDE of my choice and access project files in general.
In the end I found out that this problem boils down to accessing WSL file system - Docker/Laravel files are synced automatically from there.
WSL file-system can be accessed through a path that looks something like this:
\\wsl$\Ubuntu\home\your-username\example-app
For some reason this was not visible in the Network section of Windows Explorer. You must type it manually or use the following trick:
Open WSL Linux console and go to the folder with your Laravel app. Then type the following:
explorer.exe .
(notice the dot)
This will open Windows Explorer at your current location and you will be able to copy the path and paste into your IDE.
Trying to use iFuse to access iPhone files on Windows but not getting anyway. Would appreciate if people can share instructions/steps on how to get this to work?
iFuse to access iPhone files on Ubuntu works well; therefore, I am confident the issue is on Windows.
Using https://github.com/hooby3dfx/ifuse/releases/tag/win-dokany-0.1
Unzip test.zip in the above link
make sure iTune is installed
Install the specified Dokan version; doesn't seem to work with the latest Dokan version
Open a command window in Admin mode to run the command (e.g. ifuse tmnt --container bundle ID)
While the command is still running in the Admin window, open another command window to list the mounted directory
I'm trying to test my development environment and keep getting this error while going through the "Building Your First Network". I've installed the prerequisites on a Windows 10 Home edition so I'm using Docker Toolbox. The error is described as follows and happens just after a execute the ./byfn.sh up -l node command:
2019-11-14 17:06:26.982 UTC [msp] loadCertificateAt -> INFO 002 Failed loading ClientOU certificate at [/var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem]: [could not read file /var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem: open /var/hyperledger/orderer/msp/cacerts\ca.example.com-cert.pem: no such file or directory]
As you can see there is a backslash just before the ca.example.com-cer.pem which I think is causing the problem. Anyone have an idea of how I might solve this issue?
Docker Toolbox for windows doesn't provide a great experience for users. It's limited in how it can share windows directories with linux containers running in the linux VM it creates. I believe it can be made to work but you have to use very specific folders in your home directory and you would have to google it to find all the details but it's a lot more of a hassle.
You have other options of course
Upgrade to Windows Pro and use Docker for Windows (which doesn't have the same sharing limitations, but still not a great experience and you can still encounter problems sharing the directories)
Install a hypervisor such as virtualbox and run a linux desktop distribution such as ubuntu or mint and use that instead (which I would recommend and would suggest ubuntu 18.04 mate edition)
Wait until next year when hopefully microsoft will release WSL2 for everyone (including home edition) and then Docker won't need a linux VM running and it should be a much better experience trying to run linux containers on windows.
As mentioned by lindluni here
Backslash problem in Hyperledger 2.0.1 when orderer/peer look for .pem files
the problem arises when one creates crypto artifacts under Windows since "golang filepath.Join uses the current OS's filepath scheme". Hence, under Windows backslash is used in all the generated config.yaml files found in crypto-config/*. One can replace this backslashes before the deployment to fix the issue.
I am taking a course on Udacity that requires me to set up a virtual machine on my system. I have already downloaded and installed Virtual Box and Vagrant. When I try to run the command vagrant up, I get this error:
Could anyone please explain what might be going wrong?
I am working on my office laptop so I cannot change the firewall settings. They are controlled by McAfee. Also, the firewall has been turned off by McAfee to the best of my knowledge. I tried searching a lot but couldn't come up with a solution to this.
Well, I researched more about this and was finally able to find something. This issue comes up when vagrant doesn't have folder permission. Sometimes Cygwin shell in Windows doesn't get permission to write or create a new folder.
I followed their github issue. This is what made it work for me:
Rename C:\HashiCorp\Vagrant\embedded\gnuwin32\bin\bsdtar.exe to
something like bsdtar_backup.exe (or temporarily move it)
In that same directory, create bsdtar.bat with this content:
#ECHO OFF
"%~dp0....\mingw\bin\bsdtar.exe" %*
This will result in Vagrant using the mingw binary, without you having to dive into some code. After these two steps, try adding a box.
I typically use the atom editor for any coding work and have folders on my computer with the code. After doing some updates on my Mac OS computer, some ruby gems stopped worked, rvm no longer responded and homebrew gave me a ton of trouble. I want to prevent this from happening again and figured I'd use Vagrant instead. I like it so far and it works fine, however I want to use my Atom editor nevertheless.
Normally I work on projects using gulp or grunt and they compile the files whenever any changes are made. While I have managed to connect to Vagrant with FileZilla, I have no idea how to connect atom to it. All I need is to edit the files in the Vagrant VM, as I would if they were stored in regular directories on my Mac. Any idea how to solve this?
you can certainly use your current workflow but you do not necessarily need to connect to your vm using Filezilla or another protocol.
The best is to look at Synced Folders and synchronized your project directory. By default vagrant synchronized your current directory (where the Vagrantfile is store) to the /vagrant directory in the vm. so if you can place your project directory within the same folder, they will be automatically synchronized.
If Atom (I am not user of this editor) have a special folder where you store your project files, you can add this folder as synchronized folder. Add the following to your Vagrantfile
config.vm.synced_folder "/Users/fhenri/project/tac.local", "/project"
In my case this synchronized my host (mac os) folder /Users/fhenri/project/tac.local to the vm folder /project so whenever I make a change in this folder, I can see the exact same change from the vm.
If you use ruby and gems, it might be good to install the gem locally (within your project structure that you can share between the host and the guest) so they are automatically reflected in the 2 environments when you make a change.
When you're using gulpor grunt you would launch them from the vm, working on a synchronized folder and all the changes you will make from the mac os host would automatically be picked up on the vm. I remember when working with default Virtual box sharing folder, automatically is not flash light, you should allow a few seconds delay but still it is working.
If performance is becoming an issue, you can look at nfs synchronization type by making the change
config.vm.synced_folder "/Users/fhenri/project/tac.local", "/project", type: "nfs"
It should improve a bit