Hi Manuele,
PythonAnywhere dev here: there's no extra cost if you want to increase the
maximum number of Postgres connections -- just follow the instructions on
this help page: https://help.pythonanywhere.com/pages/PostgresConnections/.
Don't forget to contact us once you've increased the con
2016 at 1:45 PM, Niphlod wrote:
>>
>>> it's perfectly normal as pydal is a subrepo (it's in the readme, too)
>>>
>>>
>>> On Tuesday, November 1, 2016 at 5:43:44 PM UTC+1, Giles Thomas wrote:
>>>>
>>>> Thanks, Richard.
>&
ou have issue with
> it, it means you try to init you git repo over the entire web2py folder?
>
> Why don't you just version control your app? which is what we usually do...
>
> Thanks
>
> Richard
>
> On Tue, Nov 1, 2016 at 10:51 AM, Giles Thomas > wrote:
>
>&
build 2.14.6 I think...
>
> Richard
>
> On Tue, Nov 1, 2016 at 10:42 AM, Giles Thomas > wrote:
>
>> This is in a download from web2py.com -- specifically, the "Source code"
>> download from http://www.web2py.com/init/default/download.
>>
>> Interest
web2py and is a project of
> it own so it is include in the web2py repository as a submodule.
>
> Richard
>
> On Tue, Nov 1, 2016 at 8:50 AM, Giles Thomas > wrote:
>
>> Hi all,
>>
>> Someone pointed out to us that web2py has a .git file in
>> gl
oving it from the source that we install for users on PythonAnywhere,
but wanted to check first to make sure that we're not going to break
anything or cause problems for our users.
All the best,
Giles
--
Giles Thomas
PythonAnywhere: Develop and host Python from your brow
so i think it's not convinience since the user doesn't know either the
> deployed is still in process or finished. to face this, the user who
> deployed to pythonanywhere must open the pythonanywhere admin too, and
> refresh it several times, to check the apps is deployed or not.
>
Sorry, I'm a bit confused -- you seem to be saying in the first sentence
that it is working, then in the second one that it isn't...?
Giles
On Wednesday, April 20, 2016 at 8:53:17 PM UTC+1, 黄祥 wrote:
>
> yes, you all right, it back to normal right now, perhaps about the outage,
> but the same
PythonAnywhere dev here -- we did have a four-minute outage at 04:11 UTC
this morning, perhaps that was it?
On Wednesday, April 20, 2016 at 12:34:23 PM UTC+1, Leonel Câmara wrote:
>
> Weird we didn't do any changes on our side. It was probably a temporary
> error, I just tested deploying an appl
d one thing and
actually did something subtly different.
All the best,
Giles
>
> Clara
>
> El martes, 11 de noviembre de 2014 08:29:08 UTC-3, Giles Thomas escribió:
>>
>> Hi there,
>>
>> PythonAnywhere dev here -- you're right, it's a browser c
Hi there,
PythonAnywhere dev here -- you're right, it's a browser cache thing,
resulting from a bug on our side.
We have a "Strict-Transport-Security" setting on the main PythonAnywhere
site that means that if you ever visit it via https then in future your
browser will always use https to a
he
> Google Groups "web2py-users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/web2py/8toVDprfqwM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> web2py+unsubscr...@googlegroups.com.
> For more opt
Hi all,
Giles from PythonAnywhere here. I've been working with Richard to try to
track this down further. One thing I can confidently say is that it's not
an Apache/mod_wsgi problem in this case, because we use nginx and uWSGI.
I've also double-checked that the `copy_reg` import works from a
On Tuesday, October 29, 2013 1:12:12 PM UTC, stefaan wrote:
>
> It's a manual process to clear down sites from people that decide not to
>> sign up.
>>
>> Ouch... so let's hope not too many people decide to try it out then...
> (oh wait...! :D)
>
It's not that bad, we just need to run a coupl
On Monday, October 28, 2013 7:24:39 PM UTC, stefaan wrote:
> I tried creating something last week as I saw it announced on the dev
> mailing list, and despite not signing up, I now see it still appears to
> be alive. Is this expected?
(PythonAnywhere guy here.)
It's more the case that we don
On Friday, March 22, 2013 4:33:48 AM UTC, Cliff Kachinske wrote:
> The Python anywhere web site was down earlier today.
There was a brief outage at 13:40 UTC on 21 March while we upgraded the
system -- is that the downtime you meant? We're not aware of any other
outages, but if you saw prob
llation -- they're independent sets of server processes,
and clicking the button in our web interface only reloads the one that's
selected on the left-hand side of the web tab.
If that definitely wasn't the cause, I'd love to know which web app it was
and roughly the timing -- the
ywhere.com. Why were sending the traffic, but
> the referer was set to urlOfMyApp.com and http_host was set to
> myaccount.pythonanywhere.com. So, I definitely think it is a DNS host
> problem but they are telling me that what I want to do is not possible,
> with them or an
Hi there,
PythonAnywhere developer here. I assume that the request environment where
Jim S was seeing the incorrect http_host is the underlying WSGI environment
-- is that correct? If so, that's a weird result. We definitely don't do
anything strange and hacky with those headers; I just ran
19 matches
Mail list logo
