Oh. I'll look into that, thanks for the tip! On Wednesday, July 2, 2014 3:52:21 PM UTC+2, Josh Cartmell wrote: > > I vaguely recall fixing a similar problem at some point in time by setting > the PYTHON_EGG_CACHE to a different directory. As far as I know it > definitely does need to be a directory that the executing user has access > to. > > I'm not familiar with OpenShift, if you use a virtualenv though I would > probably set the egg cache to be inside your virtualenv, if not I would set > it to somewhere within your home directory. My thinking (which might be > totally wrong) is that /tmp generally can be arbitrarily wiped at any point > in time, if it got wiped while your site was using it that might cause > problems. > > > On Wed, Jul 2, 2014 at 5:58 AM, Fredrik Blomqvist <[email protected] > <javascript:>> wrote: > >> I (temporarily?) solved the problem by setting the PYTHON_EGG_CACHE env >> var to /tmp at the top of settings.py: >> >> os.environ['PYTHON_EGG_CACHE'] = '/tmp' >> >> In case a better solution exists (remember that the app resides on >> OpenShift) I would appreciate if someone told me about it. If not, well >> then I guess the case is closed! >> >> Regards, Fredrik >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Mezzanine Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
