Development Environment
Serverless Development Environment for Python, Javascript/React and Node Developers (on OSX):
Install Prerequesits Package Manger Homebrew and CLI Tools:
xcode-select --install
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"Install Runtime for Javascript and Python:
brew install node python3Install Python and Javascript packages / Dependencies:
pip3 install virtualenv
npm install -g serverless create-react-appSource: http://sourabhbajaj.com/mac-setup/Python/virtualenv.html
Additional tools to improve the developer experience:
brew cask install google-chrome
brew cask install visual-studio-code
brew cask install iterm2
brew cask install postman
brew install git
git config --global credential.helper osxkeychain
brew install git-secretsSetup a template for git to prevent checking in credentials
Make a directory for the template:
Install the hooks in the template directory:
Tell git to use it:
Install AWS patterns globally to be prevented to be checked in to git:
Check the list of secrets
git secretswill scan for:
It should return something like:
Now every time you run git init or git clone, your hooks will be copied into the .git directory of your freshly created repo. If you don’t want to set the template globally, you can use it as needed with git init --template ’~/.git-template’.
That covers new repo creation, and cloning, but we haven’t addressed the problem of existing repos that weren’t created with the template. Here we have a couple options:
git init is a non-destructive operation, so feel free to run it in existing repos. It’s safe, and will retroactively apply the template you specify.
OR
If you want to go “all in” and ensure that every repo has the proper hooks, here’s a script that will recursively walk a directory, such as ~/Projects and run git secrets --install in all repos.
Setup visual studio code
List all my installed extensions:
Create project and initialise repositories
Code: https://github.com/denseidel/apis-api/commit/ecc27aaf1f7a714938d99f1b5d656a67376c934b
Documentation
Use Gitbooks:
Install gitbook CLI:
Initialize:
Generate output to custom folder
Git Knowledge
Use branches and if needed squash all commits related to a single issue into one commit
Modify the last two commits:
Or if they are the last two:
https://stackoverflow.com/a/24690646/1929968
Use git stash to switch change between branches - https://www.youtube.com/watch?v=KLEDKgMmbBI
Development Pipeline:
Use CircleCI as a SaaS as Pipeline:
Add the git repo to it:


Setup a project as described (e.g. add the folder
.circleciwith theconfig.ymlfile)
Link to config.yml file
for containers
for serverless
Last updated