You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a storefront project using MedusaJS, specifically the Storefront Starter template. In this setup, we typically use the environment variable NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY to manage keys. However, I'm considering an alternative approach where a URL of the store receives a key and sets a cookie. This would allow us to work with multiple sales channels within the same code base.
I would love to hear your suggestions or experiences on how best to implement this approach. Are there any potential pitfalls or best practices I should be aware of?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone,
I'm currently working on a storefront project using MedusaJS, specifically the Storefront Starter template. In this setup, we typically use the environment variable NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY to manage keys. However, I'm considering an alternative approach where a URL of the store receives a key and sets a cookie. This would allow us to work with multiple sales channels within the same code base.
I would love to hear your suggestions or experiences on how best to implement this approach. Are there any potential pitfalls or best practices I should be aware of?
Thank you in advance for your insights!
Beta Was this translation helpful? Give feedback.
All reactions