⌘T | go to file |
⌘⌃P | go to project |
⌘R | go to methods |
⌃G | go to line |
⌘KB | toggle side bar |
⌘⇧P | command prompt |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/usr/bin/env ruby | |
# 1. export your RIL bookmarks | |
# 2. save this file to the same directory where your ril_export.html is | |
# 3. change username and password in the script bellow | |
# 4. run 'ruby ril_to_instapaper.rb' in terminal | |
require "cgi" | |
require "net/http" | |
require "net/https" |
This gist assumes:
- you have a local git repo
- with an online remote repository (github / bitbucket etc)
- and a cloud server (Rackspace cloud / Amazon EC2 etc)
- your (PHP) scripts are served from /var/www/html/
- your webpages are executed by apache
- apache's home directory is /var/www/
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WordPress is actually one of the most secure pieces of software available. It powers 17% | |
of the 1,000,000 most visited websites, so it is being constantly tested both internally | |
and by hackers. When an issue is discovered, an update is released which you can install | |
with one click in the dashboard. | |
The vast majority of hacked WordPress websites are running an out-of-date version of | |
WordPress. Once WordPress is updated, any vulnerabilities that are patched are now publicly | |
known, so old versions are vulnerable. | |
The next most likely source of hacking is your host. If your server isn't secure, it doesn't |