| ipython notebook --ip=0.0.0.0 --port=8080 --no-browser |
| <form accept-charset="UTF-8" action="/payment" class="cardInfo" method="post"> | |
| <fieldset class="cardInfo__cardDetails"> | |
| <div class="form-row cardInfo__cc-num"> | |
| <label for="cc-num"><abbr title="required">*</abbr><span>Card Number</span></label> | |
| <div class="cc-num__wrap"> | |
| <!-- using type="tel" because type="number" doesn’t pass HTML5 form validation with jQuery.payment formatting --> | |
| <input id="cc-num" type="tel" class="paymentInput cc-num" placeholder="•••• •••• •••• ••••" autocompletetype="cc-number" required="required"> | |
| <span class="card" aria-hidden="true"></span> |
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"
One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.
Most workflows make the following compromises:
Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying