b115f946cd
official release builds are built from branch master, as the respective tags point to commits in branch master (only). to check whether or not a new version is available, we should check branch master for new commits. checking against HEAD does not work as expected, at least in the OpenDTU-OnBattery repo, since its default branch is "development", not "master". usually, there should be no commits on master in between releases, so we will now only show "update available" if a new release was made. this is not foolproof, but should work as long as we keep "master" clean. for builds from other branches, the comparison is perfomed against the respective branch. if a user installed a binary built by github actions based on a development branch, the user will see "update available" if new commits were added to the development branch since. for other branches, also pull request builds, the test for updates will fail as the branch name shown in the system info is not actually a branch name, e.g., "helgeerbe/OpenDTU-OnBattery/pr1183-202408212043". |
||
|---|---|---|
| .. | ||
| .vscode | ||
| public | ||
| src | ||
| .gitignore | ||
| .prettierrc.json | ||
| env.d.ts | ||
| eslint.config.js | ||
| index.html | ||
| package.json | ||
| README.md | ||
| tsconfig.config.json | ||
| tsconfig.json | ||
| vite.config.ts | ||
| yarn.lock | ||
OpenDTU web frontend
You can run the webapp locally with yarn dev. If you enter the IP of your ESP in the vite.user.ts beforehand (template can be found in vite.config.ts), all api requests will even be proxied to the real ESP. Then you can develop the webapp as if it were running directly on the ESP. The yarn dev also supports hot reload, i.e. as soon as you save a vue file, it is automatically reloaded in the browser.
Project Setup
yarn install
Compile and Hot-Reload for Development
yarn dev
Type-Check, Compile and Minify for Production
yarn build
Lint with ESLint
yarn lint