That's good Romain.

The Error message gets displayed because the staging is hosted on a shared dreamhost account.
If it gets over a certain memory limit it gets killed, that's why it displays ok when you refresh it.
It's possible that submissions on the staging would go unnoticed, but I'm pretty sure that wont' be the case on the live server.
Again, if there is another staging server that we could host it, it wouldn't be a problem to change the deployment to the new one.
Maybe it would be a good idea to do it before the live server anyway.

Kosmas

On 30 March 2011 11:37, Romain d'Alverny <rdalverny@gmail.com> wrote:
On Wed, Mar 30, 2011 at 12:30, Kosmas Chatzimichalis <Kosmas@mach7x.com> wrote:
> Sorry cannot be at the meeting today..
>
> Unfortunately not a lot to report on maintdb as didn't have any time to go
> back to it.
> Only thing I've managed to have a look at was the ability to restrict the
> authenticity token in certain actions, instead of the whole application.

Ok. Didn't notify about it largely here, but we plugged the
buildsystem into the staging app to see it in real use (see
http://www.maintdb2.mageia.org.uk/ ). By the way, I notice a server
error each time I go there; on reload it works nice but... there it
is, so I'm not sure what causes it (and if some packages submissions
go unnoticed that way).

Romain
_______________________________________________
Mageia-webteam mailing list
Mageia-webteam@mageia.org
https://www.mageia.org/mailman/listinfo/mageia-webteam