Type | How to Use | Size | Comes after of | Following options | Can set css after? |
---|---|---|---|---|---|
xs | .xs() |
0px | Media Feature |
Logical Operator |
✔ |
sm | .sm() |
576px | Media Feature |
Logical Operator |
✔ |
md | .md() |
768px | Media Feature |
Logical Operator |
✔ |
lg | .lg() |
992px | Media Feature |
Logical Operator |
✔ |
xl | .xl() |
1200px | Media Feature |
Logical Operator |
✔ |
#!/usr/bin/php | |
<?PHP | |
// Generates a strong password of N length containing at least one lower case letter, | |
// one uppercase letter, one digit, and one special character. The remaining characters | |
// in the password are chosen at random from those four sets. | |
// | |
// The available characters in each set are user friendly - there are no ambiguous | |
// characters such as i, l, 1, o, 0, etc. This, coupled with the $add_dashes option, | |
// makes it much easier for users to manually type or speak their passwords. | |
// |
import Foundation | |
import CFNetwork | |
public class FTPUpload { | |
fileprivate let ftpBaseUrl: String | |
fileprivate let directoryPath: String | |
fileprivate let username: String | |
fileprivate let password: String |
<?php | |
kirby::$handlers['template'] = function($kirby, $page, $data = array()) { | |
require_once(__DIR__ . DS . 'vendor' . DS . 'autoload.php'); | |
$loader = new Twig_Loader_Filesystem($kirby->roots()->templates()); | |
$twig = new Twig_Environment($loader, array( | |
'cache' => false | |
)); |
# You don't need Fog in Ruby or some other library to upload to S3 -- shell works perfectly fine | |
# This is how I upload my new Sol Trader builds (http://soltrader.net) | |
# Based on a modified script from here: http://tmont.com/blargh/2014/1/uploading-to-s3-in-bash | |
S3KEY="my aws key" | |
S3SECRET="my aws secret" # pass these in | |
function putS3 | |
{ | |
path=$1 |
<?php | |
/** | |
* Draw a rectangle with rounded corners. | |
* @param ressource &$img An image resource | |
* @param int $x1 Upper left x coordinate | |
* @param int $y1 Upper left y coordinate | |
* @param int $x2 Bottom right x coordinate | |
* @param int $y2 Bottom right y coordinate | |
* @param int $r Corners radius | |
* @param int $color A color identifier created with imagecolorallocate() |
User sessions in J2EE and LAMP stacks have traditionally been handled in memory by the application server handling the user request. Because of that, load balancers have been configured to use sticky sessions. By sticky sessions we mean that once the user has visited the site, they will be assigned an app server and will return to that server for subsequent requests. The load balancers typically handle that by referencing the users session cookie.
Elastic cloud environments differ from traditional server configurations in that they have a variable number of servers based on traffic loads whereas traditional configurations had a fixed number of servers. When traffic volumes decline it is necessary to vaporize servers. In doing so, we would lose user sessions (essentially forcing a logout) unless we come up with a new strategy for session management.
After much research, it is clear that the best