Check the docs:
-
fastcgi_cache_valid
controls cache time - debugging is/can be done with
add_header X-Cache $upstream_cache_status;
which will add a HIT/BYPASS HTTP header to responses. - The setup of
fastcgi_skipcache
is a job left to the reader, it's working great here but does require a good understanding of your application and/or usage patterns to get it right.
I'll throw mine into the ring.
https://github.com/magnetikonline/dotfiles/blob/master/.gitconfig
I much prefer "git status -sb" for the "git st" alias. Smaller status output FTW! :)
Certainly would look at using Sass and the @extend operator, rather than potentially expensive attribute selectors.
http://sass-lang.com/documentation/file.SASS_REFERENCE.html#extend
@gxorgxo much nicer way IMHO - doesn't mess with the source array - useful for working over nodeLists too (since they won't evaluate false).
@davsket @nikola exactly, that's always been my understanding of single selectors like */h1/p/div/etc. it's only when chained up with parent selectors that the browser needs to start sniffing the DOM tree and flex it's muscles... ;)
@davsket since everything works "right to left" a universal selector is really only going to be slow if it's part of a CSS chain - e.g. "* { my-css-rule: value }" would be much, much worse if I wrote ".my-class * { my-css-rule: value }" - since now EVERY element needs to know if it has ".my-class" anywhere as it's (grand)parent or higher.
This is where CSS parsing is going to really choke, if anywhere.
@elad2412 true, true - http://caniuse.com/css3-boxsizing but for the sake of one line of CSS I personally keep it in to provide some backward compat. support.
Nice summary - note your first CSS snippet should have a "-webkit-box-sizing:" in there too :D
Ahhh @rylnd, CSS3 transition support only kicked in with IE10 - so anything below will ignore the transition directives.
Was about to add extend placeholders - probably worthwhile adding to this tip - as it's probably the closest behaviour to what your mixin will achieve (e.g. the mixin itself does not emit output).
@wifisoftinc suggest you start here: http://git-scm.com/book
This also works perfectly in ST2 - it's the way I roll with my editor, always :D
@dpashkevich I really can't say - since I typically deploy using rsync and some custom PHP scripts to minify CSS/JS and bundle assets (which I hope to clean up and put on GitHub someday....).
@smidwap for the data between your database -> application it can be a huge difference depending on the datatypes/sizes in each row. And this is compounded if the database -> application aren't on the same machine using sockets, and are using TCP/IP for the transit.
Your point on query caching makes this even worse, since your cache sizes are going to full up much quicker, since you run the risk of caching more data than you actually need/use - which could be considered wasteful.
@dpashkevich very simple infact - a quick search turned up this which will give you exactly that http://caiustheory.com/automatically-deploying-website-from-remote-git-repository the magic sauce is in core.worktree and the hooks/post-receive script.
Probably the most valuable difftool switch I have found recently is "-d", which is available in more recent Git builds. Great for diffing many files in a visual diff tool that can handle directories.
As used here with the "da" alias.
https://github.com/magnetikonline/dotfiles/blob/master/.gitconfig
Something like this - you should be running from CLI/Shell anyway and not from a HTTP request - in which case the PHP execution time limit is always hard coded to zero (e.g. - unlimited time)..
Ctrl+; and Alt + F3 were new to me - thanks!
Also, more than likely this will be dropped from PHP 5.5 once it goes final -> https://bugs.php.net/bug.php?id=55497 along with the logo/image GUID's that exist.
@pyrech exactly - that's the comment I wanted to see :)
Or if SASS is more your thing - my notes:
Good tip there - and something I have been doing for years - but good to share it around! :D
Nice work - PHP 5.5 should put most of these password hashing issues to bed with the new in-built password hashing API.
Nice tip - but it's a shame more PHP webapps turn to using absolute require/include calls instead of relative paths - which is rather trivial with __FILE__ and __DIR__ (5.3+) magic constants in PHP.
Using an absolute path skips use of the realpath cache completely so this becomes a non-issue as PHP doesn't need to convert a relative -> absolute path and then cache the result.
Love it - I think there is something big in this to get everyone out of "chained event listener hell" (trademark!).
@shawncplus lol - all good :D thx for the vid, will check it out!
Can you give an example?