If you run the terminal in VSCode on Windows, and the command is not recognised, make sure that the Path environment variable includes the following path: C:\Users\user.name\AppData\Roaming\npm. Also, make sure that this entry is at the beginning of the list because your path list can be too big for the VSCode Terminal to handle. This can be determined by typing echo %PATH% in your terminal window, and comparing it with the external cmd.exe window.
By default Docker sets up MobyLinuxVM and downloads and installs docker image on your C:\ drive. For most people this is not ideal, as this is our main application drive and can be limited in space. Especially if you are using Docker on a laptop with a small hard drive. So you will probably want to use an different drive to your C:\ drive.
It is a very straight forward task to perform.
First of all, you need to stop your docker containers using the docker stop [Container Name] command. For a list of all your docker images, run the command: docker images –all.
Then type “Hyper-V Manager in the taskbar search box and run it. Select your PC in the left hand pane. Right-click on the correct virtual machine which by default is called MobyLinuxVM. Select “Turn Off”. Right-click on the Virtual Machine and select “Move”. Follow the on-screen prompts to move your VM.
Now open Docker Settings and select Daemon. Switch from Basic to Advanced. Edit the JSON so that it looks like:
Click on Apply to apply your change. In the JSON above, the graph property is the location where your docker images will be placed by default from now on.
If you are new to Docker and would like to learn more on how to use Docker on Windows then you can buy the book Docker on Windows published by Packt.
Author Elton Stoneman guides you through getting started with docker on Windows, packaging and running applications as docker containers, developing dockerised .NET and .NET Core Applications, pushing and pulling images from docker registries, adopting container-first solution design, organising distributed solutions with Docker Compose, administering and monitoring dockerised solutions, understanding the security risks and benefits of docker, powering a continuous deployment pipeline with docker, debugging and instrumenting application containers, and guidance for implementing docker by containerising what you know.
I have released my first music album on Bandcamp. It is a mixture of music including classical, pop, and techno. You can listen here: https://mebsuta.bandcamp.com/. The individual tracks can be bought as well as the album. My band name is Mebsuta after a star in Gemini, and the album is called Eclectic Moods.
Recently, I have needed to import 3D Blender models into Unity 2017. This proved difficult for me as the assets always seemed pixilated. I found that this was the case when importing .fbx files generated from Blender. But this was not the case when importing .blend files. When importing .blend files, your assets are in the image quality you expect. The only downside is that the materials are plain without the original textures. To solve this, simply import your PNGs and drag them to your material’s Albedo setting. Here are the steps to follow when importing Blender assets into Unity 2017:
- Add a new project in Unity 2017.
- Save the current scene into a folder called Scenes.
- Add a folder called Models under the Assets root folder.
- In the Models folder add a folder for the named asset to be imported.
- Copy the .blend file into the model’s folder.
- Open up the Materials folder for the imported model.
- Copy the PNG files into the Materials folder.
- Click on the material to display its properties in the Inspector.
- Drag the relevant PNG image onto the Albedo square to the left.
- Add the model to the scene, and tweek as necessary.
For anyone who is serious about writing good, clean code that is adaptive this book is a must. Even though the book is written for C# programmers, any programmer who needs to learn agile coding using design patterns and SOLID principles will find this book of great value.
The book is partitioned into three sections. Part 1 provides you with a foundation into agile software project management using Scrum. Then you learn about programming with dependencies and layering, before you move on to reading about interfaces and design patterns. This part finishes with a look at unit testing and refactoring.
In Part 2 you are guided through the process of writing SOLID code. There are eight chapters in all in Part 2. These chapters cover the single responsibility principle, the open/closed principle, the Liskov substitution principle, interface segregation, and dependency injection.
You then move on to Part 3 which guides you through the initial phases of developing an adaptive software product over two sprints. Using a fictitious team and project, chapters 10 , 11, and 12 describe the conversations the team members have and the decisions they must make along the way.
You can find the code samples on GitHub. The code examples reflect a selection of some of the patterns and practices that were covered in Parts 1 and 2. Not everything is covered, but some of the more common implementation questions are answered.
All-in-all a very good book, and one that is easy to read from cover-to-cover.
TeslaThemes provide you with the ability to test their WordPress templates for free, and you don’t need to provide credit card details either. There are over 65 themes for you to experiment with until you find the one that is right for you.
The process is rather easy in order to get up and running. All you have to do is visit the Tesla Test Room insert your email, check your inbox, and then you can log in and test the themes.
You get access to a test WordPress Install with all the themes in it for 7 days. After that the test website and created user will be deleted.