Guide to overwrite Gravatar when using an extended user model

[ghost]

added a small section on overriding gravatar when using an extended user model.

[alexweissman]

I'm not sure if this is the appropriate section to include this in - what do you think about putting this in its own recipe and then fleshing it out a little more?

[ghost]

probably not the best section - but it took me a little while to figure out, and will be helpful for anyone searching the docs for "avatar". The best option would be to write a full recipe/sprinkle for avatar integration, but I'm pretty swamped right now. The other problem with avatars is that everyone will have different storage - I use S3, but many folks will want to store locally, and probably some people will want to store in the database -_-. happy for you to not merge it, but i think it should be at least mentioned you need to override the default behaviour if you have a new db field called avatar.

[alexweissman]

everyone will have different storage - I use S3, but many folks will want to store locally, and probably some people will want to store in the database

So, the simple solution to this is to abstract out the persistence layer. Take a look at, for example, how the "remember me" library does this kind of abstraction: https://github.com/gbirke/rememberme/tree/master/src/Storage

Every storage (persistence) driver implements the StorageInterface interface. Classes that need to interact with the storage layer can work with any implementation of StorageInterface, without worrying about the details of how the particular storage driver works.