That's great feedback, thanks! I'm going to take your advice and just use mysql :)
Thanks again, Mark Mark Baker Technology Lead, Tools http://www.mindcandy.com http://www.moshimonsters.com +44 (0) 7971 808 540 [email protected] On 10 March 2014 20:48, Leandro Regueiro <[email protected]> wrote: > On Mon, Mar 10, 2014 at 7:59 PM, Jerome Leclanche <[email protected]> > wrote: > > Right. I haven't tested that with postgres (I'm not familiar with that > > part really). > > > > I would say try to get it working without fabric first. > > J. Leclanche > > > > > > On Mon, Mar 10, 2014 at 6:54 PM, Mark Baker <[email protected]> wrote: > >> Thanks for the response, but I'm not following those instructions. I'm > >> trying to follow the fabric instructions here > >> http://pootle.readthedocs.org/en/latest/server/fabric_deployment.html > >> > >> Because I want to be able to redeploy if I have code changes, and it > also > >> need it to be a production rather than an evaluation install. > >> > >> I would also assume that 'Poole setup' is basically running manage.py > setup > >> > >> But I'm not at my computer to check immediately. > > Yes, 'pootle setup' is the same as 'python manage.py setup'. > > Pootle is usually deployed using MySQL, and despite it is known that > some people tried to use PostgreSQL I am actually not sure if they > succeeded. Maybe it is worth considering using MySQL. > > Leaving that aside, if you have problems running any commands it is a > good idea to avoid running a "porcelain" command like 'setup' and > instead run the several "plumbing" commands it actually masks. These > are the commands it hides when running for new deployments (for > upgrading existing deployments the commands are others): > > $ python manage.py syncdb --noinput > $ python manage.py migrate > $ python manage.py initdb > > All these commands have Fabric equivalents (see below). Since you have > done previous tries you might have a broken DB, so before running the > previous commands you will probably have to wipe out all the tables in > the DB. > > This should work (assuming you have a clean DB): > > fab production bootstrap > fab production create_db > fab production update_config > fab production syncdb > fab production migratedb > fab production initdb > fab production deploy_static > fab production enable_site > > But we have never tried doing this with PostgreSQL so we can't tell > for sure if it will work. > > > >> On Monday, March 10, 2014, Jerome Leclanche <[email protected]> wrote: > >>> > >>> Are you sure you followed the guide here: > >>> > >>> > http://pootle.readthedocs.org/en/latest/server/installation.html#initializing-the-configuration > ? > >>> "manage.py setup" is not part of that. > >>> J. Leclanche > >>> > >>> > >>> On Mon, Mar 10, 2014 at 5:14 PM, Mark Baker <[email protected]> > wrote: > >>> > Ok, I'm now using git master branch. > >>> > > >>> > That was a little better -- syncdb worked. > >>> > manage.py setup didn't though. > >>> > > >>> > 2014-03-10 16:56:03,971 INFO Using Python PO > >>> > 2014-03-10 16:56:04,496 INFO Setting up a new Pootle installation. > >>> > Syncing... > >>> > DatabaseError: current transaction is aborted, commands ignored until > >>> > end of > >>> > transaction block > >>> > > >>> > > >>> > On the database side the actual error was: > >>> > > >>> > > >>> > ERROR: relation "pootlecache" does not exist at character 22 > >>> > > >>> > STATEMENT: SELECT COUNT(*) FROM "pootlecache" > >>> > > >>> > > >>> > I also tried running manage.py migrate which did work, but then > >>> > manage.py > >>> > initdb failed with: > >>> > > >>> > 2014-03-10 17:07:08,789 INFO Using Python PO > >>> > 2014-03-10 17:07:09,263 INFO Populating the database. > >>> > DoesNotExist: PootleProfile matching query does not exist. > >>> > > >>> > > >>> > I get the same error now from 'manage.py setup'. > >>> > > >>> > 2014-03-10 17:09:57,401 INFO Populating the database. > >>> > DoesNotExist: PootleProfile matching query does not exist. > >>> > > >>> > > >>> > underlying db error: ERROR: relation "pootle_app_pootleprofile" does > not > >>> > exist at character 204 > >>> > > >>> > > >>> > I hope that's of use to someone, I think I'll be attempting to use > mysql > >>> > at > >>> > this point... > >>> > > >>> > > >>> > > >>> > > >>> > On 10 March 2014 16:27, Jerome Leclanche <[email protected]> wrote: > >>> >> > >>> >> There is better Postgres support in git currently. If you're not on > >>> >> git master, you will encounter issues with migrations. > >>> >> > >>> >> Try it there, and use manage.py syncdb before issuing any other > >>> >> manage.py command. Should help. > >>> >> > >>> >> On Mon, Mar 10, 2014 at 3:57 PM, Mark Baker <[email protected]> > >>> >> wrote: > >>> >> > Hey folks, > >>> >> > > >>> >> > I'm setting up a new pootle server and ideally I'd like to use > >>> >> > Postgres. > >>> >> > I > >>> >> > love that pootle comes with a Fabric deploy file, so I'm trying to > >>> >> > use > >>> >> > that > >>> >> > as well. > >>> >> > > >>> >> > The Fabric installer currently only supports mysql but I've added > >>> >> > postgres > >>> >> > support for the CREATE DATABASE / DROP DATABASE statement, as that > >>> >> > was > >>> >> > fairly easy :) > >>> >> > > >>> >> > However, I'm now stuck at the 'manage.py setup' stage with a > postgres > >>> >> > error. > >>> >> > The actual error from Fabric is this unhelpful one: > >>> >> > > >>> >> > django.db.utils.DatabaseError: current transaction is aborted, > >>> >> > commands > >>> >> > ignored until end of transaction block > >>> >> > > >>> >> > But digging into the postgres logs I found this error first: > >>> >> > 14:30:54 UTC:172.31.21.93(57281):pootle@pootle:[18390]:ERROR: > >>> >> > relation > >>> >> > "django_site" does not exist at character 78 > >>> >> > 2014-03-10 14:30:54 > >>> >> > UTC:172.31.21.93(57281):pootle@pootle:[18390]:STATEMENT: > >>> >> > SELECT "django_site"."id", "django_site"."domain", > >>> >> > "django_site"."name" > >>> >> > FROM "django_site" WHERE "django_site"."id" = 1 > >>> >> > 2014-03-10 > >>> >> > > >>> >> > > >>> >> > To give you an idea of what I've done so far I've run > >>> >> > fab production bootstrap > >>> >> > fab production create_db > >>> >> > fab production update_config > >>> >> > fab production setup > >>> >> > > >>> >> > Any thoughts? Is there another step for setting up a new server > that > >>> >> > I've > >>> >> > missed? > >>> >> > > >>> >> > P.S. is there a mailing list archive around? I hate asking > questions > > The archives are in > http://sourceforge.net/p/translate/mailman/translate-pootle/ > > Bye > ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
