- twig/twig - Twig, the flexible, fast, and secure template language for PHP - 279287
- symfony/symfony - The Symfony PHP framework - 230662
- doctrine/common - Common Library for Doctrine projects - 230352
- doctrine/dbal - Database Abstraction Layer - 217097
- monolog/monolog - Logging for PHP 5.3 - 197983
- doctrine/orm - Object-Relational-Mapper for PHP - 196816
- swiftmailer/swiftmailer - Swiftmailer, free feature-rich PHP mailer - 172086
- kriswallsmith/assetic - Asset Management for PHP - 165852
- [sensio/distribution-bundle](https://packagist.org/packages/sen
rsync (Everyone seems to like -z, but it is much slower for me)
- a: archive mode - rescursive, preserves owner, preserves permissions, preserves modification times, preserves group, copies symlinks as symlinks, preserves device files.
- H: preserves hard-links
- A: preserves ACLs
Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.
If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.
<?php | |
/** | |
* | |
* GF Directory Entry Detail Lockdown | |
* https://gist.github.com/spivurno/5855683 | |
* | |
* GF Directory add-on allows filtering entries on the list view; however, a user can manually | |
* enter in any entry detail URL (i.e. http://site.com/directory-ii/entry/225/3277/) and see | |
* any entry. | |
* |
<?php | |
namespace Acme\Bundle\Command; | |
use Symfony\Bundle\FrameworkBundle\Command\ContainerAwareCommand; | |
use Symfony\Component\Console\Input\InputArgument; | |
use Symfony\Component\Console\Input\InputOption; | |
use Symfony\Component\Console\Input\InputInterface; | |
use Symfony\Component\Console\Output\OutputInterface; | |
use Symfony\Component\HttpFoundation\RedirectResponse; |
Moved to git repository: https://github.com/denji/nginx-tuning
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon
with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
# SYNTAX: | |
var pattern = new RegExp(pattern, attributes); # attributes: g (global); i (case-sensitive); m (multiline matches) | |
var pattern = /pattern/attributes; # same as above | |
# BRACKETS: | |
[...]: Any one character between the brackets. | |
[^...]: Any one character not between the brackets. |
<?php | |
/** | |
* Simple file to help add manual entries to a gravity form, so we don't have to deal w/ GFs output. | |
*/ | |
require_once $_SERVER['DOCUMENT_ROOT'] . '/wp/wp-load.php'; | |
$data = $_REQUEST; | |
// ----------------------------------------------- |