Activities of "improwise"

It seem like the new CLI when using --old does not work if you have a Windows username with a space in it (Firstname Lastname). The actual old CLI as well as the new CLI without the --old does not seem to have this problem. Is there a way to make it work?

\src>abp new BookStore --old [10:36:38 ERR] 'C:\Users\Firstname' is not recognized as an internal or external command, [10:36:38 ERR] operable program or batch file.

(And yes, I am well aware of the fact that Windows in general have limitations with usernames with a space in it even in 2024).

Thanks for responding.

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

I am not seeing anything Docker related on that page though?

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.

Have read the page above a few times by now, and together with what is communicated in forums etc. I don't really see the message "if you want to build for production, use the old CLI" coming across clearly, especially the "so if I use the old CLI, what will happen when that is dropped in the near future?" question. Now, don't get me wrong, I understand the challenge of making this transition from old to new and the reasons for it, at the same time, it also creates some challenges for us customers going forward with new projects.

This is probably beyond the scope of this thread though, but I would recommend that ABP looks into improving the communication and recommendations about this as I get the feeling that we are not the only one feeling a bit of discomfort at the moment going forward because of this. Then of course there is .NET Aspire on the horizon as well.

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

AFAIK, ABPs recommendation is not to use the old CLI any more though and based on this thread https://abp.io/support/questions/7625/React-Native--Expo-migration?CurrentPage=2, old CLI / templates will not have support for React Native etc going forward?

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.

Thanks for that. What is the timeline on this?

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.

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

Thanks for answering.

Just to make sure we understand this correctly, going forward, there is basically no container support in ABP unless you have a business or enterprise license, and as of now, no included Docker support regardless of what ABP version you use unless you add it yourself?

This compared to the previous CLI which had full support for Docker and Docker Compose out of the box?

Hi,

Still waiting for an update on this or a confirmation that Docker support has been dropped from the new CLI (templates) as the current support for Docker using the new CLI is very basic compared to the one in the old CLI, and also no support at all for Docker compose etc.

Hi all, it seems like ya are not read my comment well, I'll migrate to 51 but if you guys read the migration guid react expo recommend to update version incrementally. I'll migrate today to 51

https://reactnative.dev/docs/upgrading#expo-projects

Thanks,
Masum

Thanks for the clarification.

And it will be TypeScript as well then going forward?

@masum.ulu

Can you please confirm that Typescript will be used rather than Javascript going forward? Thanks

Hi again, I was working on this and other problems too, we'll release this enhancement for new template (Volo.Abp.Studio.Cli) we deprecated (Volo.Abp.Cli) dotnet tool's template. Development stage is done. Now it's on test stage. We'll release ASAP.

Can you please clarify what you (ABP) mean with the Volo.Abp.Cli being deprecated? AFAIK know, that is still the only template that has Docker support etc.

What is the status on this? ABP seem to have dropped support for Docker almost completely with the new CLI.

Pre-requirement check fails with 0.9.4

18:22:46.338 Information Failed task execution: "Checking pre-requirements" 18:22:46.338 Information ERROR: "An error has occured!" 18:22:46.338 Information ERROR DETAILS: "An internal error occurred during your request!" 18:22:46.339 Error Requested registry access is not allowed.

I am still unable to replicate the issue on my end.

See separate post above