mrkpatchaa

Use case : Imagine we have just created a project with composer create-project awesone-project (currently V0.2). 2 weeks later, there is a new release (V0.3). How to update your project ? Since composer update only updates the project dependencies, it is not what we are looking for. Composer doesn't know about awesome-project since it's not in our composer.json.

After trying many git solutions, I've come to this :

git archive --output=changes.zip HEAD $(git diff --name-only SHA1 SHA2 --diff-filter=ACMRTUXB)

This command will check for changes between the two commits and ignore deleted files.

PatrickLang

Create a resource group

Create a resource group in Azure to hold all of the resources you'll be creating:

• Virtual Network
• Virtual Machines

Create a VNet

• Don't use 172.* IPs. I used 10.3.0.0/24