teracy-dev’s documentation

Contents:

• Introduction
  • About Teracy
  • Join And Work With Us?
  • What Will You Get After The Training Program?
  • Why teracy name?
• Getting Started
  • Automatic Installation on macOS
  • Manual Installation on macOS
  • Automatic Installation on Linux (Ubuntu)
  • Manual Installation on Linux (Ubuntu)
  • Automatic Installation on Windows
  • Manual Installation on Windows
  • teracy-dev Git Clone and Vagrant Up
  • Git Setup
• Basic Usage
  • Vagrant
  • IP Address
  • File Sync
  • References
• Advanced Usage
  • Configuration
  • Upgrading
• Best Practices
  • New User On-boarding Flow
  • Upgrading User Flow
• Extending teracy-dev
  • Installing ChefDK
  • Creating new Chef cookbooks
  • Installing kubectl and gcloud
  • Summary
  • References
• Docker
  • docker-machine
  • Debugging
  • Related Resources
• Toolchain
  • Git
  • Vim
  • Sublime Text
  • Jira Client
• Built-in IDE (codebox)
• Style Standards
  • Common Standards
  • Document Standards
  • C/C++ Coding Standards
  • Python Coding Standards
  • Java Coding Standards
  • JavaScript Coding Standards
  • HTML, CSS Coding Standards
  • Ruby Coding Standards
  • PHP Coding Standards
  • Objective C Coding Standards
  • XML Coding Standards
• Workflow
  • Initializing Working Repositories
  • Git Branching Off
  • Working with Git
  • References
• teracy-dev Development
  • Project Setup
  • CI Setup
  • Rake Tasks
  • Build teracy/dev Docker image
  • Base Boxes
  • References
• Git Training
  • Studying
  • Practising
• Most Used Git Commands
  • Fork
  • Clone
  • Remote
  • Branch
  • Fetch
  • Status
  • Diff
  • Commit
  • Log
  • Push
  • Rebase
  • Merge
  • Pull request
  • Reset
  • Stash
  • Squash
  • Learn More
• Firefox Add-ons Development Guide
• Document Guide
  • Style Guide
  • reStructuredText Writing
  • Markdown Writing
  • References
• Databases Guide
• Node.js Development Guide
  • Enable proxy and add aliases domains
  • Init the project
  • Install dependencies
  • Add app.js and update package.json’s scripts
  • Create dev mode
  • Run on dev mode
  • Two-way sync for node_modules
  • Remote debugging
  • Create Prod mode
  • Run on prod mode
  • Create review mode
  • Run on review mode
  • Create CI/CD system
  • Summary
• C/C++ Training
• Python Development Guide
• Django Training
• Ruby Development Guide
• PHP Development Guide
• HTML/CSS Training
• JavaScript Training
• Java Training
• Objective C Training
• iOS Training
• Android Training
• Semantic Versioning
  • Base
  • Python
  • Java
  • Ruby
  • PHP
• Release Process
  • Starting
  • Releasing
  • Ending
• FAQs
  • Why teracy-dev? Why not just Docker?
  • How do I know which version of teracy-dev that I’m using?
  • After vaggrant ssh, why cannot I run the grunt or npm command in the VM?
  • What should I do after updating vagrant_config_override.json to get it applied to the VM?
  • What should I do when $ vagrant up gets stuck at this step?
  • /etc/hosts is not properly updated when I got errors, after $ vagrant destroy and $ vagrant up. I end up having multiple same entries that the wrong one is on the top of the file. This leads to wrong DNS to point to the right VM’s IP address. What should I do?
  • What should I do when the teracy-dev version is changed?
  • What should I do when changing provisioner (Chef, Bash…)?
  • What should I do when meeting other errors, and the problems cannot be solved with vagrant reload or vagrant reload --provision?

Indices and tables

• Index
• Search Page