-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installation script have selection for CosmosDB MongoDB but will not work #266
Comments
@magnuskarlssonhm |
Sorry, forgot to delete the setting cfg file. Above was with the db deleted but file in place. |
Since the install process fails due to the Mongo/Cosmos DB index issue https://docs.microsoft.com/en-us/answers/questions/258032/the-index-path-corresponding-to-the-specified-orde.html |
Asked Microsoft Azure team to extend the Cosmos DB MongoDB instance count and then it worked. It took them 3 weeks though. |
However, maybe a mapping for SQL server and regular Cosmos DB could be something? Feels a bit limited at the time. Or, my favourite apporach, separeate front and backend (CMS and Ecom) and this will work. |
Installing with CosmosDB in Azure the OrderBy clauses crashes since indexing is somewhat wrong.
At the moment Serverless CosmosDB does not work with installation script since it default to max 100containers. However, this can be scaled if talking to Microsoft Azure support. Using serverless CosmosDB is the most managed, cloud native soltion available and support for it would be very good.
To prevent complexities with asking for more than 100 containers/collections it wold be good if one could rmeove dependencies like blog etc. if one (like us) want to use it as a headless ecom with another CMS and custom checkout built on top of it.
https://grandnode.com/boards/topic/62744741289e440e8c915356/installing-with-azure-documentdb-mongodb
The text was updated successfully, but these errors were encountered: