SVN set up for Joomla Components - Joomla! Forum - community, help and support
i began using svn component development , have basic understanding. have 3 branches each component, admin,site,and install. keep .xml file in install track changes it.
1. how assign version numbers component. lets admin revision 5 , site revision 20 , install revision 7. how find these revision numbers , scheme making version number of entire component? 5.20.7?
2. how deal .xml file in admin section. when component installed, .xml file stored in admin section of component. when check out admin side of component updating , testing need .xml file in admin section. when export admin side of component directory create installable archive, file in admin side causes installation error. there way set svn repository or xml file avoid this? should write script automate export deletes offending .xml?
3. have working copies of given component in several places. read part of thread suggested linux use soft links directory use checkout various apache directories used testing. command line setting soft links , there apache settings need changed?
thank you!
1. how assign version numbers component. lets admin revision 5 , site revision 20 , install revision 7. how find these revision numbers , scheme making version number of entire component? 5.20.7?
2. how deal .xml file in admin section. when component installed, .xml file stored in admin section of component. when check out admin side of component updating , testing need .xml file in admin section. when export admin side of component directory create installable archive, file in admin side causes installation error. there way set svn repository or xml file avoid this? should write script automate export deletes offending .xml?
3. have working copies of given component in several places. read part of thread suggested linux use soft links directory use checkout various apache directories used testing. command line setting soft links , there apache settings need changed?
thank you!
i have revised thinking , devised linux shell scripts automate set up. far think clever.
1. keep each joomla module in 2 repositories, site , admin. using admin version , site version numbers in assigning version numbers release. admin = 31 site = 27 version 1.31.27. version 1 changes 2 when sql changes.
2.-3. have number of scripts automate this. make work well, named repository parent directory same component - com_yourcomponent. have /srv/svn/com_yourcomponent.
i keep files end in admin part of component in admin branch, of directory named after component, /svn/com_yourcomponent/branches/admin, admin being actual repository of scripts. keep site repository in directory called /svn/com_yourcomponent/branches/site. not sure why threw in directory branches. seems there should better set handling branches of code.
to create intallable zip file use following script named z.sh first parameter component name:
rm -r /home/mydir/joomla/extensions/$1/*
svn export file:///srv/svn/$1/branches/admin /home/mydir/joomla/extensions/$1/admin
svn export file:///srv/svn/$1/branches/site /home/mydir/joomla/extensions/$1/site
cp /home/mokelly1/joomla/extensions/gpl.txt /home/mydir/joomla/extensions/$1
cp /home/mokelly1/joomla/extensions/$1/admin/index.html /home/mydir/joomla/extensions/$1
mv /home/mokelly1/joomla/extensions/$1/admin/*.xml /home/mydir/joomla/extensions/$1
mv /home/mokelly1/joomla/extensions/$1/admin/install.*.php /home/mydir/joomla/extensions/$1
cd /home/mydir/joomla/extensions
zip -r $1.zip $1/*
you notice on line 4, copy gpl license , on line 5 copy new index.html file. seldom remember include gpl , index.html allows installation work.
to make working copy can update , test in sandbox, install component , run script named w.sh first parameter component name:
rm -r /srv/www/htdocs/mydomain.com/administrator/components/$1
rm -r /srv/www/htdocs/mydomain.com/components/$1
rm -r /home/mydir/public_html/$1/admin
rm -r /home/mydir/public_html/$1/site
svn checkout file:///srv/svn/$1/branches/admin /home/mydir/public_html/$1/admin
svn checkout file:///srv/svn/$1/branches/site /home/mydir/public_html/$1/site
ln -s /home/mydir/public_html/$1/admin /srv/www/htdocs/mydomain.com/administrator/components/$1
ln -s /home/mydir/public_html/$1/site /srv/www/htdocs/mydomain.com/components/$1
this removes component scripts installed joomla , replaces them link fresh working copy in home directory.
the component still works in web server revising , testing working copy in home directory.
when revisions complete, commit using graphic interface esvn. in order correctly test new version, run following script named r.sh first parameter component name:
rm -r /srv/www/htdocs/mydomain.com/administrator/components/$1
rm -r /srv/www/htdocs/mydomain.com/components/$1
svn export file:///srv/svn/$1/branches/admin /srv/www/htdocs/mydomain.com/administrator/components/$1
svn export file:///srv/svn/$1/branches/site /srv/www/htdocs/mydomain.com/components/$1
chown -r wwwrun:www /srv/www/htdocs/mydomain.com/administrator/components/$1/*
chown -r wwwrun:www /srv/www/htdocs/mydomain.com/components/$1
this removes links home directory in sandbox component , exports latest version component directories site , admin. able correctly un-install joomla component, install new revised component zip file created first script. way install tested new revisions.
i not sure if handling permissions correctly best security.
to make process seem automated, created icons on desktop call these scripts each component. doing more clicking , less wondering next.
now if automate version portion of zip file name nice!
hope helps save time!
1. keep each joomla module in 2 repositories, site , admin. using admin version , site version numbers in assigning version numbers release. admin = 31 site = 27 version 1.31.27. version 1 changes 2 when sql changes.
2.-3. have number of scripts automate this. make work well, named repository parent directory same component - com_yourcomponent. have /srv/svn/com_yourcomponent.
i keep files end in admin part of component in admin branch, of directory named after component, /svn/com_yourcomponent/branches/admin, admin being actual repository of scripts. keep site repository in directory called /svn/com_yourcomponent/branches/site. not sure why threw in directory branches. seems there should better set handling branches of code.
to create intallable zip file use following script named z.sh first parameter component name:
rm -r /home/mydir/joomla/extensions/$1/*
svn export file:///srv/svn/$1/branches/admin /home/mydir/joomla/extensions/$1/admin
svn export file:///srv/svn/$1/branches/site /home/mydir/joomla/extensions/$1/site
cp /home/mokelly1/joomla/extensions/gpl.txt /home/mydir/joomla/extensions/$1
cp /home/mokelly1/joomla/extensions/$1/admin/index.html /home/mydir/joomla/extensions/$1
mv /home/mokelly1/joomla/extensions/$1/admin/*.xml /home/mydir/joomla/extensions/$1
mv /home/mokelly1/joomla/extensions/$1/admin/install.*.php /home/mydir/joomla/extensions/$1
cd /home/mydir/joomla/extensions
zip -r $1.zip $1/*
you notice on line 4, copy gpl license , on line 5 copy new index.html file. seldom remember include gpl , index.html allows installation work.
to make working copy can update , test in sandbox, install component , run script named w.sh first parameter component name:
rm -r /srv/www/htdocs/mydomain.com/administrator/components/$1
rm -r /srv/www/htdocs/mydomain.com/components/$1
rm -r /home/mydir/public_html/$1/admin
rm -r /home/mydir/public_html/$1/site
svn checkout file:///srv/svn/$1/branches/admin /home/mydir/public_html/$1/admin
svn checkout file:///srv/svn/$1/branches/site /home/mydir/public_html/$1/site
ln -s /home/mydir/public_html/$1/admin /srv/www/htdocs/mydomain.com/administrator/components/$1
ln -s /home/mydir/public_html/$1/site /srv/www/htdocs/mydomain.com/components/$1
this removes component scripts installed joomla , replaces them link fresh working copy in home directory.
the component still works in web server revising , testing working copy in home directory.
when revisions complete, commit using graphic interface esvn. in order correctly test new version, run following script named r.sh first parameter component name:
rm -r /srv/www/htdocs/mydomain.com/administrator/components/$1
rm -r /srv/www/htdocs/mydomain.com/components/$1
svn export file:///srv/svn/$1/branches/admin /srv/www/htdocs/mydomain.com/administrator/components/$1
svn export file:///srv/svn/$1/branches/site /srv/www/htdocs/mydomain.com/components/$1
chown -r wwwrun:www /srv/www/htdocs/mydomain.com/administrator/components/$1/*
chown -r wwwrun:www /srv/www/htdocs/mydomain.com/components/$1
this removes links home directory in sandbox component , exports latest version component directories site , admin. able correctly un-install joomla component, install new revised component zip file created first script. way install tested new revisions.
i not sure if handling permissions correctly best security.
to make process seem automated, created icons on desktop call these scripts each component. doing more clicking , less wondering next.
now if automate version portion of zip file name nice!
hope helps save time!
Comments
Post a Comment