Hi,
Here are some relevant explanations.
https://abp.io/docs/latest/cli/differences-between-old-and-new-cli
Thanks for that. What is the timeline on this?
December 31, 2024 you can see the milestone here https://github.com/abpframework/abp/milestone/107
Based on other posts here, I believe that we are not the only ones that are currently confused / frustrated about what CLI / templates to actually use for new projects intended for production, especially considering that ABP Studio (and the new CLI I think) is still in beta. I hope ABP will be able to address this situation better going forward as I feel that we have been stuck in a holding pattern for quite some time now.
Yes, the studio is still in the beta phase and almost stable. If you want a stable template, I still recommend you use the old CLI.
In fact, you can use the new template and copy the Docker configuration from the old template to the new template. It's a little ugly, but it works.
Hi,
and as of now, no included Docker support regardless of what ABP version you use unless you add it yourself?
No, you can use the old CLI to create the project. abp new BookStore --old
This compared to the previous CLI which had full support for Docker and Docker Compose out of the box?
I will bring the previous docker support to the new template.
Hi,
Studio focus on the Kubernetes, but Docker support is also important, we will consider add Docker compose to the template in the next version. https://abp.io/docs/latest/studio/kubernetes
Hi,
I will ask the team
Hi,
I think this is a problem of redis cluster.
As I understand, the redis cluster should be responsible for the data consistency of each node.
Will this error occur if you use the redis cluster provided by aws or azure?
Hi,
could you share some error logs and screenshots? thanks.
Hi,
I think it can't be done, It can intercept the local cluster
Do you need to deploy your app through Abp Studio for it? or can you do that with manual deployment?
yes, you need to manual deployment for now, the studio will support deployment in the future
Hi,
Of course, your ticket was refunded.
Hi,
I can't reproduce the problem
I'm closing this, free open.
