Turns out you're right. I missed this the first time I read this article:

The HTML page itself isn’t listed in the manifest. Pages that associate with a manifest become part of it.

Yesterday I did a lot of work to clean up the repo. I also simplified the build/dev process; all files are now compiled with cake build and none of the compiled files are tracked. So please update your master before you start new branches.

I have two more things I want to do in this area, one of them addressing this issue:

1. Speed up the compilation to under 3 seconds. (#25)

2. Automate updating the .appcache file with an md5 hash of the current time or something (thus invalidating the cache), with every cake build or change to index.html (matter of fact, that file should also be in HAML, and it should also be compiled with cake build). This way new commits will always invalidate the cache, and development won't be a pain in the ass.

This means commits will always have to include changes to this file, which kind of sucks, but I can't think of a better solution besides removing the appcache entirely, or .gitignoring it and somehow generating it when someone first forks the repo.

Appcache was designed exactly for apps like this, so I'd like to keep it if possible.

How does that sound?

App cache development issues. #37

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions