I have an application that runs on web2py 2.9.11 . I tried downloading the
latest version, packaging the app in the old version and re-uploading it in
the new version, but predictably this did not work. The documentation says
that upgrading should just be a matter of unzipping the new version of
I have upgraded to web2py version 2.13.4 from 2.8.2
When I use the scheduler I get.
OperationalError: table scheduler_task has no column named prevent_drift
Any suggestions?
Thanks
Peter
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/we
I need to upgrade the version of web2py on my live website (hosted by
webfaction) to match the local development version. I want to be
absolutely sure (as I'm not entirely clear) about a few things.
1. if I connect (via putty) to the live site, is there a specific
instruction to stop and res
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
You just have to copy the file in your new application and it should work.
You can also create a new one, but I should have look to detail how to do
it. Ask if you need it.
Richard
On Tue, Mar 13, 2012 at 9:40 AM, Richard Vézina wrote:
> you have to set a parameters.py or parameters_443.py, yo
you have to set a parameters.py or parameters_443.py, you will find it in
your backup in web2py folder.
Richard
On Mon, Mar 12, 2012 at 5:18 PM, horridohobbyist
wrote:
> I followed your instructions, but when I try to access
> admin/default/index, I get the following error message:
>
> "admin di
Follow my solution with the source control to have the easiest process.
On Mon, Mar 12, 2012 at 2:18 PM, horridohobbyist
wrote:
> I followed your instructions, but when I try to access
> admin/default/index, I get the following error message:
>
> "admin disabled because unable to access password
I followed your instructions, but when I try to access admin/default/index,
I get the following error message:
"admin disabled because unable to access password file"
So apparently your instructions are incomplete. All I'm trying to do is
update my production system as easily as possible. I don
Use Fabric for about the samething, but since Horrido not to use version
control I leave thing basic.
Richard
On Mon, Mar 12, 2012 at 1:12 PM, Bruce Wade wrote:
> PS: I have my git set to an account that can't ssh to my server. Therefor
> I have to ssh then switch user to pull/push to my reposi
PS: I have my git set to an account that can't ssh to my server. Therefor I
have to ssh then switch user to pull/push to my repository.
On Mon, Mar 12, 2012 at 10:11 AM, Bruce Wade wrote:
> I do something similar but much much more efficient.
>
> My project is under git version control. When upg
I do something similar but much much more efficient.
My project is under git version control. When upgraded I create a new
branch, unpack the new version of the code, test, if it didn't break
anything I then switch to the old branch and merge the new branch into it.
This prevents you from have to
I am strongly suggest to you to not updating that way. Or if you do so,
backup your web2py folder before.
What I usually do:
download latest source from download page
backup my "staging"/"prod" web2py installation
remove the old installation : cd /home/www-data/ && rm -Rf web2py/
Uncompress the n
I'm currently running Version 1.99.2 on my Ubuntu Linux server. Is there an
easy way to upgrade to the latest version (1.99.7)?
My web2py installation says "Checking for upgrades...", but it never
finishes checking! I presume that if it were to finish checking, there
would be a way to upgrade a
16 matches
Mail list logo
