{"push_id":1402648186,"size":7,"distinct_size":3,"ref":"refs/heads/0.4.0","head":"10dc383b72716ec6407d355b8f4cd7a7de85d546","before":"7fd2ded36a56cf5c74f48448e43a0c68eade4790","commits":[{"sha":"b2cddb36e86b38e16d06f859407f7d3e2e5f3882","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Fix error caused by 5b7c6c9cf21efd9639b046efc84d7f2820987e4d\n\nMoved the function outside the scope of the class, causing a no method\nerror.","distinct":false,"url":"https://api.github.com/repos/devlocker/breakfast/commits/b2cddb36e86b38e16d06f859407f7d3e2e5f3882"},{"sha":"f07302b7b8e375e10bb07eaeef8ee50feaa30d0c","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Determine if server is running\n\nRelates to https://github.com/devlocker/breakfast/issues/9\n\nIssue:  Running bundle exec puma causes Breakfast to not start\n\nReason: The current check for determining if a server is running\n        (defined? Rails::Server) only works when the server is started\n        through the rails server command. Other forms will be ignored,\n        i.e. Puma, Passenger, etc.\n\nFix:    Rather ugly unfortunately, but there is no unified way of telling\n        if the process is starting in server mode. So for every possible\n        server we will have to check if it is running.","distinct":false,"url":"https://api.github.com/repos/devlocker/breakfast/commits/f07302b7b8e375e10bb07eaeef8ee50feaa30d0c"},{"sha":"ce8be9f8c9e88075700909a87555ceb8a4e496c9","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Merge pull request #10 from devlocker/determine_if_server_running\n\nBetter determine if server running","distinct":false,"url":"https://api.github.com/repos/devlocker/breakfast/commits/ce8be9f8c9e88075700909a87555ceb8a4e496c9"},{"sha":"4d5b848f318471d905fa3c3cae106f0c47700cfe","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Version 0.3.1\n\nAdded:\n\n  * Better support for determining if Server is running. Using puma,\n    passneger, etc. instead of the default rails server command now\n    work.","distinct":false,"url":"https://api.github.com/repos/devlocker/breakfast/commits/4d5b848f318471d905fa3c3cae106f0c47700cfe"},{"sha":"e976a151ce3d4100ef46ddbf7bfad0f7cdc7a955","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Production Manifests\n\nFirst take on manifests. A manifest is a file which has a list of assets\nmapped to fingerprinted versions. For example, when the end user adds an\ninclude tag for app.css, Breakfast will use the manifest to find the\nfingerprinted version (app-some-32-character-hex.css) to serve instead.\n\nThe rationale for doing this in a production environment is that you can\ntake advantage of [HTTP Caching](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching).\n\nIf assets were not fingerprinted, you could not reliably use\nCache-Control headers.\n\n> For example, suppose you've told your visitors to cache a CSS\n> stylesheet for up to 24 hours (max-age=86400), but your designer has\n> just committed an update that you'd like to make available to all\n> users. How do you notify all the visitors who have what is now a\n> \"stale\" cached copy of your CSS to update their caches? You can't, at\n> least not without changing the URL of the resource.\n\nBy implementing fingerprinting you can set Cache Control headers far out\ninto the future without worrying about serving stale assets. If the\ncontent of the file changes, so will the fingerprint. If you re-deploy\nwith the same assets, the MD5 Digest will stay the same, keeping the\ncache intact.\n\nThis commit / PR introduces a Manifest class which is responsible for\nmanaging a manifest, fingerprinting files, and cleaning up any old\nunused files.\n\nHowever, unlike the current asset pipeline behavior, none-digested\nassets are also included in the public/assets directory.\n\nShould the end user not want to generate digested files, set\nconfig.breakfast.digest = false. It currently defaults to false in\ndevelopment / test and true everywhere else.","distinct":true,"url":"https://api.github.com/repos/devlocker/breakfast/commits/e976a151ce3d4100ef46ddbf7bfad0f7cdc7a955"},{"sha":"3271a71b68d8e8b552ec5da79fec9ecf1ed3ff50","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Fix StatusBar CSS bug\n\nIf box-sizing is not set to border box, then the success message does\nnot line up properly. Removed unneeded padding.","distinct":true,"url":"https://api.github.com/repos/devlocker/breakfast/commits/3271a71b68d8e8b552ec5da79fec9ecf1ed3ff50"},{"sha":"10dc383b72716ec6407d355b8f4cd7a7de85d546","author":{"name":"Patrick Koperwas","email":"565ec6518443fd8b377bbc9065386bca948635b3@gmail.com"},"message":"Prepare v0.4.0","distinct":true,"url":"https://api.github.com/repos/devlocker/breakfast/commits/10dc383b72716ec6407d355b8f4cd7a7de85d546"}]}
{"actor":{"display_login":"PatKoperwas"}}