element-web/scripts/package.sh

#!/bin/bash

set -e

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

yarn clean
VERSION=$version yarn build

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

mkdir -p dist
cp -r webapp element-$version

# Just in case you have a local config, remove it before packaging
rm element-$version/config.json || true

$(dirname $0)/normalize-version.sh ${version} > element-$version/version

tar chvzf dist/element-$version.tar.gz element-$version
rm -r element-$version

echo
echo "Packaged dist/element-$version.tar.gz"
remove leading v in /version file so its semver and also then consistent with electron versioning Signed-off-by: Michael Telatynski <7t3chguy@gmail.com> 2017-05-02 22:24:02 +02:00			`#!/bin/bash`
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 19:41:30 +01:00
			`set -e`

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 10:40:24 +01:00			`if [ -n "$DIST_VERSION" ]; then`
			`version=$DIST_VERSION`
Take version from first arg, if given 2016-11-02 12:38:11 +01: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 19:41:30 +01:00
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best. 2019-03-12 12:06:57 +01:00			`yarn clean`
Pass our VERSION to sentry plugin's release arg via env (#19474) Use our existing VERSION, deduced by the packaging script, as the release for sentry sourcemaps. This will be undefined for dev builds. 2021-10-22 16:06:14 +02:00			`VERSION=$version yarn build`
Include config.sample.json in dist tarball Fixes https://github.com/vector-im/vector-web/issues/2607 2016-11-21 11:40:35 +01:00
			`# include the sample config in the tarball. Arguably this should be done by`
Update scripts and docs to use `yarn` where appropriate Most `npm` operations are replaced with `yarn`, which generally has better behavior. However, steps like publish that write to the NPM registry are left to `npm`, which currently handles these tasks best. 2019-03-12 12:06:57 +01:00			# `yarn build`, but it's just too painful.
Include config.sample.json in dist tarball Fixes https://github.com/vector-im/vector-web/issues/2607 2016-11-21 11:40:35 +01:00			`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 16:22:06 +01:00			`mkdir -p dist`
Updating package.sh This should correct the tarball structure from `riot-$version` to `element-$version`. 2020-07-31 22:59:13 +02:00			`cp -r webapp element-$version`
remove leading v in /version file so its semver and also then consistent with electron versioning Signed-off-by: Michael Telatynski <7t3chguy@gmail.com> 2017-05-02 22:24:02 +02:00
Remove config.json from package dir 2019-04-24 12:27:07 +02:00			`# Just in case you have a local config, remove it before packaging`
Updating package.sh This should correct the tarball structure from `riot-$version` to `element-$version`. 2020-07-31 22:59:13 +02:00			`rm element-$version/config.json \|\| true`
Remove config.json from package dir 2019-04-24 12:27:07 +02:00
Fix Docker build versioning (#20077) * Centralise version scripts and fix Docker version * Refactor generation of a git-hash-based version into get-version-from-git * Refactor normalization of versions (stripping leading v) into normalize-version.sh * Call get-version-from-git from ci_package.sh, call normalize-version from package.sh * Refactor docker-write-version.sh into docker-package.sh, which both writes the version file and invokes yarn build passing VERSION * Normalize the version received from the server 2021-12-07 05:11:01 +01:00			`$(dirname $0)/normalize-version.sh ${version} > element-$version/version`
remove leading v in /version file so its semver and also then consistent with electron versioning Signed-off-by: Michael Telatynski <7t3chguy@gmail.com> 2017-05-02 22:24:02 +02:00
Updating package.sh This should correct the tarball structure from `riot-$version` to `element-$version`. 2020-07-31 22:59:13 +02:00			`tar chvzf dist/element-$version.tar.gz element-$version`
			`rm -r element-$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 19:41:30 +01:00
			`echo`
Updating package.sh This should correct the tarball structure from `riot-$version` to `element-$version`. 2020-07-31 22:59:13 +02:00			`echo "Packaged dist/element-$version.tar.gz"`