ideally you should have 2 locations (your choice for them to be
domain-related or "folder" related , i.e. domain.com/domain2.com vs
domain.com/first/ domain.com/second) and have separate wsgiscriptaliase
directives, one pointing to "old" and the other pointing to "new" web2py
folders.
On Thurs
Thanks for your reply.
Actually we want to keep apache+ssl+mod_wsgi+postgres installations as they
are. Keeping them unchanged what should be the right approach to run same
applications side-by-side on both old and new versions of web2py?
Our servers are in amazon cloud.
Thanks & Regards
On
Do you have a limitation, why would you put 2 version of web2py on the same
machine... I would create an other VM with the new stuff!
You could use the same database if you want pointing the postgres of the
old version of web2py...
Richard
On Thu, Feb 7, 2013 at 4:06 AM, at wrote:
> Hi,
>
> C
Hi,
Currenty we are usnig web2py (1.99.7) + apache + ssl + mod_wsgi +
postgresql on ubuntu on production and development servers.
Before we upgrade to latest stable version i.e. 2.3.2 on production, we
want to run both old and latest versions side-by-side on development
servers. What should be
4 matches
Mail list logo