Download installable product test
Christopher Johnson
Kapil uploaded a nightly build test distribution for GetPaid. The idea being that you can grab the file, unpack in your Products directory, restart zope and then have GetPaid running. It is in the downloads section of the Google Code site (the first one at http://getpaid.googlecode.com/files/PloneGetPaid-2007-07-12.tgz ).
I forgot to test my instance before installing it (doh!), but after adding the products, I can't get to any of the Plone sites or add a new one. I am wondering how the getpaid.core gets into the products (since the download only includes PloneGetPaid and Five).
Anyway, the simple idea is delightful and will be great for distribution!
Cheers,
Chris
--
Cofounder and CEO
ifPeople - Innovation for People
www.ifpeople.net
t: 678-608-3408
130 Boulevard NE, #6
Atlanta, GA 30312
kap...@gmail.com
there's been a huge amount of progress made on getpaid during and
since the google sprint, one of the things we need desparately need
before release is more widespreading testing.
> enter buildout
> exit testers
ouch.. buildout has been problematic for a few reasons, its finicky,
it obtuse in error messages, and just generally assumes some seasoned
developer. we need a better way of doing this, doing it by hand was
nasty at the north carolina sprint, where most of the time was spent
getting folks setup with development environments. but while buildout
has been successful when it works in allowing folks to get started
with getpaid, its been a source of frustration, and its only been
getting worse. the case in point of setting up an authorizeddot
processor is a good example, buildout insists on compiling it,
requiring a lot of dev (gcc/libssl-dev/swig/python-dev/etc) software,
even if it could be installed simply on the system via other means.
the handling of dependencies of zope.* packages which are in the zope
installation is really bad, it goes out and fetches the latest zope
3.4 versions from pypi, which will break the system..
anyways, buildout has become more trouble than its worth, maybe its an
okay tool for deployment, and its likely to see increased use w/ plone
3, but for getpaid, where we want to have an easy entry to using the
system in a variety of contexts (on an existing site, for example),
and its just proved not well suited.
so, i spent some hours today basically coming up with a replacement
for this. basically we now have a script that extract the packages
from our buildout directory structure and create a tarball of plain
zope products, that you can drop into your *existing plone site*.
a new nightly that should work better is up at,
http://getpaid.googlecode.com/files/PloneGetPaid-2007-07-13.tgz
note this is not the one that chris linked to earlier.
as for the authorizedotnet processor and its m2crypto requirements, we
can now ask people to just install it via whatever platform specific
tools they have (binary on windows, apt-get install m2crypto on debian/
ubuntu, etc) instead of trying to deal with buildout compiling it.
currently these nightlies are not useable for development in the sense
that their not connected to svn, that still requires buildout...
so whats the future of buildout and getpaid development? its going
away before milestone 1, but not immediately, you'll still be able to
run and develop with buildout for a while. i'll send out an email when
we have a new buildout free bundle available for use.
-kapil
On Jul 12, 8:50 pm, "Christopher Johnson" <cjj.ifpeo...@gmail.com>
wrote: