Files
web/apps/scandic-web/README.md
Joakim Jäderberg fa63b20ed0 Merged in feature/redis (pull request #1478)
Distributed cache

* cache deleteKey now uses an options object instead of a lonely argument variable fuzzy

* merge

* remove debug logs and cleanup

* cleanup

* add fault handling

* add fault handling

* add pid when logging redis client creation

* add identifier when logging redis client creation

* cleanup

* feat: add redis-api as it's own app

* feature: use http wrapper for redis

* feat: add the possibility to fallback to unstable_cache

* Add error handling if redis cache is unresponsive

* add logging for unstable_cache

* merge

* don't cache errors

* fix: metadatabase on branchdeploys

* Handle when /en/destinations throws
add ErrorBoundary

* Add sentry-logging when ErrorBoundary catches exception

* Fix error handling for distributed cache

* cleanup code

* Added Application Insights back

* Update generateApiKeys script and remove duplicate

* Merge branch 'feature/redis' of bitbucket.org:scandic-swap/web into feature/redis

* merge


Approved-by: Linus Flood
2025-03-14 07:54:21 +00:00

1.6 KiB

This is a Next.js project bootstrapped with create-next-app.

Getting Started

  • Firt, make sure you have built the design-system once:
yarn workspace @scandic-hotels/design-system build
  • Create a .env.local file in the root of the scandic-web directory with the keys from the .env.example file.

  • Then run the development server:

yarn dev

Open http://localhost:3000 with your browser to see the result.

Caching

You have the choice to either use redis (via redis-api; a tiny http proxy) or in-memory/unstable_cache (depending on edge or node). Setting REDIS_API_HOST will configure it to use the distributed cache, not providing it will fall back to in-memory/unstable_cache When pointing to the azure hosted variant you also need to provide REDIS_API_KEY

Locally it's easiest is to spin everything up using docker/podman - podman compose up or docker-compose up This will also spin up Redis Insight so that you can debug the cache.

  • Navigate to http://localhost:5540
  • Click 'Add Redis database'
  • Provide Connection URL redis://redis:6379

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!