You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pallets and their data would be copied to the servers they are aware of.
arcgis_servers: []
To make it backwards compatible with existing pallets, we can add a property to the servers array that will be used if the pallet does not describe an arcgis_servers property.
copyAlways: true
This would allow forklift to manage multiple disparate arcgis servers with different configurations.
For instance, forklift could manage the data on the geocoding server, the wri server, and other managed servers that are not mapserv.
👍 if you agree or comment to modify
The text was updated successfully, but these errors were encountered:
It would make sense to put it on the servers config options but if you aren't using servers and are only moving data around that would fail. I suppose shipTo could be a default and it could be overridden in the pallet.
Pallets and their data would be copied to the servers they are aware of.
arcgis_servers: []
To make it backwards compatible with existing pallets, we can add a property to the servers array that will be used if the pallet does not describe an
arcgis_servers
property.copyAlways: true
This would allow forklift to manage multiple disparate arcgis servers with different configurations.
For instance, forklift could manage the data on the geocoding server, the wri server, and other managed servers that are not mapserv.
👍 if you agree or comment to modify
The text was updated successfully, but these errors were encountered: