[build 9/9] RUN npm run ng build -- --output-path=dist --configuration=production is not working on docker container. We'll try to find a way to run it and fix it whenever we find a solution.
I refunded your credit.
I think you want to add an application instead of a microservice.
There is no automated way to add application currently. You can check the public-web application and create a new one similar to it.
Galip, biz problemimizi hallettik. Projede 'AbpPaymentStripeHttpApiModule' modulunu kullanıyorduk. 7.3.2 upgrade sonrası paketler restore olmadı. 'AbpPaymentStripeHttpApiModule' modulunu projeden kaldırdık. Restore oldu. Bu modüle bakmalısınız.
I had to dig to find the problem, yes it is related to Payment Module. The related changes are documented here: https://docs.abp.io/en/commercial/latest/migration-guides/v5_2#payment-module Saas and Payment modules are no longer coupled. But if you want to use it together please check this docs aswell: https://docs.abp.io/en/commercial/latest/migration-guides/v5_3#saas-payment-module-dependency-improvements
TLDR: Remove the Volo.Payment.Stripe.HttpApi dependency and make the related configuration to use with SaasModule:
Configure<AbpSaasPaymentOptions>(options =>
{
options.IsPaymentSupported = true;
});
We're investigating the problem.
@serdar.genc@talentra.net and @huseyinalan can you give information about from which version you are updating to v7.3.1? Or were you updating to v7.3.2?
Try adding it to the AdministrationService.Host please. SettingMagement is hosted by AdministrationService.
Hello,
Did you check both ABP Framework Migration Guide and the Commercial Migrations Guide?
If it didn't help you can create a zoom invitation to galip.erdem@volosoft.com for Thursday at 10:00 AM Toronto time.
The best way I would suggest is to use the Language Management.
An other way is overriding the TenantResource under the SaasService. You can check this post with source codes: https://community.abp.io/posts/how-to-override-localization-strings-of-depending-modules-ba1oy03l
Let us know if it works for you or not.
I have created a workaround for this problem, it should be available in the next patch.
That being said, we're planning major changes on gateway swagger UI in the future for better production environment coverage.
Did you configure ocelot for websockets? https://ocelot.readthedocs.io/en/latest/features/websockets.html
Hi,
I think you misunderstand it, there is no problem with hosting or functionality of the gateway. The current behavior is showing the api definitions of the other microservices. It is exactly the same with the microservice swagger UI. You can use the microservice itself for the swagger UI, that works fine in any environment. The problem is related to the gateway swagger UI api definitions.