Diogo Costa wrote:
Fantato wrote:
Hi Diogo,
Every resource you include into the resources folder inside a module is embedded into oml and will be publish to the deploy target when you module was published. In runtime, you will be able to replace this resource. So, you could find the new resource as you said. But inside the module you always will get the original file unless you change it inside the service studio.
If you need manage this file in runtime frequently, I suggest you create an initial bootstrap using the FIleSystems extension to put the first version of this file on runtime folder and after that only upload new version in runtime or put the resource on database keeping the latest version that should be deployed into that folder every time you need.
Hi Fantato,
What you mean with " I suggest you create an initial bootstrap using the FIleSystems extension to put the first version of this file on runtime folder and after that only upload new version in runtime ".
I don't understand what you are sayin, can you show me a example, please ?
Thanks,
Diogo Costa.
Hi Diogo,
The first point is the reason you are trying to update the js file in runtime. Who will do this update? A User with some specific role or only the developer?
If the responsible user allowed to do this updated is the developer. You only need to change the resource inside service studio. Is not necessary to create this logic to put the resource on filesystem. The platform will do it for you.
But, if you need to replace the file with any users, so you should create some screens and logic to do that. My point in the last answers was to avoid errors if this files was not there in the first deploy. So the bootstrap was required to put an initial version of this file.