You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the idea of this but I balked as soon as I saw the giant list of third party services and dependencies that it needed to be set up for a so called "minimal skeleton".
In my mind if the goal is a small, minimal skeleton there should only have to be a web-server,. a database server,, and your done. Please read the rest before you get angry.
I get the value that caching in memcache provides, and I think caching in a lot of cases makes a lot of sense, but since such a cache is not always part of your app (IT can also be part of infrastructure or replaced with other services) , it really it shouldn't be a requirement to use memcache as other technologies exist and not all projects/deployments/clouds are compatible with it, and so that violates the fundamental ideal that this is a minimal skeleton if memcache is a hard dependency.
Thus in my mind for something like this, the need to depend on memcache should be more of an add/on/option and not a hard dependency.
The text was updated successfully, but these errors were encountered:
duaneking
changed the title
Flask-Skeleton is bloated.
Flask-Skeleton Contains MemCache as a dependency.
Oct 19, 2014
I love the idea of this but I balked as soon as I saw the giant list of third party services and dependencies that it needed to be set up for a so called "minimal skeleton".
In my mind if the goal is a small, minimal skeleton there should only have to be a web-server,. a database server,, and your done. Please read the rest before you get angry.
I get the value that caching in memcache provides, and I think caching in a lot of cases makes a lot of sense, but since such a cache is not always part of your app (IT can also be part of infrastructure or replaced with other services) , it really it shouldn't be a requirement to use memcache as other technologies exist and not all projects/deployments/clouds are compatible with it, and so that violates the fundamental ideal that this is a minimal skeleton if memcache is a hard dependency.
Thus in my mind for something like this, the need to depend on memcache should be more of an add/on/option and not a hard dependency.
The text was updated successfully, but these errors were encountered: