← Back to team overview

ubuntu-accomplishments-contributors team mailing list archive

Re: Web Gallery Staging

 

Hi,

I just noticed it was another problem.
AFAICS we don't take care of invalidating client side cache.
We should append a changing version value ?001 to any js/css file.

On another site of mine I use the first few chars from the git version hash:
css/style.css?73c

Not sure what would be the best method here.

Robin



2012/12/19 Janos Gyerik <info@xxxxxxxxxxx>

> Hi Robin,
>
> I had a discussion with Jono last night exactly about this. Things are
> much better now, there is a cron job to run collectstatic every hour.
> Also keep in mind that your browser may cache css files and you have
> to force reload. In some unusual cases you may have to go as far as
> opening the outdated css link itself and force refresh, though I have
> not had this problem yet with the staging site (this is usually caused
> by ssl cert issues).
>
> Jono, Michael: it seems that is still a minor issue with the setup: it
> appears that collectstatic is not run immediately after you pull from
> the trunk. After my last push, the template changes became visible
> quite soon, but the css changes became visible only at the turn of the
> next hour (probably because collectstatic runs hourly). It's as if you
> have multiple cron jobs scheduled to run at different times. This is
> not good, because there is a window during which the site may look
> broken. Please double-check the setup and make sure that manage.py
> collectstatic runs right after bzr pull.
>
> Thanks,
> Janos
>
>
> On Wed, Dec 19, 2012 at 12:32 PM, Robin Gloster <robin@xxxxxxxxxx> wrote:
> > Jono,
> >
> > could you please run
> > manage.py collectstatic
> > on the server wenn deploying so that the CSS etc gets updated correctly
> >
> > Thanks
> > Robin
> >
> >
> > 2012/12/18 Jono Bacon <jono@xxxxxxxxxx>
> >>
> >> Hi All,
> >>
> >> To ease development as we head towards release, we have two servers set
> up
> >> for the Web Gallery:
> >>
> >>  * Staging - http://213.138.100.229:8000/ - trunk is pulled and
> deployed
> >> here once an hour (at every .30 in the hour). This is where the
> development
> >> team can see the site deployed against real data.
> >>  * Production - currently production is on a temporary instance as the
> >> real server is being deployed.
> >>
> >> Michael has assured me that the regular updates from trunk should be
> >> happening now. Apologies for the delay in getting this running.
> >>
> >>    Jono
> >>
> >> --
> >> Jono Bacon
> >> Ubuntu Community Manager
> >> www.ubuntu.com / www.jonobacon.org
> >> www.identi.ca/jonobacon www.twitter.com/jonobacon
> >>
> >> --
> >> Mailing list:
> https://launchpad.net/~ubuntu-accomplishments-contributors
> >> Post to     : ubuntu-accomplishments-contributors@xxxxxxxxxxxxxxxxxxx
> >> Unsubscribe :
> https://launchpad.net/~ubuntu-accomplishments-contributors
> >> More help   : https://help.launchpad.net/ListHelp
> >>
> >
> >
> > --
> > Mailing list: https://launchpad.net/~ubuntu-accomplishments-contributors
> > Post to     : ubuntu-accomplishments-contributors@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~ubuntu-accomplishments-contributors
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
>
> --
> Janos Gyerik
> http://titan2x.com/
>

Follow ups

References