start new:
tmux
start new with session name:
tmux new -s myname
| # vim: set expandtab sw=4 tabstop=4: | |
| # *color* 'area' 'fgcolor' 'bgcolor' '[attributes]' | |
| # general | |
| color default 15 235 | |
| color cursor 15 241 | |
| color title-focus 242 221 | |
| color title-blur 242 221 | |
| color delimiter 213 default | |
| color author 156 default |
| " Use the following commands to remove the Chef development kit on macOS. | |
| " To remove installed files: | |
| >$ sudo rm -rf /opt/chefdk | |
| "To remove the system installation entry: | |
| >$ sudo pkgutil --forget com.getchef.pkg.chefdk | |
| " To remove symlinks: | |
| " For chef-client version 12.x, under /usr/local/bin: | |
| >$ sudo find /usr/local/bin -lname '/opt/chefdk/*' -delete |
| #!/bin/bash | |
| # Author: Erik Kristensen | |
| # Email: [email protected] | |
| # License: MIT | |
| # Nagios Usage: check_nrpe!check_docker_container!_container_id_ | |
| # Usage: ./check_docker_container.sh _container_id_ | |
| # | |
| # Depending on your docker configuration, root might be required. If your nrpe user has rights | |
| # to talk to the docker daemon, then root is not required. This is why root privileges are not |
$ yum install gcc make ncurses ncurses-devel
$ yum install ruby ruby-devel lua lua-devel luajit \
luajit-devel ctags git python python-devel \
python3 python3-devel tcl-devel \
perl perl-devel perl-ExtUtils-ParseXS \
perl-ExtUtils-XSpp perl-ExtUtils-CBuilder \
perl-ExtUtils-Embed
$ yum clean all| crack Sublime Text (2 and 3) | |
| 1. Open Sublime in a HEX editor (the executable file) | |
| 2. Find 43 33 33 42 30 32 | |
| 3. Replace in the string 33 42 with 32 42 | |
| 4. Save | |
| 5. Enter the license below: | |
| —–BEGIN LICENSE—– | |
| Patrick Carey |
| # Deploy | |
| require 'mina/bundler' | |
| require 'mina/rails' | |
| require 'mina/git' | |
| require 'mina/rbenv' | |
| set :rails_env, 'production' | |
| set :deploy_to, 'deploy_location_without_current' | |
| set :app_path, 'app_location' | |
| set :user, 'alif' |
On OS/X Sierra, after recently running a brew update I started receiving the error message Sorry, you can't use byebug without Readline when trying to run some rake tasks in my ruby project folder. I observed this in projects and gems that include byebug or pry in their Gemfile or gem.spec. I've found in my googling that many begin encountering this error message after running a brew update but there are other triggering conditions as well.
>> rake aws:show_config
WARN: Unresolved specs during Gem::Specification.reset:
mime-types (>= 0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
Sorry, you can't use byebug without Readline. To solve this, you need to