This is a Cheat Sheet for interacting with the Mongo Shell ( mongo on your command line). This is for MongoDB Community Edition.
Mongo Manual can help you with getting started using the Shell.
FAQ for MongoDB Fundamentals and other FAQs can be found in the side-bar after visiting that link.
When working with Git, there are two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the [atlassian.com Git Workflow][article] article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on [setting up GIT Bash autocompletion][git-auto]. This tool will assist you to better visualize the state of a branch in regards to changes and being in sync with the remote repo.
When working with Git, there are two prevailing workflows are [Gitflow][gitflow] and [feature branches][feature]. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the [atlassian.com Git Workflow][article] article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on [setting up GIT Bash autocompletion][git-auto]. This tool will assist you to better visualize the state of a branch in regards to changes and being in sync with the remote repo.
| Network Interface Configurator. | |
| - View network settings of an ethernet adapter: | |
| ifconfig eth0 | |
| - Display details of all interfaces, including disabled interfaces: | |
| ifconfig -a | |
| - Disable eth0 interface: | |
| ifconfig eth0 down |
Displays contents of /proc/net files. It works with the Linux Network Subsystem, it will tell you what the status of ports are ie. open, closed, waiting, masquerade connections. It will also display various other things. It has many different options. Netstat (Network Statistic) command display connection info, routing table information etc. To displays routing table information use option as -r.
Sample output:
Proto Recv-Q Send-Q Local Address Foreign Address (state)
tcp4 0 0 127.0.0.1.62132 127.0.0.1.http ESTABLISHED
| # Terminal Cheat Sheet | |
| pwd # print working directory | |
| ls # list files in directory | |
| cd # change directory | |
| ~ # home directory | |
| .. # up one directory | |
| - # previous working directory | |
| help # get help | |
| -h # get help |
| # ConfigMap to expose configuration related to backend application | |
| apiVersion: v1 | |
| kind: ConfigMap | |
| metadata: | |
| name: backend-conf # name of configMap | |
| data: | |
| server-uri: 34.66.207.42 # enternal ip of backend application 'Service' |
| # Define 'Service' to expose FrontEnd Application | |
| apiVersion: v1 | |
| kind: Service | |
| metadata: | |
| name: to-do-app-frontend | |
| spec: | |
| selector: # pod labels should match these | |
| app: to-do-app | |
| tier: frontend | |
| ports: |
| # Define 'Service' to expose backend application deployment | |
| apiVersion: v1 | |
| kind: Service | |
| metadata: | |
| name: to-do-app-backend | |
| spec: | |
| selector: # backend application pod lables should match these | |
| app: to-do-app | |
| tier: backend | |
| ports: |
| FROM node:7.7-alpine | |
| # install dependencies | |
| ADD package.json /tmp/package.json | |
| RUN cd /tmp && npm install | |
| # Copy dependencies | |
| RUN mkdir -p /opt/to-do-app && cp -a /tmp/node_modules /opt/to-do-app | |
| # Setup workdir |