Hello,
I've been trying to make the step of moving between my development
version and production version seamless, so the paver make_release
function seemed to be exactly what I needed. In pavement.py
make_release calls package_all, but package_all has 'build' as a
prerequisite.
I don't understand why, if you want to build a package for installing,
why you would want to rebuild it. The biggest problem is that for my
release I change out local_settings....but then during the build
process it calls syncdb....but I don't want it to syncdb at that
point, the whole thing will be installed and sync on another machine.
Calling syncdb on my dev machine with my production local_setttings
of course won't work. Can I safely comment out the build step from
the package building process or is there something I am missing here
and that it needs to be rebuilt before packaging for deployment ?
@needs(
'build',
'package_geoserver',
'package_geonetwork',
'package_webapp',
'package_bootstrap'
)
def package_all(options):
info('all is packaged, ready to deploy')
Matt Hanson
Applied GeoSolutions
403 Kent Place
Newmarket, NH 03857
