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.
We have managed to get some sort of Hello World working with Blazor, but without any connection to the endpoints in our services.
Our plan was to try migrating the 7.3 project to 8.3.1, but we've had problems with it despite support.
Anyway, we don't quite understand where to place all the projects, and we would need a Hello World that includes the following:
This would be incredibly valuable. This is how we got started with ABP 6 and 7, as you had good documentation for a BookStore and tutorial, and with that knowledge from the ABP Framework, it was easy to start with microservice architecture.
I hope you can provide something like this, because we've completely lost the knowledge we had from version 7 now that we've started with 8.
Best regards.
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).
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?
We have previously used ABP 7, but now we created an ABP 8.3 microservice template, and it looked different.
Specifically, the Blazor WASM application was missing when adding a new microservice according to: https://abp.io/docs/latest/solution-templates/microservice/adding-new-microservices#adding-a-new-microservice
How do you add a Blazor project in an added microservice?
Additionally, there are two projects in the /apps/blazor directory, ProjectName.Blazor.Client and ProjectName.Blazor. How does the Blazor project in the microservice appends as dependency project in /apps/blazor (like it did in ABP 7)?
Thank you in advance for your help.
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 :-)
Hi,
I struggling to get a containerized Blazor WASM Docker container to work. I have managed to get the other things to work in Kubernetes.
However, I am not sure how to deal with the different Dockerfile.azure, Dockerfile.base and Dockerfile.local , is there any reason to not just have one Dockerfile.base and a regular Dockerfile?
Can you please give me a working example of Dockerfile.base and a Dockerfile which create a Blazor WASM container image? The generated ones from 8.2.3 only create an empty nginx container as far as I can understand.
Thanks