Update Heroku now provides an elegant solution to this issue : session affinity <https://blog.heroku.com/archives/2015/4/28/introducing_session_affinity>
https://devcenter.heroku.com/articles/session-affinity Basically, it sets a special cookie that tends to distribute users towards the dyno they've previously been served with. I've tested it and it does solve the initial issue : which is allowing a file-based session system (admin & appadmin) in a concurrent server environment. This is also a great performance improvement as you can rely less on Memcache and more on RAM-based caching. The only caveat I've found so far is that when you scale up or down your dyno pool, sessions ends up being redistributed on the fly to even things out between dynos. This shouldn't be an issue if your main application doesn't rely too heavily on the filesystem though. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
