Default settings try to use /usr/var as the cache path about grip

[joeyespo]

I'm seeing the same thing when running on Ubuntu. My not-so-good workaround is to use sudo grip. But yeah, this should absolutely not be a requirement in running Grip.

This bug is the consequence of using Flask's Instance folder. Rethinking it, while runtime data storage is perfect in normal web application instance folders, it makes less sense when using Flask in a CLI application. Especially since it can be installed in a location with fewer privileges like this.

I don't think /tmp is appropriate because it's intended to persist between runs. It is a cache, but it's also a place to dump local style overrides. So it seems like it falls under the "application data" category, ~/.grip.

I'm not an expert in this area though. Can anyone chime in on where this should actually go?

Thanks for bringing this up, @borntyping.

[borntyping]

If there's doubt about where grip should store data, I'd go with ~/.grip, especially since that's the expected behaviour for a lot of applications and tools, and is very unlikely to conflict with permissions and system folders.

[akhikhl]

Workaround for "Permission denied: '/usr/var'" that worked for me:

sudo mkdir /usr/var
sudo chown user:group /usr/var

then grip starts without errors.

[jdevera]

Hit by this today. Unfortunately @swsnider's patch does not fully work, as os.abspath does not exist. I used os.path.expanduser('~/.cache/grip') instead.

This should be a sane default, and then perhaps if somebody wants to use local style overrides, maybe there could be an option for it.

[jdevera]

PR sent :)