* Pretend to upload source maps to sentry
* Build release not in docker so we can upload source maps sensibly
and also upload the release as a plain tarball while we're at it
* fix yaml
* Try specifying version this way
* test rebuild
* pass secrets through
* Too many sentries
* It's almost 2023 and we're still having BSD vs GNU tar issues
* Maybe get sensible tag name & release identifier
* Wrong plugin, and also try the 'release' option which might the right thing
* Try a different github action
see if github likes that any better
* add contents write permission
and switch to the asset upload plugin that had the helpful doc
* actually put release name in tarball path
* copy docker config to right path
* Prettify vite config
* Only activate sentry plugin if we have secrets
* Use env var for tag name
* Also spelling env correctly would likely help
* Fix variable syntax
* Put env var in correct place
One day maybe I will not find yaml syntax confusing
We only ever used the static instance() method to get to the config
object, so just make a static instance that returns the ConfigOptions
directly, throwing an exception if it's not yet initialised. This way
the types can all be non-optional (plus it's shorter).
The other options are things people usually won't need or want to
set, so just keep it to the basics.
* Rename config sample to match element-web
* Update / simplify build instructions
* Rename nginx config file to differentiate it from EC config
* We don't need to check out the js-sdk separately anymore
* Remove the vite proxying: there's no need since Matrix HSes allow
cross origin requests. This will let us move the default homeserver
config to the config file (in a separate PR...)
* Remove the product name variable which just set it to the default anyway
* load analytics id from url in embedded mode
Signed-off-by: Timo K <timok@element.io>
* add start call in the widget code path
Signed-off-by: Timo K <timok@element.io>
* send group call id instead of call name
Signed-off-by: Timo K <timok@element.io>
* generate analyticsid based on account analyticsid
This make it impossible to find users from the element web posthog instance
in the element call instance
* move registration type setup PosthogAnalytics.ts
* Order identificaition and tracking.
This fixes an issue that the widget version did not identify the user before sneding
the first track event.
Because start call is called right after app startup.
Signed-off-by: Timo K <timok@element.io>
