element-web/scripts/package.sh

#!/bin/sh

set -e

dev=""
if [ "$1" = '-d' ]; then
    dev=":dev"
fi

if [ -n "$DIST_VERSION" ]; then
    version=$DIST_VERSION
else
    version=`git describe --dirty --tags || echo unknown`
fi

npm run clean
npm run build$dev

# include the sample config in the tarball. Arguably this should be done by
# `npm run build`, but it's just too painful.
cp config.sample.json webapp/

mkdir -p dist
cp -r webapp vector-$version
echo $version > vector-$version/version
tar chvzf dist/vector-$version.tar.gz vector-$version
rm -r vector-$version

echo
echo "Packaged dist/vector-$version.tar.gz"
Move package script out and make it tar into a versioned top level directory. It may as well be a shell script since it's unix specific anyway, and maintaining it inside package.json is now impractical. 2016-02-24 21:41:30 +03:00			`#!/bin/sh`

			`set -e`

Fix jenkins script / redeployer and make them re-use the package script rather than doing their own thing 2016-11-08 20:08:01 +03:00			`dev=""`
It's '=' in sh, not '==' 2016-11-11 21:07:03 +03:00			`if [ "$1" = '-d' ]; then`
Fix jenkins script / redeployer and make them re-use the package script rather than doing their own thing 2016-11-08 20:08:01 +03:00			`dev=":dev"`
			`fi`

Use an env var for the package version Because supplying arguments to npm scripts is a bad idea: it just appends the arguments blindly to whatever the command was. Thanks, npm. 2016-11-04 12:40:24 +03:00			`if [ -n "$DIST_VERSION" ]; then`
			`version=$DIST_VERSION`
Take version from first arg, if given 2016-11-02 14:38:11 +03:00			`else`
			version=`git describe --dirty --tags \|\| echo unknown`
			`fi`
Move package script out and make it tar into a versioned top level directory. It may as well be a shell script since it's unix specific anyway, and maintaining it inside package.json is now impractical. 2016-02-24 21:41:30 +03:00
Build to the 'webapp' directory instead People may have config files in vector/ so it would be nonideal if we started overwriting them / blowing them away. 2016-11-08 18:46:21 +03:00			`npm run clean`
Fix jenkins script / redeployer and make them re-use the package script rather than doing their own thing 2016-11-08 20:08:01 +03:00			`npm run build$dev`
Include config.sample.json in dist tarball Fixes https://github.com/vector-im/vector-web/issues/2607 2016-11-21 13:40:35 +03:00
			`# include the sample config in the tarball. Arguably this should be done by`
			# `npm run build`, but it's just too painful.
			`cp config.sample.json webapp/`

Rename the package script/output dir to 'dist' To match conventions from other projects and match the release script which expects releasde artefacts in dist/ 2016-11-01 18:22:06 +03:00			`mkdir -p dist`
Build to the 'webapp' directory instead People may have config files in vector/ so it would be nonideal if we started overwriting them / blowing them away. 2016-11-08 18:46:21 +03:00			`cp -r webapp vector-$version`
Auto-create a sensible version file. Copy the vector dir so we can put it in there rather than creating files in the main vector dir. 2016-02-24 21:59:33 +03:00			`echo $version > vector-$version/version`
Rename the package script/output dir to 'dist' To match conventions from other projects and match the release script which expects releasde artefacts in dist/ 2016-11-01 18:22:06 +03:00			`tar chvzf dist/vector-$version.tar.gz vector-$version`
Auto-create a sensible version file. Copy the vector dir so we can put it in there rather than creating files in the main vector dir. 2016-02-24 21:59:33 +03:00			`rm -r vector-$version`
Move package script out and make it tar into a versioned top level directory. It may as well be a shell script since it's unix specific anyway, and maintaining it inside package.json is now impractical. 2016-02-24 21:41:30 +03:00
			`echo`
Rename the package script/output dir to 'dist' To match conventions from other projects and match the release script which expects releasde artefacts in dist/ 2016-11-01 18:22:06 +03:00			`echo "Packaged dist/vector-$version.tar.gz"`