Pyramid - Adding ZEO to an existing ZODB project - pylons-devel

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Pyramid - Adding ZEO to an existing ZODB project
Date: Fri, 2 Nov 2012 16:08:29 -0700 (PDT)
From: Ellison Marks <gty...@gmail.com>
To: pylons-devel@googlegroups.com
Message-Id: <7c69cb40-f78c-4412-8ca2-7e8240139f6d@googlegroups.com>
In-Reply-To: <17243c93-d5b8-4f4f-99fb-7d9c553a1865@googlegroups.com>
References: <11d1d996-cd3a-408e-bf5a-32dbc440a6f4@googlegroups.com>
 <17243c93-d5b8-4f4f-99fb-7d9c553a1865@googlegroups.com>
Subject: Re: Pyramid - Adding ZEO to an existing ZODB project
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_159_3722038.1351897709280"

------=_Part_159_3722038.1351897709280
Content-Type: multipart/alternative; 
	boundary="----=_Part_160_10847466.1351897709280"

------=_Part_160_10847466.1351897709280
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Yeah, I've been doing a little more reading (particularly on the paster 
config files), and it seems like the ZEO doc you referenced (that was the 
one I was reading in the first place) is slightly misleading. For one 
thing, pyramid_tm handles the repoze.tm2 slot mentioned there, as well as 
the repoze.retry slot. It also has some automatic configuration with a 
tween, so the pipeline is unnecessary. For another, the example zeo.conf 
file it lists doesn't seem to work in my setup(win7 64 bit python 2.7), as 
the address part of it errors out down the callstack, saying it requires an 
integer. I switched it to localhost:9001 and it appears to work. The 
problem I'm having now is, I can't find any docs at all on zeo.conf, to see 
if there's anything else I should tweak in there.

On Friday, November 2, 2012 8:14:55 AM UTC-7, Sam wrote:
>
> You just need to change the zodb_uri setting in your .ini file(s) to an 
> appropriate uri with the zeo: protocol (instead of the file: protocol).
>
> For example, if you're running the zeo server locally from the same 
> directory as your .ini file (as the cookbook recipe suggests under the 
> "Running" section), you would change it like so:
>
> zodb_uri = zeo://%(here)s/zeo.sock
>
> For production use, you may run the zeo server on another machine and will 
> want to connect by IP address and port instead of socket.  See 
> http://docs.pylonsproject.org/projects/pyramid_zodbconn/en/latest/ for 
> more info on ZEO urls and all the other details of zodb connections.
>
>
> On Thursday, November 1, 2012 8:57:59 PM UTC-4, Ellison Marks wrote:
>>
>> I'm a bit new to pyramid, but I'm building an application and had a few 
>> questions. The one the title refers to is basically this:
>>
>> The tutorial in the pyramid cookbook about ZEO show how to set up a 
>> server "from scratch", as it says. However, I've already started out using 
>> the ZODB scaffold, and I'm not yet confident enough to go about changing 
>> the setup.py and the ini files too much. I'm wondering if anyone could 
>> point me to a tutorial (or provide one themselves) on integrating ZEO into 
>> a project that's already using ZODB.
>>
>> Thanks in advance.
>>
>
------=_Part_160_10847466.1351897709280
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Yeah, I've been doing a little more reading (particularly on the paster con=
fig files), and it seems like the ZEO doc you referenced (that was the one =
I was reading in the first place) is slightly misleading. For one thing, py=
ramid_tm handles the repoze.tm2 slot mentioned there, as well as the repoze=
.retry slot. It also has some automatic configuration with a tween, so the =
pipeline is unnecessary. For another, the example zeo.conf file it lists do=
esn't seem to work in my setup(win7 64 bit python 2.7), as the address part=
 of it errors out down the callstack, saying it requires an integer. I swit=
ched it to localhost:9001 and it appears to work. The problem I'm having no=
w is, I can't find any docs at all on zeo.conf, to see if there's anything =
else I should tweak in there.<br><br>On Friday, November 2, 2012 8:14:55 AM=
 UTC-7, Sam wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0;marg=
in-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;"><div>You jus=
t need to change the zodb_uri setting in your .ini file(s) to an appropriat=
e uri with the zeo: protocol (instead of the file: protocol).</div><div><br=
></div><div>For example, if you're running the zeo server locally from the =
same directory as your .ini file (as the cookbook recipe suggests under the=
 "Running" section), you would change it like so:</div><div><br></div><div>=
zodb_uri =3D zeo://%(here)s/zeo.sock<br></div><div><br></div><div>For produ=
ction use, you may run the zeo server on another machine and will want to c=
onnect by IP address and port instead of socket. &nbsp;See&nbsp;<a href=3D"=
http://docs.pylonsproject.org/projects/pyramid_zodbconn/en/latest/" target=
=3D"_blank">http://docs.<wbr>pylonsproject.org/projects/<wbr>pyramid_zodbco=
nn/en/latest/</a>&nbsp;<wbr>for more info on ZEO urls and all the other det=
ails of zodb connections.</div><div><br></div><div><br></div><div>On Thursd=
ay, November 1, 2012 8:57:59 PM UTC-4, Ellison Marks wrote:<blockquote clas=
s=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #ccc =
solid;padding-left:1ex">I'm a bit new to pyramid, but I'm building an appli=
cation and had a few questions. The one the title refers to is basically th=
is:<br><br>The tutorial in the pyramid cookbook about ZEO show how to set u=
p a server "from scratch", as it says. However, I've already started out us=
ing the ZODB scaffold, and I'm not yet confident enough to go about changin=
g the setup.py and the ini files too much. I'm wondering if anyone could po=
int me to a tutorial (or provide one themselves) on integrating ZEO into a =
project that's already using ZODB.<br><br>Thanks in advance.<br></blockquot=
e></div></blockquote>
------=_Part_160_10847466.1351897709280--

------=_Part_159_3722038.1351897709280--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
