| Quick tip for handling CSRF Token Expiration - common issue is when you use csrf protection is that if | |
| a form sits there for a while (like a login form, but any the same) the csrf token in the form will | |
| expire & throw a strange error. | |
| Handling it is simple, and is a good lesson for dealing with other types of errors in a custom manner. | |
| In Middleware you will see a file VerifyCsrfToken.php and be tempted to handle things there. DON'T! | |
| Instead, look at your app/Exceptions/Handler.php, at the render($request, Exception $e) function. | |
| All of your exceptions go through here, unless you have excluded them in the $dontReport array at the |
| #!/bin/bash | |
| # | |
| BACKUPDEST="$1" | |
| DOMAIN="$2" | |
| MAXBACKUPS="$3" | |
| if [ -z "$BACKUPDEST" -o -z "$DOMAIN" ]; then | |
| echo "Usage: ./vm-backup <backup-folder> <domain> [max-backups]" | |
| exit 1 |
Ref: https://gist.github.com/vertexclique/9839383
Please use built-in Terminal.app (of Mac OS X) to type and rune the command, do not use another tool (like iTerm2).
Common step after enter run the patch command:
| ---- | |
| TEMPORARY DIRECTORY: This is where plugin / theme authors can store temporary files and directories. When a temporary directory expires, the garbage collector will delete it. | |
| * '''tmp_dir_create'''( $expiration, $primary_file ) | |
| * ==> string $absolute_path | WP_Error $error | |
| * Create a temporary directory specifically for the plugin/theme defined by $primary_file. | |
| * '''tmp_dir_info'''( $absolute_path, $with_listing = false ) | |
| * ==> array $tmp_info | WP_Error $error | |
| * Get info about the temporary directory at $absolute_path. |
| # The server clause sets the main parameters. | |
| server: | |
| # Allow network connections outside of localhost | |
| interface: 0.0.0.0 | |
| # Don't automatically run in the background because I want to be able to kill it without hunting a pid | |
| do-daemonize: no | |
| # TODO: Change this to your network range, like `192.168.0.0/16 allow` | |
| access-control: 10.0.0.0/16 allow | |
| # TODO: Change this to your username, or whatever user you want to run/own the `unbound` process | |
| username: "bryanjswift" |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
Other people's projects:
My projects (tutorials are on my blog at http://maxoffsky.com):
LDAP runs on port 389
LDAPS runs on port 636
Ubuntu Guide: https://help.ubuntu.com/12.04/serverguide/openldap-server.html
Debian Guide: http://wiki.debian.org/LDAP/OpenLDAPSetup
| # to generate your dhparam.pem file, run in the terminal | |
| openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048 |
