layout | title |
---|---|
page |
Contact/Resume |
This page contains a copy of my resume, my email is readme.py@gmail.com.
layout | title |
---|---|
page |
Contact/Resume |
This page contains a copy of my resume, my email is readme.py@gmail.com.
#!/usr/bin/env python | |
# -*- coding: utf-8 -*- | |
# @Author: tasdik | |
# @Date: 2016-01-26 | |
# @Email: prodicus@outlook.com Github username: @prodicus | |
# @Last Modified by: tasdik | |
# @Last Modified time: 2016-01-30 | |
# MIT License. You can find a copy of the License @ | |
# http://prodicus.mit-license.org |
########## | |
# BASICS # | |
########## | |
To make changes: | |
git add path/to/file1 path/to/file2 | |
git commit -m "templates: Changed the XX template to do XX" | |
To push that to the central server (which makes it available for deployment): |
To detach your current session use C-b d
. You can also use C-b D
to have tmux give you a choice which of your sessions you want to detach.
Figure out which sessions are running by using
$tmux ls
This will give you a list of all running sessions,
To connect to that session you start tmux again but this time tell it which session to attach to:
You started mongodb server, but No matter what. However, when you run sudo status mongodb again, you’ll get mongodb stop/waiting instead of mongodb start/running
Note: This condition is largely due to an unclean shutdown, and results in the creation of a lockfile /var/lib/mongodb/mongod.lock
The fix is a quick two-step process as follows:
Remove the lockfile. Run the repair script. This is accomplished as follows:
#Git cheatsheet
Author: Tasdik Rahman (@tasdikrahman)