sudo pacman -Syu zsh
You do not need to install manjaro-zsh-config
and all the other related packages like zsh-syntax-highlighting
, zsh-history-substring-search
, zsh-autosuggestions
, etc., as we will use Oh My Zsh.
sudo pacman -Syu zsh
You do not need to install manjaro-zsh-config
and all the other related packages like zsh-syntax-highlighting
, zsh-history-substring-search
, zsh-autosuggestions
, etc., as we will use Oh My Zsh.
Starting a personal node project could be easy; starting a team node project could be challenging.
I am a developer currently working in SEEK Australia.
In my experience, common mistakes developer make when starting a projects are:
# Find the latest version on https://github.com/creationix/nvm#install-script | |
$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash | |
# Add in your ~/.zshrc the following: | |
export NVM_DIR=~/.nvm | |
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" | |
$ source ~/.zshrc |
{ | |
"restaurants": [{ | |
"id": 1, | |
"name": "Mission Chinese Food", | |
"neighborhood": "Manhattan", | |
"photograph": "1.jpg", | |
"address": "171 E Broadway, New York, NY 10002", | |
"latlng": { | |
"lat": 40.713829, | |
"lng": -73.989667 |
In your command-line run the following commands:
brew doctor
brew update
/* -------------------------------------------------------------------------- */ | |
// All Bootstrap 4 Sass Mixins [Cheat sheet] | |
// Updated to Bootstrap v4.5.x | |
// @author https://anschaef.de | |
// @see https://github.com/twbs/bootstrap/tree/master/scss/mixins | |
/* -------------------------------------------------------------------------- */ | |
/* | |
// ########################################################################## */ | |
// New cheat sheet for Bootstrap 5: |
This procedure explains how to install MySQL using Homebrew on macOS Sierra 10.12
$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
At this time of writing, Homebrew has MySQL version 5.7.15 as default formulae in its main repository :
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore
is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules
directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
.gitignore
in your home directory and add any filepath patterns you want to ignore.Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignore
for.gitignore
in your home directory, if you prefer.