I had a conversation with development just to make sure I was on the same page as them and here are your options:
- Move any content you want to share publicly into a directory structure within
- Use the Web Dev module to mount your own folders of content
I’ll cover the first option because I’m more familiar with that route.
Assuming your images/svgs are in a folder structure starting with “Files” and there is an image named my_image.jpeg in the “Files” directory (such that
C:\Files\my_image.jpeg is a real file):
- Move the Files directory to
C:\Program Files\Inductive Automation\Ignition\webserver\webapps\main so that you have
C:\Program Files\Inductive Automation\Ignition\webserver\webapps\main\Files\my_image.jpeg.
- Place an Image Component in a View.
Image.props.source to “http://<gateway_ip>:<gateway_port>/Files/my_image.jpeg”.
The short story of why we don’t allow for you to just point at
C:\Files\my_image/jpeg is Security. suppose you had
C:\Personal_files\2018_tax_return.pdf on the file system… Well, if we allowed for just pointing components at any old directory, then nothing would be safe.