On Thursday, December 29, 2016 at 2:50:19 AM UTC-8, Jorrit wrote:
>
> I was trying to upgrade from 2.9.11 to 2.14.6 . Strangely enough it did
> work when I tried it again today. The first time I kept getting an error
> about sessions and cPickle.
>
> I guess I will have to rigorously test all the
I was trying to upgrade from 2.9.11 to 2.14.6 . Strangely enough it did
work when I tried it again today. The first time I kept getting an error
about sessions and cPickle.
I guess I will have to rigorously test all the in-app JS parts that
interact with the core functionality to see if they st
> Though there is no reason to change the layout or CSS unless you want to.
>> Nothing will break if you keep your old layout. The only things in the
>> front end that could break upon upgrade are those that are coupled to
>> backend framework code (e.g., web2py.js, which depends on the framew
On Wednesday, December 28, 2016 at 11:42:48 AM UTC-8, Anthony wrote:
>
> On Wednesday, December 28, 2016 at 2:31:59 PM UTC-5, Dave S wrote:
>>
>>
>>
>> On Wednesday, December 28, 2016 at 9:42:26 AM UTC-8, Anthony wrote:
>>>
>>> Also, can you expand on "did not work"? What problems do you see?
>>>
On Wednesday, December 28, 2016 at 2:31:59 PM UTC-5, Dave S wrote:
>
>
>
> On Wednesday, December 28, 2016 at 9:42:26 AM UTC-8, Anthony wrote:
>>
>> Also, can you expand on "did not work"? What problems do you see?
>>
>> The main thing you might need to update within the app is web2py.js.
>> Maybe
On Wednesday, December 28, 2016 at 9:42:26 AM UTC-8, Anthony wrote:
>
> Also, can you expand on "did not work"? What problems do you see?
>
> The main thing you might need to update within the app is web2py.js. Maybe
> also web2py_ajax.html, appadmin.py, and appadmin.html.
>
> Anthony
>
There a
Also, can you expand on "did not work"? What problems do you see?
The main thing you might need to update within the app is web2py.js. Maybe
also web2py_ajax.html, appadmin.py, and appadmin.html.
Anthony
On Wednesday, December 28, 2016 at 11:36:55 AM UTC-5, Massimo Di Pierro
wrote:
>
> Can you
Can you define "the latest version".
Can you install in a new folder and then copy the old web2py/applications/
subfolder over the new one?
On Wednesday, 28 December 2016 10:20:22 UTC-6, Jorrit wrote:
>
> I have an application that runs on web2py 2.9.11 . I tried downloading the
> latest versi
I guessed I needed to do a migration, but I did not realise that I could do
it in db.py. It works now thanks Dave and Niphlod.
On Monday, 29 February 2016 20:00:29 UTC, Niphlod wrote:
>
> yep, that's definitely the case. when scheduler gets a new feature, it's
> possible that the underlying tabl
yep, that's definitely the case. when scheduler gets a new feature, it's
possible that the underlying table get changed. as table definitions are
inside scheduler's code, you need to let migrations happen (or even better,
drop the scheduler_* tables on the backend, drop related .table files, and
On Monday, February 29, 2016 at 9:06:03 AM UTC-8, peter wrote:
>
> 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
>
>
I think one of N
2012/3/13 Wikus van de Merwe :
> I assume that you have only one application and you keep it separate from
> web2py:
> $HOME/workspace/my-project/src <-- your application folder
> $HOME/workspace/my-project/web2py <-- web2py folder
>
> To upgrade web2py to a desired version you can run then the f
I assume that you have only one application and you keep it separate from
web2py:
$HOME/workspace/my-project/src <-- your application folder
$HOME/workspace/my-project/web2py <-- web2py folder
To upgrade web2py to a desired version you can run then the following
script. It pulls the changes fr
Well, web2py does provide the ability to upgrade through /admin (unlike
pretty much every other framework). But I would strongly suggest spending
the 10 minutes to learn these three Mercurial commands. It'll make you a
*much* better developer.
hg clone
hg pull
hg update
Upgrading is not hard, we are just trying to save you the pain if something
goes wrong.
The easiest way to upgrade is to download the code, unzip it over your
current production code. However if something breaks there is going to be
no easy way to revert.
I have shown my designer to use git in un
You guys are kidding, right? I have to use source code control or Git or
Fabric (none of which I'm familiar with), just to update my *production*system?
I have to spend time and energy to learn all these tools (which I
no longer need for development)?
In all other respects, web2py is easy...wri
http://newtriks.com/2011/12/01/automated-deployment-using-git/
On Mon, Mar 12, 2012 at 4:17 PM, Bruce Wade wrote:
> If you use GIT you could also automate the entire process. You can write a
> plugin that will cause your production to change branch and pull the new
> code for testing whenever yo
If you use GIT you could also automate the entire process. You can write a
plugin that will cause your production to change branch and pull the new
code for testing whenever you update the target branch on your local host
and push.
OK writing the script is a little more complicated then using web2
I definitely suggest using version control instead. SSH in to your server
and "hg clone" web2py from Google Code. Then whenever you want to do an
update, SSH in to server and "hg pull; hg update". You can "hg update" to
specific changesets (ie, roll back if something broke)(this is not fool
pro
19 matches
Mail list logo
