I was attempting to mount a folder using the webdev module. Ran through a number of post talking about mapping the network drive, having ignition run as a user with credentials, or to just "Consider assigning a real user to the gateway's service (one that has network privileges) and then use UNC paths in your scripts."
I've tried poking around a bit, and it looks like the ignition services is running on an account that has read/write access to the folder we created and mapped in ignition.conf file but nothing has worked yet. When I go to the URL of the mounted folder I get a 404 error. I had our IT department create the folder then add the necessary lines to the conf file, stop the service, then start the service.
My thought was to have the html, css, and js files in a mounted folder so I can edit them in an ide like VS code and not have to re-upload changed files. Is this kind of idea a waste of time? I would like to make a web app using precompiled bootstrap.
A solution would be cool, but also just asking for advice/counseling/guidance. Thanks!
I would place such a folder on the gateway machine, eliminating double network transfers for every access. Placing that folder under the Ignition install directory will make it automatically accessible to the unmodified Ignition service. You just need to export that folder as a share, and allow access to developers.
Thank you for the response ptrumel! I will be honest and tell you that I don't understand, "export that folder as a share, and allow access to developers" but I can run it by the IT guy.
So if I had a folder created in C:/Program Files/Inductive Automation/Ignition that should work? If I understand you correctly, from there I would be able to mount any child files or folders to my project?
Yes, though I'd probably put it under the .../data/projects/yourProject/com.inductiveautomation.webdev/ path to keep it localized. (But not under resources.)
ahh, I did see that file location while following some other bread crumbs. Would this sort of practice be scalable and sustainable? Right now I'm the only engineer messing around and trying to develop apps for ignition. We haven't set the folder up yet because I don't know how that would work out years form now when we have a few more engineers doing the stuff I'm trying to do.
We would end up creating a share in every webdev fold for every project correct?
Yes, but you may want that, so project files stay in the filesystem for git integration alongside the WebDev project jython that calls for it.
But it doesn't have to be this way. You could make just one share under /data/ and then have project folders under that. The WebDev module itself doesn't care.
Or, perhaps, make the data folder itself the share (but be careful with network security).