Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| igotcha:installation [2019/08/21 12:29] – sarah | igotcha:installation [2023/08/11 12:18] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 27: | Line 27: | ||
| * Under Override os type, select the latest version of the software | * Under Override os type, select the latest version of the software | ||
| * Save again | * Save again | ||
| - | |||
| - | ==== Lamar Development ==== | ||
| - | |||
| - | Bitbucket: [[https:// | ||
| - | |||
| - | === Build Versions === | ||
| - | Written on August 16th, 2019 | ||
| - | |||
| - | Lamar version: 5.0.6 | ||
| - | iGotcha Signage version: 2.14.0.5 | ||
| - | |||
| - | Update: | ||
| - | iGS v. 2.14.0.5 resolves issue with Advanced Installer not updating the registry key to show the latest version of Lamar application on CMS. | ||
| - | |||
| - | Also, if you come across a computer that has Lamar v.3.x.x or v.4.x.x installed, then you need to uninstall the application first before you can install version 5.x.x. | ||
| - | N.B. Lamar CMS is more reliable than iGS CMS with respect to showing Lamar version. | ||
| - | |||
| - | === Preparing a new build (with Advanced Installer): === | ||
| - | Note: This steps below show you how to prepare a new build for upgrading the kiosks | ||
| - | |||
| - | Refer to this path in iGotcha Drive if you need to know how to set up Advanced Installer: | ||
| - | - Run command to change application version: yarn run version --new-version XXXXX | ||
| - | - Run command: yarn run package | ||
| - | - Go to Advanced Installer on Quy's computer: Lammar_NEW_July23.aip | ||
| - | - In " | ||
| - | - In "Files and Folders" | ||
| - | - In " | ||
| - | - Click to save | ||
| - | - Make a new build. The new .msi file is saved in this path: D: | ||
| - | - Upload the msi file to AWS. Save it in this folder: " | ||
| - | - Don't forget to make this file public. Once you've done that, then copy the Object URL of the msi file | ||
| - | - Go back to Advanced Installer. Open another file: update_NEW_July23.aip | ||
| - | - In " | ||
| - | - In " | ||
| - | - In " | ||
| - | - Click to save | ||
| - | - Click to build | ||
| - | - It will create a text file for you, titled " | ||
| - | - Once it's been uploaded to AWS, then make this file public | ||
| - | |||
| - | === Google Analytics Reports === | ||
| - | * **Credentials**: | ||
| - | * **Type of reports**: | ||
| - | * **Duration**: | ||
| - | * **Final format of the report**: Not specified by the client. You could export the reports to Google Sheets and email the client links to these sheets. | ||
| - | * **Where to generate reports on Google Analytics**: | ||
| - | |||
| - | N.B. Previous reports are saved in Google Sheets in case you need an idea of what the reports should look like | ||
| - | |||
| - | === Development === | ||
| - | Api keys: | ||
| - | We use 2 APIs that require APIs key, which can be found here: [[https:// | ||
| - | * Google Map API | ||
| - | * Darksky (to get temperature) | ||
| - | |||
| - | These Apis key are used in main process and are also store in [[https:// | ||
| - | |||
| - | Google Map API: | ||
| - | * use to render google map | ||
| - | * Use to [[https:// | ||
| - | |||
| - | Darksky Api: | ||
| - | Used to fetch weather in [[https:// | ||
| - | |||