First, you have to run Powershell as administrator. Then type the following:
Set-ExecutionPolicy UnrestrictedAccept to continue.
Then we install Chocolatey:
| <template> | |
| <v-container id="signinup-form" class="fill-height"> | |
| <Notification | |
| :message="snackbarMessage" | |
| :snackbar="snackbar" | |
| :type="snackbarType" | |
| /> | |
| <v-row align="center" justify="center" no-gutters> | |
| <v-col cols="12" sm="8" md="8" class=""> | |
| <v-card class="evelation-12 card"> |
| # SQL Server - do this early to avoid issues with newer versions of VC++ 2015 redist | |
| choco install sql-server-2017 | |
| choco install sql-server-2017-cumulative-update | |
| choco install sql-server-management-studio | |
| # tools | |
| choco install git | |
| choco install nodejs | |
| choco install tortoisegit | |
| choco install vscode |
| ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/id_rsa | |
| ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/github_rsa | |
| ssh-keygen -t rsa -b 4096 -N '' -C "rthijssen@gmail.com" -f ~/.ssh/mozilla_rsa |
npm install --save-dev svg-sprite-loader svgo-loader| ################# | |
| # Initial Setup # | |
| ################# | |
| #The command to run, built from the raw link of this gist | |
| #START http://boxstarter.org/package/nr/url?https://gist.githubusercontent.com/dewdad/56f9818c123ad984afbcfba90eb18359/raw/1d094bd48f488085807babd71456db9794e64ea9/RegUserBoxstarter.ps1 | |
| #As described here: http://boxstarter.org/Learn/WebLauncher | |
| ######################################### |
I made a list of 20 things I might want out of a monorepo tool for a Design System to use as a basis for comparing some of the options including Lerna, Northbrook, and Rush.
| How I migrated from multi-repository to mono-repository in one day | |
| We had a lot of repositories for different services. There are 20K+ commits in 15+ repositories. Each repository has its own Dockerfile, tests, lint rules, etc. | |
| Turns out, it’s hard to maintain, especially when you have dependent repositories across. I.e. you have repository api that is using a package from another repository, let’s say commons. If you publish an update in commons, you need to go through all the dependent repositories and update commons there. | |
| Now, just imagine how long it takes, to make a clone of each repository, make an update there and push changes back to remote. It’s hard to say for me, but these kinds of updates were leading to half a day work just for updating the changes in other repositories. Therefore, we allocated resources for changing that. | |
| But, before I started migration to a mono repository, I spent some time investigating the pros and cons of other alternatives. | |
| /** | |
| * Waits for an element satisfying selector to exist, then resolves promise with the element. | |
| * Useful for resolving race conditions. | |
| * | |
| * @param selector | |
| * @returns {Promise} | |
| */ | |
| export function elementReady(selector) { | |
| return new Promise((resolve, reject) => { | |
| let el = document.querySelector(selector); |
| import System; | |
| import System.Windows.Forms; | |
| import Fiddler; | |
| // INTRODUCTION | |
| // | |
| // Well, hello there! | |
| // | |
| // Don't be scared! :-) | |
| // |