Thanks! It worked with all services started.
Thanks,
We did some progress with that information. However, for some reason auth-server did not succeed to authorize admin@abp.io with password 1q2w3E* .
I did all database migrations (administration, audit-logging, identity and saas) but no success. Not even the log in auth-server indicates some error. Any ideas?
Best rregards.
Thanks,
It seems to work. However, the migration from < 8.2 to 8.2 is not very straightforward. Think it need some more documentation, the templates that was created for ABP 7 was a much easier.
Sure, here is the structure (creating a new ms template, then using ABP Studio to generate the customer microservice).
Edit: Updated screenshot
I am not sure where to place the ABP 7 projects:
services/customer/src/GeoTicket.CustomerService.Domain, services/customer/src/GeoTicket.CustomerService.Domain, services/customer/src/GeoTicket.CustomerService.Domain.Shared, services/customer/src/GeoTicket.CustomerService.Application, services/customer/src/GeoTicket.CustomerService.Application.Contracts, services/customer/src/GeoTicket.CustomerService.HttpApi, services/customer/src/GeoTicket.CustomerService.HttpApi.Client, services/customer/src/GeoTicket.CustomerService.HttpApi.Host
in the new ABP 8.3 structure. Please help me map those projects to the new directories / projects in the screenshot.
Thanks :-)
Thank you,
But does this mean that I shouldn’t partition out Blazor code into the different microservices (as in ABP 7), but rather put all the Blazor code under apps/blazor/ProjectName.Blazor and apps/blazor/ProjectName.Blazor.Client?
Thanks,
I thought that you used the base to build inside container, and then copy that build into each app / service. But now I understand that that you build on host first.
Thanks, problem solved :-)
Sure,
I did not get the latest template (8.3.1) to work either. Same problem, no Blazor WASM.
Can you please give me the commands from installing correct ABP CLI version, to create a new template, and working Docker commands ?
Thanks, I got you and seems reasonable.
Hi,
Yes you can.
But I recommend you create a shared project
Thanks, I understand but not the reason. Can you tell me please? :-)
Ok, but why it is not possible to reference service a in service b? It is just the front-end client I mean. Bad practice or any other technical issues? In some projects I have seen only one big Blazor project, that communicate with the gateway. ABP MicroService have one top Blazor app, referencing to other Blazor project in the different services.
