This project was generated with angular-cli version 1.0.0-beta.26.
Run npm run build to build the project. The build artifacts will be stored in the dist/ directory. Use the -prod flag for a production build.
After running npm run build, run npm run electron and an electron app will be served up.
Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.
Run ng github-pages:deploy to deploy to GitHub Pages.
To get more help on the angular-cli use ng help or go check out the Angular-CLI README.
Due to issues from building the amo-tools-suite node modules, packages cannot be built cross platform.
electron-builder makes one installer that will install either x64 or ia32 as appropriate
- electron-builder v13.9.0+
- electron-packager v8.5.2
Run npm run windows to build the installer in x64 and ia32.
Installer will be in ../output
latest.yml will be in ../output
- icnutils
- graphicsmagick
- xz-utils
- rpm
- apt
- electron-builder v13.9.0+
- electron-packager v8.5.2
Run npm run linux to build a tar.gz, .deb, and .rpm in x64
Packages will be in ../output
*Cannot build cross platform on Linux due to building the amo-tools-suite node module. To build for ia32 on 32bit Linux, run ./node_modules/.bin/build -l --ia32
Can only be done on Mac due to signing issues
- electron-builder v13.9.0+
- electron-packager v8.5.2
- An Apple Developer account and correct code signing certificate
Run npm run mac to build a .zip and .dmg in x64 and ia32.
Packages will be in ../output/mac
latest-mac.json will be in ../output/github
The code will be signed with a certificate from your keychain automatically as long as it is appropriate and valid
electron-builder and electron autoUpdate does not support auto updating on Linux
- electron-updater v1.8.2
- electron-log v1.3.0
- electron-builder v13.9.0+
- electron-packager v8.5.2
Build the application as directed above. electron-builder will create the installer/executable AND a file named latest.yml or latest-mac.json (when building Mac packages).
Go to the AMO-Tools-Desktop releases page in GitHub.
Draft a new release. For the tag version, make sure to include a v before the version number (example: v0.0.1).
Upload BOTH the installer/executable AND the latest.yml and latest-mac.json. (the autoUpdater looks for the latest.yml and latest-mac.json in the release. If they is not present, it will not work.)
Publish the release.
Once the older version of the application is started, it will check for an update, download it, and install it automatically.