Richard van der Hoff
|
9ce2adceef
|
Include config.sample.json in dist tarball
Fixes https://github.com/vector-im/vector-web/issues/2607
|
2016-11-21 10:40:35 +00:00 |
|
David Baker
|
6e47d2f1b5
|
It's '=' in sh, not '=='
|
2016-11-11 18:07:03 +00:00 |
|
David Baker
|
3b06563960
|
Fix jenkins script / redeployer
and make them re-use the package script rather than doing their
own thing
|
2016-11-08 17:08:01 +00:00 |
|
David Baker
|
5b7f629996
|
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 15:46:21 +00:00 |
|
David Baker
|
f5d95f7314
|
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 09:40:24 +00:00 |
|
David Baker
|
d04cc03c1c
|
Take version from first arg, if given
|
2016-11-02 11:38:11 +00:00 |
|
David Baker
|
f17e851435
|
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 15:22:06 +00:00 |
|
David Baker
|
fa322e8488
|
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 18:59:33 +00:00 |
|
David Baker
|
874123bbfa
|
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 18:41:30 +00:00 |