Activities of "improwise"

Thanks.

I see this is mentioned here

https://abp.io/docs/latest/framework/ui/angular/environment

but I think that the requirements for ABP should probably highlight more clearly that Nginx or IIS is a requirement (at least if you are using Angular). I believe that the problem here might be that for various reasons, we are running the Angular app from a Web App (linux) using node stack, which AFAIK uses Nginx to run the container, but not actually serve the content files. Because of this, we are using the startup command

pm2 serve /home/site/wwwroot --no-daemon --spa

Which probably does not work with remoteEnv out of the box.

What we did now was to change the environment.prod.ts to this instead as the dynamic-env.json file in wwwroot

remoteEnv: { url: '/dynamic-env.json', mergeStrategy: 'deepmerge' }

Which at least seem to not cause any problems even though the dynamic-env file is being served, but we have not really looked into it more in detail except that verifying that we are not getting this error message.

Not sure what potentia drawbacks this may have though?

The requirements should probably be updated as well to indicate that IIS or Nginx is needed (at least for it to work out of the box) if this isn't listed.

Thanks.

[maliming] said: hi

You can create a new mvc template project and copy the _Footer.cshtml to your project with the same folder structure and customize it.

Thanks

Not sure why we would need/want to create an MVC project?

Please just at least make it default that the footer is empty so that those projects that actually want to have a footer like this can then do this rather than every project not wanting to have a Copyright Volosoft need to remove it. Thanks.

Thank you, that additional info in the logs will be good to have. Can confirm that the error seem to go away once we commented out this in environment.prod.ts

/* remoteEnv: { url: '/getEnvConfig', mergeStrategy: 'deepmerge' }*/

That said, I still would like to know what is actually wrong here and how to get it working. Disabling functionality seems like a workaround that isn't really a solution to the problem, and increased logging of the error probably won't solve it either.

[maliming] said: hi

We will show some in the console if this endpoint is wrong.

Thanks.

Hi,

Is this something that will be changed in the future as at least we didn't see anything in console?

Also, how com this isn't working as we have not changed the URLs or paths as I know and they should be relative to the baseURLwhich seem to be working?

Thanks, will look into that. But how come this isn't, at least what we have found, more clearly logged/indicated?

Thanks

Can we PLEASE fix this damn service bot closing unresolved tickets?

Actually, I thought so to but turns out they properties are actually included all the way, at least with the Angular UI we are using. All you need to do is to fix the last step to actually have them show up. This is at least true for the list (GetList), have not looked if they are included for Get(xxx) as well.

    <ngx-datatable-column name="{{ '::CreationTime' | abpLocalization }}" prop="measurementAssignment.creationTime" >
      <ng-template let-row="row" ngx-datatable-cell-template>
        {{ row.xxx?.creationTime | shortDateTime }}
      </ng-template>
    </ngx-datatable-column>

Update, seems like this properties are actually included so what would be needed is more an option i ABP Suite to actually control if they are shown etc.

Perhaps some middle ground would be to include the most frequently used base properties in DTOs etc but not render them automatically in UI etc.

Could you implement this using the Extended classes etc so that even if you have to do it manually, they would still survive regenerations in ABP suite etc?

All this can of course be solved today, just as you could manually do anything ABP Suite does, but the goal here is of course not having to unless you want something more specific than to include some base properties.

Needs a human