Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
Build your own version of Akeeba release, use at your own risk, not endorsed by https://www.akeebabackup.com/
#!/bin/bash
# you need some dependencies, run them once
# pear channel-discover pear.phing.info
# pear install [--alldeps] phing/phing
# pear install -f VersionControl_SVN
# the major difficulties is to find a combination of version that work together...these are the latest as of today 19.05.2016
export release_version=3.1.1
export buildfiles_version=master
export fof_version=3.0.10
# -- dont change below this line ----------------------
date=`date +%d%m%Y`
export base=/tmp/arsrele-${date}
function init() {
rm -rf ${base}
mkdir ${base}
cd ${base}
git clone https://github.com/akeeba/buildfiles.git
cd buildfiles
git checkout -b ${buildfiles_version}
cd ${base}
git clone https://github.com/akeeba/fof.git
mv fof fof3
cd fof3
git checkout -b ${fof_version}
cd ${base}
git clone https://github.com/akeeba/release-system.git
mv release-system ars
cd ars
git checkout -b ${release_version}
}
function build() {
cd ${base}/buildfiles
php ../buildfiles/tools/link.php `pwd`
cd build
phing link
phing git
cd ${base}/fof3
php ../buildfiles/tools/link.php `pwd`
cd build
phing link
phing git
cd ${base}/ars
php ../buildfiles/tools/link.php `pwd`
cd build
phing link
phing git
cd ${base}
}
init
build
@nikosdion

This comment has been minimized.

Copy link

commented Mar 10, 2017

Hi Cedric! I stumbled upon this gist looking for something entirely different. So I thought I could comment on it.

I don't tag ARS releases very often. You can always use the development branches of both ars and fof. That the configuration I use in my dev server. If you want to be ultra safe use development ars with latest tagged fof. That's always the deployed configuration on the live server ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.