| # -*- coding: utf-8 -*- | |
| import re | |
| import json | |
| import time | |
| import datetime | |
| import requests | |
| import operator | |
| import concurrent.futures |
| import shutil | |
| import os | |
| import sys | |
| import subprocess | |
| import re | |
| # Settings | |
| root_folder = 'C:/Users/Robert/Videos/YouTube/Playlists/' | |
| destination_regex = re.compile(r'^\[download\] Destination: (.*)$', re.M) |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>JS Bin</title> | |
| </head> | |
| <body> | |
| <p> | |
| Edit the CSS below! Live style preview, without JavaScript! | |
| </p> |
Who needs another blog? How brave are you? Build a real estate website. You've got your auth, CRUD, relationships, image uploading/resizing, geocoding via Google, auto PDF fliers and an iCalendar output of inspection times. It's the sort of thing you can just keep adding to until you've got a fully-fledged real estate CRM. Then sell it and make some bank.
(from http://www.reddit.com/r/PHP/comments/3cnufr/what_is_the_php_equivalent_of_a_todo_app/)
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>Created on JS Bin</title> | |
| </head> | |
| <body> | |
| <div> | |
| This is a sample text. | |
| </div> |
| <% | |
| # RNB, A VIM COLORSCHEME TEMPLATE | |
| # Author: Romain Lafourcade (https://github.com/romainl) | |
| # Canonical URL: https://gist.github.com/romainl/5cd2f4ec222805f49eca | |
| # This template is designed to help vimmers create their own colorschemes | |
| # without much effort. | |
| # | |
| # You will need Ruby to generate your colorscheme but Ruby knowledge is | |
| # not needed at all. |
| javascript:(function(){var newSS, styles='* { background:white ! important; color: black !important; text-decoration: none !important } :link, :link * { color: #0000EE !important } :visited, :visited * { color: #551A8B !important }'; if(document.createStyleSheet) { document.createStyleSheet("javascript:'"+styles+"'"); } else { newSS=document.createElement('link'); newSS.rel='stylesheet'; newSS.href='data:text/css,'+escape(styles); document.getElementsByTagName("head")[0].appendChild(newSS); } })(); |
| 1. make new project | |
| cd www/sites/ && mkdir new-project | |
| 2. add project to homestead config | |
| vi ~/.homestead/Homestead.yaml | |
| 3. add project to hosts file | |
| sudo vi /etc/hosts | |
| 4. fire up homestead, or re-provision if already running | |
| cd www/Homestead && vagrant up | vagrant provision | |
| 5. edit files locally by pointing phpstorm or vim to www/sites/<your-project> | |
| 6. run devtools via ssh |
| So you've cloned somebody's repo from github, but now you want to fork it and contribute back. Never fear! | |
| Technically, when you fork "origin" should be your fork and "upstream" should be the project you forked; however, if you're willing to break this convention then it's easy. | |
| * Off the top of my head * | |
| 1. Fork their repo on Github | |
| 2. In your local, add a new remote to your fork; then fetch it, and push your changes up to it | |
| git remote add my-fork git@github...my-fork.git |
| # https://bosnadev.com/2014/09/12/install-elasticsearch-on-laravel-homestead/ | |
| # https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-repositories.html | |
| # https://www.elastic.co/blog/elasticsearch-unplugged | |
| # Install Java | |
| sudo apt-get install openjdk-7-jre-headless -y | |
| # Download & install the Public Signing Key | |
| wget -qO - https://packages.elastic.co/GPG-KEY-elasticsearch | sudo apt-key add - |
