This is a set of helpers for finding the application's currently active models/routes/controllers/etc. This isn't a straightforward process because of how Ember (rightly) encapsulates application objects, but it's useful in debugging environments to be able to quickly access them. And with the beta release of Ember Data, the store is not easily accessible without helpers either.
All helpers can be called directly if you provide them an application instance:
elnuevodia.com,primerahora.com###DivSpace
Here at PyData NYC, I heard a tutorial of how to use numpy and iPython notebooks. In a previous gist, I wrote drew all the zip codes of the Bronx in d3.js
This would be great for reproducing inforgraphics like Educational Attainment in New York City -- Brooklyn which looks a bit like a jigsaw puzzle:
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.
| ==== SNIP ==== | |
| class DistanceSerializer(serializers.Serializer): | |
| km = serializers.FloatField() | |
| m = serializers.FloatField() | |
| mi = serializers.FloatField() | |
| ft = serializers.FloatField() | |
| class SearchResultSerializer(serializers.Serializer): |
| App = Ember.Application.create({ | |
| customEvents: { | |
| swipeLeft: 'swipeLeft', | |
| swipeRight: 'swipeRight', | |
| swipeLeftTwoFinger: 'swipeLeftTwoFinger', | |
| swipeRightTwoFinger: 'swipeRightTwoFinger', | |
| dragDown: 'dragDown', | |
| dragUp: 'dragUp', | |
| dragDownTwoFinger: 'dragDownTwoFinger', | |
| dragUpTwoFinger: 'dragUpTwoFinger' |
httpOnly (and secure to true if running over SSL) when setting cookies.csrf for preventing Cross-Site Request Forgery: http://expressjs.com/api.html#csrfbodyParser() and only use multipart explicitly. To avoid multiparts vulnerability to 'temp file' bloat, use the defer property and pipe() the multipart upload stream to the intended destination.
| (function() { | |
| var isNone = Ember.isNone; | |
| DS.SailsWebSocketRESTAdapter = DS.RESTAdapter.extend({ | |
| bulkCommit: false, | |
| serializer: DS.FixedRelationsRESTSerializer, | |
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
| 1033edge.com | |
| 11mail.com | |
| 123.com | |
| 123box.net | |
| 123india.com | |
| 123mail.cl | |
| 123qwe.co.uk | |
| 126.com | |
| 150ml.com | |
| 15meg4free.com |