Setup environment

Introduction

Environment setup is something that if you don't do right the first time around it will come back to haunt you because you will spend a lot of time fighting with your tools instead of your tools helping you. Also, installing tools with sudo can result in you having to use that tool with sudo for every command. When downloading things like node modules off the internet this could be a very bad idea. So don't use sudo unless it is specifically listed.

How to use

If you are wondering how to use this guide. You need to know that all of our documentation is stored in the instructions directory. From there you should pick your os and follow the setup instructions. Once the setup instructions are complete you should be able to then find additional tools useful for certain kinds of development. See the kinds-of-development section.

Assumed File Structure

Create these directories before / as you get started.

• mkdir ~/repos (git clone here)
• mkdir ~/lando (lando repos here)
• mkdir ~/patches (contrib patches here)
• mkdir ~/sql (.sql files here - exclude from backups)
• mkdir ~/vms (Vangrantfiles here)

Setting up this repository

• This repository is meant to be used as a backup and quick transfer of my local environment setup. If you wish to use my shell configuration you can follow the steps below.
• mkdir ~/repos
• cd ~/repos
• git clone [email protected]:ccjjmartin/setup.environment.git
• NOTE: If you see "Permission Denied (publickey)" this means that you need to setup your publickey on GitHub or use the https version of the url.
• mkdir ~/repos/setup.environment/SAVE_ME_DONT_DELETE/
• touch ~/repos/setup.environment/SAVE_ME_DONT_DELETE/.gitconfig
• git config --global core.editor "nano"
• git config --global user.name "John Doe"
• git config --global user.email [email protected]
• Run scripts/setup-symlinks.sh to setup home_directory files