Skip to content

Latest commit

 

History

History
309 lines (211 loc) · 7.64 KB

dev-team.md

File metadata and controls

309 lines (211 loc) · 7.64 KB

Dev Team setup

Standard Mac setup for developers at Studio 24.

Command Line Tools

You may need to re-install these when upgrading to a new OS version (you need to run this after upgrading to macOS Ventura). Toggle privileges (so you have admin rights) and run the following in terminal:

xcode-select --install

Homebrew

Install Homebrew

Make sure you run the commands to add Homebrew to your path (the install command tells you what this is).

Verify it works.

brew doctor

If there are any recommendations, it's worth following them.

Update to latest version

brew update
brew upgrade
brew cleanup

PHP

Note to Alan - do we need to install PHP? I don't believe it comes as standard. If so here's some sample instructions that need testing on a fresh machine...

Install the latest stable version of PHP:

brew install php
brew install composer
brew install symfony-cli/tap/symfony-cli

Laravel installer:

composer global require laravel/installer

This installs the following CLI commands:

Software packages

Install following software via Homebrew. Please install packages from Homebrew one-by-one, since they may include setup instructions (e.g. for NVM):

brew install --cask phpstorm
brew install --cask github
brew install --cask imageoptim
brew install wget
brew install node
brew install nvm
brew install python
brew install pyenv
brew install awscli
brew install nano
brew install goaccess
brew install tableplus
brew install 1password-cli

This installs the following CLI commands:

  • aws - AWS CLI
  • nano - Simple text editor
  • npm - Node Package Manager
  • nvm - Node Version Manager
  • op - 1Password CLI
  • python3 and pip3 for Python 3
  • wget - tool to download files
  • goaccess - tool to analyse access logs. View the website for usage instructions
  • op - to use 1Password via the cli (for SSH etc)

iTerm

iTerm is a better terminal for the Mac.

brew install --cask iterm2

Git

Set default branch to main:

git config --global init.defaultBranch main

User setup:

git config --global user.name "Your Name"
git config --global user.email [email protected]
git config --global pull.ff only

Create a secure SSH key with a password. Store your SSH key password in your personal private vault in 1Password.

See instructions on Generating a new SSH key and adding it to the ssh-agent.

  • Copy keys to GitHub
  • Set the key title to your computer name (so you remember where this came from)
  • To copy your SSH public key to the clipboard:
pbcopy < ~/.ssh/id_ed25519.pub
  • Test access to GitHub:
ssh -T [email protected]

If this doesn't work, add the following to ~/.ssh/config:

Host github.com
 Hostname ssh.github.com
 Port 443

Default merge strategy

The default merge strategy is fast-forward, if this doesn't work you can create a merge commit:

git pull --no-ff

Or rebase your changes

git pull --rebase

Studio 24 team

In order to access private repos and push code to any repos you need to be a member of the Studio 24 team. Request this from the Support Team.

Global Git ignore file

We use a global gitignore file to ignore IDE and OS files we don't want to commit to git. Any project files you want to exclude from git must be added to the project .gitignore file.

Download the global .gitignore file via:

curl https://raw.githubusercontent.com/studio24/mac-setup/main/global-gitignore/.gitignore > ~/.gitignore

And tell Git to use it via:

git config --global core.excludesfile ~/.gitignore

Oh My Zsh

We use Oh My Zsh to customise your terminal, install via:

sh -c "$(curl -fsSL https://raw.github.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

We use two plugins:

Install these via:

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

Edit your ~/.zshrc file:

nano ~/.zshrc

Add the plugins to the list of plugins for Oh My Zsh to load:

plugins=( 
    # other plugins...
    zsh-syntax-highlighting zsh-autosuggestions
)

Close and re-open iTerm to enable the new plugins.

Theme

You can also use different themes if you wish. The team prefer the agnoster theme, which you need to install a Powerline font to use. You can do this via:

git clone --depth 1 [email protected]:powerline/fonts.git ~/fonts
cd ~/fonts
./install.sh
cd ../
rm -Rf fonts

Update your ~/.zshrc file:

ZSH_THEME="agnoster"

You then need to select a Powerline font in iTerm (Preferences > Profile > Text). Noto Mono for Powerline is recommended.

PHPStorm

When you setup PHPStorm install the following plugins (Settings > Plugins):

  • .env files support
  • Laravel Idea (we have commercial license for this)
  • Symfony Support

Login to your JetBrains account to activate commercial plugins.

Optional software

Optional, install these if you want to use them:

brew install --cask rapidapi
brew install --cask textmate
brew install --cask cyberduck
brew install --cask visual-studio-code
brew install --cask transmit
brew install --cask sublime-text

Textmate installs the following CLI commands:

  • mate - CLI command to open text files in Textmate

If you have a license (front-end team):

brew install --cask sketch

SSH

Whenever you need to connect to a remote server please make sure you are on the VPN.

SSH keys for deployment

Developers need to add your SSH key to Studio 24 dev SSH keys repo. This will give you permission to deploy websites. Please note these SSH keys are updated every half an hour on servers.

Important note: always use SSH (secure shell) when cloning a git repo, not HTTPS.

SSH aliases

We use a shared ssh-config file to help accessing remote servers.

Install this via:

git clone [email protected]:studio24/ssh-config.git ~/.ssh/ssh-config

Create a ~/.ssh/config file and add the following to it:

Host *
	UseKeychain yes
	IdentityFile ~/.ssh/id_rsa

Include ssh-config/*.conf

If your ssh key is not called id_rsa, use the correct name instead.

You can test this by outputting all host shortcuts:

~/.ssh/ssh-config/bin/show_hosts

Local development environment

To install a local development environment, see the Local development environment document.

Configure 1Password for SSH access

To setup and use 1Password for SSH access to servers, see the 1Password for SSH document. 3