-
Notifications
You must be signed in to change notification settings - Fork 248
Description
I embed flask-session in an app, and let people configure it as they want so they can benefit from the large backend support of the library.
However, the configuration parameter are numerous, and they require people installing my application to read the documentation of flask-session to do what thy need. This is inconvenient because those people may not be familiar with Flask or Python at all. They are just devops folks installing an application.
I don't know how hard this would be, technically speaking, but I would suggest to be able to configure everything from a single URL shaped configuration parameter, say SESSION_URL. This could have values such as redis://user:password@host:6379/1, memcached://localhost:11211, postgresql://user:password@host/database etc.
This syntax is common on other projects and would probably sound familiar to people installing my application.
Then some magic would detect the session type and initialize what is needed.
I opened the feature request here, but this feature could also live elsewhere, say a flask-session-url library.
What do you think?