Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
| #!/bin/bash | |
| # Function displaying wrong usage information | |
| # Proper usage is: ./dev_start.sh Rails-Project-Folder | |
| usage() | |
| { | |
| cat << EOF | |
| usage: $0 Rails-Project-Folder | |
| EOF | |
| } |
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
| # This file is part of VISVIS. This file may be distributed | |
| # seperately, but under the same license as VISVIS (LGPL). | |
| # | |
| # images2gif is free software: you can redistribute it and/or modify | |
| # it under the terms of the GNU Lesser General Public License as | |
| # published by the Free Software Foundation, either version 3 of | |
| # the License, or (at your option) any later version. | |
| # | |
| # images2gif is distributed in the hope that it will be useful, | |
| # but WITHOUT ANY WARRANTY; without even the implied warranty of |
This is an example command for Backtick. A Backtick command consists of some executable JavaScript and a bit of metadata in JSON.
Here are the required steps to create a command:
Create a new Gist with a command.js and command.json file.
Write your JavaScript in command.js. This will be injected into and executed on the page the user is currently on when they run it.
Add some metadata to the command.json file:
This is an example command for Backtick. A Backtick command consists of some executable JavaScript and a bit of metadata in JSON.
Here are the required steps to create a command:
Create a new Gist with a command.js and command.json file, or simply fork this one.
Write your JavaScript in command.js. This will be injected into and executed on the page the user is currently on when they run it.
Add some metadata to the command.json file:
This is an example command for Backtick. A Backtick command consists of some executable JavaScript and a bit of metadata in JSON.
Here are the required steps to create a command:
Create a new Gist with a command.js and command.json file, or simply fork this one.
Write your JavaScript in command.js. This will be injected into and executed on the page the user is currently on when they run it.
Add some metadata to the command.json file:
This Gist / Backtick command will make the issue queue description sticky when you scroll down the comments of the issue. Read more here: https://association.drupal.org/node/17983
This is a command for Backtick. It allows you to make a web page editable. Once you run the command you can click anywhere on the page and delete elements or type something.
To use this:
7556270.This simple script will take a picture of a whiteboard and use parts of the ImageMagick library with sane defaults to clean it up tremendously.
The script is here:
#!/bin/bash
convert "$1" -morphology Convolve DoG:15,100,0 -negate -normalize -blur 0x1 -channel RBG -level 60%,91%,0.1 "$2"
When debugging Drupal, I often stick dpm($some_array, "my array"); calls to see what the value of $some_array is.
This fails spectacularly if the code I'm debugging is run very late in the request after drupal_get_messages() has already been called. (Eg most hook_preprocess_THEMEHOOK functions).
In that case, I've found it useful to add these helper functions somewhere (any enabled custom module, or even index.php), use them instead of dpm. They'll serialize objects to apache's error_log (wherever that is), which you can track by opening a terminal tab and running:
tail -f /var/log/apache2/error.log | tr '%' "\n"