On Friday, June 14, 2019 at 2:57:38 PM UTC-5, Jim Gregory wrote:
>
>
> On the old version of my blog, I would get relative URLs
> '/blog/', but now I'm getting '/blog/default/'.
> SImilar behavior is occurring in the top-level navigation. Has routing
> behavior changed?
>
> I had forgotten
OK, I installed the current version of web2py on my laptop and copied over
the 'init' application and a 'blog' application. I've launched the test
server and opened the blog app in my browser.
The main problem I'm having now is URL rewriting. Here's routes.py in my
blog app:
On Wednesday, June 12, 2019 at 2:43:20 PM UTC-7, Dave S wrote:
>
>
>
> On Wednesday, June 12, 2019 at 1:13:38 PM UTC-7, Jim Gregory wrote:
>>
>> I will be moving a legacy application from my old shared host to a new
>> VPS, and would like to upgrade web2py at the same time from 2.08 to the
>>
the cleanest option is to install the new web2py and then copy or symlink
your application under the applications folder. Check that everything works
well before deploying. I'd b interested to know if anything break. I do not
expect anything to break.
On Wednesday, 12 June 2019 13:13:38 UTC-7,
On Wednesday, June 12, 2019 at 1:13:38 PM UTC-7, Jim Gregory wrote:
>
> I will be moving a legacy application from my old shared host to a new
> VPS, and would like to upgrade web2py at the same time from 2.08 to the
> current version (2.18.5). How should I go about doing this? What changes
>
> I will be moving a legacy application from my old shared host to a new
> VPS, and would like to upgrade web2py at the same time from 2.08 to the
> current version (2.18.5). How should I go about doing this?
>
since you said from shared host to a new host, perhaps can do it manually:
-
6 matches
Mail list logo
