What needs to happen?
The documentation already explains how settings such as HOP_CONFIG_FOLDER, HOP_SHARED_JDBC_FOLDERS, project folders and additional plugins can be kept outside the Hop installation.
For Hop Web/Docker, could the documentation clarify the recommended upgrade procedure, especially:
which folders/files should be preserved across upgrades;
which should always come from the new image;
how additional JDBC drivers and plugins should be handled;
what volume mounts are recommended for an upgrade-friendly deployment.
A small Docker Compose example would be very helpful.
Issue Priority
Priority: 3
Issue Component
Component: Documentation
What needs to happen?
The documentation already explains how settings such as HOP_CONFIG_FOLDER, HOP_SHARED_JDBC_FOLDERS, project folders and additional plugins can be kept outside the Hop installation.
For Hop Web/Docker, could the documentation clarify the recommended upgrade procedure, especially:
which folders/files should be preserved across upgrades;
which should always come from the new image;
how additional JDBC drivers and plugins should be handled;
what volume mounts are recommended for an upgrade-friendly deployment.
A small Docker Compose example would be very helpful.
Issue Priority
Priority: 3
Issue Component
Component: Documentation