"cfd000" की गतिविधियाँ

To clarify, do you want to deploy all your applications (Http.Api.Host, Web and IdentityServer) to same domain with sub folders? Web is running on: mydomain Http.Api.Host on: mydomain.com/api IdentityServer on: mydomain.com/account

If so, you will need to write Rewrite rule in load balancer (nginx i suppose) to redirect to /account

You can check deployment configurations docs. Also official identityserver4 deployment docs.

If you have already deployed identityserver, you can also share its link.

Correct. I have the rules configured and working, but the interactions aren't correct.

For RemoteServices__Default__BaseUrl I am using the internal name of the HTTP-API service. For AuthServer__Authority I cannot use the internal name because the redirect to the login page does not work externally. When I put the FQDN of the Identity-Server (with /Account at the end), and click the Login button, I am redirected to my url.com/?handler=Login which does not load.

1. Should the Identity server external URL be configured for AuthServer__Authority?
2. How do I get the Login button to redirect to url.com/Account/Login (or, is there another way to get that redirection to work properly behind the load balancer?)

The best practice is creating your folder structure same as ABP is,

• YourCompany's Project folder
• • abp contains abp github repository
• • abp-pro contains abp-pro modules
• • • naming the pro modules with same as abp (attached img) When using --local-framework-ref --abp-path target --abp-path to abp
      After this you need just few minutes of manual working Replace all \abp\abp\ with \abp-pro\

Thanks for the suggestions. I was able to come up with a script that got it all working (prior to seeing your posts). My folder structure put "abp" in the same directory as the pro modules (basically those folders all all moved up 1 level from where you put them), and I was able to replace SuiteTemplate with a reference in the same way as "Commercial.Core".

Any idea if that matters? Everything seems to be compiling, the only problem I have now is the CLI project creation with local references creates a project that will also need some references "fixed".

The challenge we have is that we are trying to debug core framework functionality, and our solution built using ABP Suite is not allowing that to happen. We switched to building the solution using the CLI, which does allow the breakpoints to be hit, but requires a HUGE amount of manual editing of dozens of project files just to get a successful compile.

One of the huge benefits of paying for ABP Commercial was access to the full source code. Without the ability to easily debug at every level (our projects, the ABP Pro/Commercial modules, and the base open source ABP framework) we are not getting the benefits we were promised.

This is a bug in the ABP get-source function.

If it is not possible to get the source for a given module, the resulting project files should reference the package. The resulting output is non-functional without manually editing 89 broken project references.