it works, but super slow. problem is that we need to wait until Christophe came back from holidays (next week) until we can do something, because looks like the problem is not in the app but in the server (at least, for what I have managed to see). Esteban On 05 Aug 2014, at 14:52, Norbert Hartl <norbert@hartl.name> wrote:
Are you working on it?
Norbert
And Christophe is the only one that can do anything? That's such a bottle neck then we should have a little more resources for that. Norbert Am 05.08.2014 um 15:12 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
it works, but super slow. problem is that we need to wait until Christophe came back from holidays (next week) until we can do something, because looks like the problem is not in the app but in the server (at least, for what I have managed to see).
Esteban
On 05 Aug 2014, at 14:52, Norbert Hartl <norbert@hartl.name> wrote:
Are you working on it?
Norbert
problems always arise when we cannot do much for solving them quickly (is murphy's law)⦠usually we would have: Nico, Christophe and me. But Nico is no longer working here (and also is on holidays), Christophe is in holidays and I already did as much as I can. Now, the other problem is *if* is an infrastructure problem: smalltalkhub runs in INRIA servers, and thatâs usually a good thing, but there is bureaucracy to accomplish before being able to kill a process⦠and I would like to restart apache. I *feel* that it can be a problem there because when I enter config seaside app, sometimes it fails to serve: http://smalltalkhub.com/files/WADevelopmentFiles/development.css with a 503 error (Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable)) and of course, that file is served directly by apache, without going to the pharo image. So⦠I cannot restart the apache until I find one of the guys in the IT office (and most of them are also on holidays) and convince them to give me root rights. Obviously, I think it will be faster to wait for Christophe, because he already has the proper rights. But in any case, actual problem is not because Iâm lazy to try to solve it⦠is because I tried everything I can and now Iâm more or less as screw as you :) Esteban On 05 Aug 2014, at 17:03, Norbert Hartl <norbert@hartl.name> wrote:
And Christophe is the only one that can do anything?
That's such a bottle neck then we should have a little more resources for that.
Norbert
Am 05.08.2014 um 15:12 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
it works, but super slow. problem is that we need to wait until Christophe came back from holidays (next week) until we can do something, because looks like the problem is not in the app but in the server (at least, for what I have managed to see).
Esteban
On 05 Aug 2014, at 14:52, Norbert Hartl <norbert@hartl.name> wrote:
Are you working on it?
Norbert
http://smalltalkhub.com/files/WADevelopmentFiles/development.css
with a 503 error (Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable)) Did you change anything meanwhile? I can download the file w/o any problems now ... and according to the HTTP Headers it's served by "Zinv HTTP Components 1.0" ... not Apache.
CU, Udo On 05.08.2014 17:34, Esteban Lorenzano wrote:
problems always arise when we cannot do much for solving them quickly (is murphy's law)⦠usually we would have: Nico, Christophe and me. But Nico is no longer working here (and also is on holidays), Christophe is in holidays and I already did as much as I can. Now, the other problem is *if* is an infrastructure problem: smalltalkhub runs in INRIA servers, and thatâs usually a good thing, but there is bureaucracy to accomplish before being able to kill a process⦠and I would like to restart apache. I *feel* that it can be a problem there because when I enter config seaside app, sometimes it fails to serve:
http://smalltalkhub.com/files/WADevelopmentFiles/development.css
with a 503 error (Failed to load resource: the server responded with a status of 503 (Service Temporarily Unavailable))
and of course, that file is served directly by apache, without going to the pharo image.
So⦠I cannot restart the apache until I find one of the guys in the IT office (and most of them are also on holidays) and convince them to give me root rights.
Obviously, I think it will be faster to wait for Christophe, because he already has the proper rights. But in any case, actual problem is not because Iâm lazy to try to solve it⦠is because I tried everything I can and now Iâm more or less as screw as you :)
Esteban
On 05 Aug 2014, at 17:03, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote:
And Christophe is the only one that can do anything?
That's such a bottle neck then we should have a little more resources for that.
Norbert
Am 05.08.2014 um 15:12 schrieb Esteban Lorenzano <estebanlm@gmail.com <mailto:estebanlm@gmail.com>>:
it works, but super slow. problem is that we need to wait until Christophe came back from holidays (next week) until we can do something, because looks like the problem is not in the app but in the server (at least, for what I have managed to see).
Esteban
On 05 Aug 2014, at 14:52, Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>> wrote:
Are you working on it?
Norbert
participants (3)
-
Esteban Lorenzano -
Norbert Hartl -
Udo Schneider