GitHub User: henkm
thanks, helped me a lot. +1
I'd like to see that tutorial too.
I've been trying out turbolinks and pjax several times and almost every time I disabled it after a while. It does feel faster and in fact is faster, but you'll have to come up with work arounds for some small problems every time. And you'll have this constant worry: will this still work for my IE8 users? Frankly, this approach just feels a bit icky to me, mostly because I feel less in control of what is going on.
Wow, this is great. I usually use apache+passenger and a MySQL database. Tried to read up on the differences and benchmarks, but it's still not clear to me: is it just a matter of personal preference or is this setup (postgres, nginx, unicorn) really faster/better?
Great cast. Think I like this solution better than thinking sphinx. Is it also better?
Also: writing your own controller action for generating the manifest file, makes it possible to generate a list of all the possible html-files the user may wish to see offline:
I'm happy with this solution. But I guess it won't be possible doing this if each user has a pretty big collection of records and files.
Thanks for the write up. I find that the rack-offline gem is good, but doesn't really fit my needs. I want the complete app to be available offline for a certain user (including all the users assets - thumbnails - saved with paperclip).
I've created a CacheManifest controller and model which loads a manifest with CacheManifestItems (another model) for each logged in user. If the user changes one of its files, the manifest get's updated the next time the user loads a page.
This works great: the entire app is available offline.
I've tried to use this technique to also add new items, if they don't exist yet. Ryan Bates came up with a great idea and I used it like this:
Great tutorial (as always) and great plugin.