Activities of "improwise"

Besides the previous errors we have reported with regard to the included Expo template, I don't think this will work either for Expo Web as that would require a normal URL instead of a deep link (protocol handler)

  "AbpSolution4_Mobile": {
    "ClientId": "AbpSolution4_Mobile",
    "RootUrl": "exp://localhost:19000"
    

[maliming] said: hi

We have changed this behavior so that, even without IIS or Nginx, it will no longer show errors.

Thanks.

Thanks.

Please also consider if there is a need to update docs to highlight this (requirements for getting dynamic envs to work) and also considering this ticket as it seem to have been valid for a needed fix. Thanks.

[maliming] said: hi

Every template project will include a footer component. You can change it in MVC. blazor and angular.

Thanks.

Is this something that will be introduced as at least in our :NET + Angular we don't seem to have this, even though I assume we could create a new MVC project, take that footer.cshtml and move it into the existing structure.

[maliming] said: hi

We provide the _Footer.cshtml file instead of an empty file in the template, allowing the customer to change it more easily.

Thanks.

But this template assumes that you are using MVC from what I understand, if not, things get more complicated just to remove a Copyright notice which, at least according to me, never should have been there to begin with (even though the option to enable it if needed would be nice).

Thanks.

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?