The Command Line
The Command Line
for Web Developers
About the Book
This book is for developers and designers alike. Seeing a blank Terminal window waiting for your input can feel overwhelming. Where do you begin? Why should a web developer even need to know about Bash or Unix? Do you have to become an expert in this stuff just to do your job? Chris Williams is here to help.
This book is perfect for those just starting out and for those who want to really understand what’s going on in their computers.
Table of Contents
About this book
- Just enough information
- This book is already out of date
- This book has a Mac bias
- So why the book?
- Who am I?
- 1.1 What is the command line?
- 1.2 Why use the command line?
- 1.3 A brief history of Bash
- 1.4 Today’s development landscape
- 1.5 Using Git for version control
- 1.6 Summary
2. Basic Commands
- 2.1 Moving around
- 2.2 Changing directories
- 2.3 Using shortcuts to execute commands
- 2.4 Using flags on commands
- 2.5 What are hidden files and directories?
- 2.6 Files have permissions
- 2.7 ACL: Access Control List
- 2.8 Moving, copying, and removing files
- 2.9 Move to rename
- 2.10 Copying files with cp
- 2.11 Removing files with rm
- 2.12 You’ve just replaced Finder
3. More Advanced Bash
- 3.1 Finding data with grep
- 3.2 Using pipes to chain commands
- 3.3 Other ways to chain commands
- 3.4 Redirection syntax
- 3.5 Common redirection examples
- 3.6 Shortcuts to accessing desktop applications
- 3.7 Symbolic Links
- 3.8 Application helpers
- 3.9 Aliases
- 3.10 Searching command history
- 3.11 PATH is where commands are located
- 3.12 You’re a wizard, Harry
4. Setting things up
- 4.1 Install Xcode Command Line Tools
- 4.2 Install Ruby for user access
- 4.3 Install Homebrew
- 4.4 Install Node.js
- 4.5 Install Python
- 4.6 What have I done?
- 5.1 What are all these hidden files?
- 5.2 The loading order for dotfiles
- 5.3 Configure your profile
- 5.4 Customize your Prompt
- 5.5 Sharing configurations
- 5.6 Summary
6. Serving Locally
- 6.1 How local servers work
- 6.2 Using Apache as a server
- 6.3 Using Node as a server
- 6.4 Using Python as a server
- 6.5 Summary
7. Getting started with Git
- 7.1 Why everyone loves Git
- 7.2 So how does Git work?
- 7.3 Set up Git
- 7.4 The Basics
- 7.5 Timeline visualized
- 7.6 Moving back in time
- 7.7 Common workflows and best practices
- 7.8 Making great commits
- 7.9 Troubleshooting and Tips
- 7.10 Summary
8. Text Editors
- 8.1 Using popular text editor applications
- 8.2 Using Vim
- 8.3 Summary
- 9.1 How to use npm
- 9.2 Using package.json
- 9.3 Defining run commands
- 9.4 Managing Front-end Packages and Tasks
- 9.5 Summary
- About this book
The Leanpub 60-day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them