Gotcha… You’re correct to identify a few edge cases related to preserving user-level content within the gateway. Most everything is stored in
data/, but there are a few outliers. JDBC drivers, third-party modules, and custom pylib content come to mind. Generally, if you’re adding new sub-folders via additional volumes (versus inheriting existing content from the base image, such as is the case with
data/) you’ll be fine.
That said, you can also build your own custom derived image where you package in some of this custom code (that isn’t part of a traditional Ignition project/tags/etc) into the image itself. It can be as simple as a
FROM inductiveautomation/ignition:<tag> (to bring in everything else from the base image) and then a couple
COPY statements to bring your files in. Then you’d launch your container against
mcarritt1/ignition:8.1.9, for example. I should have some good examples for folks to draw inspiration from on the IA Github “soon”.