https://github.com/pierrickp/liophotos
LioPhotos is a browser extension that help Lionel by adding features to Lumys Photos software
https://github.com/pierrickp/liophotos
Last synced: about 1 year ago
JSON representation
LioPhotos is a browser extension that help Lionel by adding features to Lumys Photos software
- Host: GitHub
- URL: https://github.com/pierrickp/liophotos
- Owner: PierrickP
- Created: 2023-07-07T14:25:45.000Z (about 3 years ago)
- Default Branch: master
- Last Pushed: 2023-07-07T15:24:04.000Z (about 3 years ago)
- Last Synced: 2024-04-15T14:24:59.979Z (over 2 years ago)
- Language: JavaScript
- Size: 97.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
# LioPhotos
LioPhotos is a browser extension that help Lionel by adding features to Lumys Photos software
## Features
Lumys scolaire
- Add a button to generate a CSV with child's name and child's code
- Allow select pictures from one to another using ctrl + click (or cmd + click on Mac)
Iconea Pro
- Add a textarea on customer page to prefill inputs easily
## Development
### 🛠 Build locally
1. Checkout the copied repository to your local machine
1. Run `yarn` to install all required dependencies
1. Run `yarn run build`
The build step will create the `distribution` folder, this folder will contain the generated extension.
### 🏃 Run the extension
Using [web-ext](https://extensionworkshop.com/documentation/develop/getting-started-with-web-ext/) is recommended for automatic reloading and running in a dedicated browser instance. Alternatively you can load the extension manually (see below).
1. Run `yarn run watch` to watch for file changes and build continuously
1. In another terminal, run `npx web-ext run -t chromium`
1. Check that the extension is loaded by opening the extension options ([in Firefox](media/extension_options_firefox.png) or [in Chrome](media/extension_options_chrome.png)).
#### Manually
You can also [load the extension manually in Chrome](https://www.smashingmagazine.com/2017/04/browser-extension-edge-chrome-firefox-opera-brave-vivaldi/#google-chrome-opera-vivaldi) or [Firefox](https://www.smashingmagazine.com/2017/04/browser-extension-edge-chrome-firefox-opera-brave-vivaldi/#mozilla-firefox).
### Publishing
It's possible to automatically publish to both the Chrome Web Store and Mozilla Addons at once by adding these secrets on GitHub Actions:
1. `CLIENT_ID`, `CLIENT_SECRET`, and `REFRESH_TOKEN` from [Google APIs][link-cws-keys].
2. `WEB_EXT_API_KEY`, and `WEB_EXT_API_SECRET` from [AMO][link-amo-keys].
Also include `EXTENSION_ID` in the secrets ([how to find it](https://stackoverflow.com/a/8946415/288906)) and add Mozilla's [`gecko.id`](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/browser_specific_settings) to `manifest.json`.
The GitHub Actions workflow will:
1. Build the extension
2. Create a version number based on the current UTC date time, like [`19.6.16`](https://github.com/fregante/daily-version-action) and sets it in the manifest.json
3. Deploy it to both stores
#### Auto-publishing
Thanks to the included [GitHub Action Workflows](.github/workflows), if you set up those secrets in the repo's Settings, the deployment will automatically happen:
- on a schedule, by default [every week](.github/workflows/release.yml) (but only if there are any new commits in the last tag)
- manually, by clicking ["Run workflow"](https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/) in the Actions tab.