* feat: update to Phenix HTML 4.1
* fix: updating to the new Gettext.Backend approach
* chore: update pot files ro locale version 45.0.0
* fix: downgrade cloack back to 1.1.2
* revert: merge of mix.lock
* fix: new syntax for field name generation for phx-feedback-for
* Revert "fix: new syntax for field name generation for phx-feedback-for"
This reverts commit 4d95e4f1c9367d2d5c606ced2190ab23edcb971b.
* fix: downgrade floki back to 0.35.2
* Revert "fix: downgrade floki back to 0.35.2"
This reverts commit a4f0b6bf4b32099d89003c3d20f72333d510e109.
* fix: ensure floki nil is handled
* style: linter findings
* Revert "fix: ensure floki nil is handled"
* fix: new syntax for field name generation for phx-feedback-for
* debug: floki paramter error
* Revert "debug: floki paramter error"
This reverts commit 61920267edf5186b593920bde7d87e8b30af55aa.
* fix: Remove unnecessary code in settings_test.exs which breaks floki 0.36+
* Add URL_PATH environment variable for reverse proxy deployments
For example, this can be used to run TeslaMate behind a reverse proxy, using a
URL path such as "/teslamate".
* gettext: update pot and po files
Generated using:
mix gettext.extract --merge
* web: run mix format
* gettext: update pot and po files
Re-generating gettext files after running mix format.
Generated using:
mix gettext.extract --merge
* Upgrade to phoenix 1.7.0
The minimal changes necessary to compile the application
* Import Phoenix.Component instead of LiveView
* Fix compilation warnings
* mix format
* Update tests to trim newline characters
* mix gettext.extract --merge
* style: correct linting
* rebuild gettext
* fix: correct spacing before unit for energy added
* fix: use unicode character for whitespace
* fix: spacing with witespace
* fix: use numeric value for charge_energy_added in charging test
* fix: avoid warning about unsued function, which is actually used in plug
* fix: use whitespace in test before charge_energy_added
---------
Co-authored-by: JakobLichterfeld <jakob-lichterfeld@gmx.de>
Store API tokens encrypted in the database.
During the database migration a randomly generated key will be used encrypt the tokens if no ENCRYPTION_KEY environment variable was provided.
If the application is started without the presence of an ENCRYPTION_KEY (or if the key failed to decrypt the existing tokens), the UI will display a warning with further instructions.
