Museum now supports configuring the URL that the clients should use for
cast, accounts (passkeys) and families portal.
Changes are in main, and also the latest published Docker image.
If you're using the old method (which was only supported by the web app,
unlike the new method which is supported by both mobile and web) of
configuring the custom environment variables, then you should instead
use the corresponding setting in the museum configuration.
```
NEXT_PUBLIC_ENTE_ACCOUNTS_URL => apps.account
NEXT_PUBLIC_ENTE_FAMILY_URL => apps.family
```
Reference: [apps block in
local.yaml](fe2771f2e0/server/configurations/local.yaml (L75-L89))
Museum now supports configuring the URL that the clients should use for cast,
accounts (passkeys) and families portal.
If you're using the old method (which was only supported by the web app, unlike
the new method which is supported by both mobile and web, and also for cast) of
configuring the custom environment variables, then you should instead use the
corresponding setting in the museum configuration:
- NEXT_PUBLIC_ENTE_ACCOUNTS_URL => apps.account
- NEXT_PUBLIC_ENTE_FAMILY_URL => apps.family
Reference: [apps block in
local.yaml](fe2771f2e0/server/configurations/local.yaml (L75-L89))
## Description
feat: update to use go1.23
---
relates to https://github.com/Homebrew/homebrew-core/pull/201919
(homebrew side always use latest go for building the artifact)
also love a new cli release for some patches so that we can proceed with
the homebrew PR
Signed-off-by: Rui Chen <rui@chenrui.dev>
The useEffect that underlay useMemoSingleThreaded shouldn't be having
any impact none of this code has an async dispatch, and all of it
already runs serially on the main thread.
The useEffect that underlay useMemoSingleThreaded shouldn't be having any impact
none of this code has an async dispatch, and all of it already runs serially on
the main thread.
