Saved connections¶
Save the connection once, then reuse it.
Examples:
- Production PostGIS
- Production GeoServer
- Field Data S3
You do not save the whole workflow here. You save how to reach the system. The table name, object key, layer, or project still belongs to each run or Job.
Why they exist¶
Without a saved connection you would retype host, bucket, and password every time.
With a saved connection:
- Save Production PostGIS.
- In any workflow, pick it as the Destination.
- Enter only this run's schema and table.
One connection can feed many Jobs.
Sources you can save¶
| Type | What is saved | Chosen per workflow |
|---|---|---|
| URL | The URL | Import when you use it |
| FeatureServer | Service URL | Layer |
| S3 | Endpoint, bucket, keys | Object key |
| QFieldCloud | Server and login | Project and GeoPackage |
| Mergin Maps | Server and login | Project and GeoPackage |
Upload cannot be saved.
Destinations you can save¶
| Type | What is saved | Chosen per workflow |
|---|---|---|
| PostGIS | Database login | Schema, table, write mode |
| S3 | Bucket and keys | Object key, overwrite |
| SFTP | Host and login | Remote path, overwrite |
| GeoServer | Server and login | Workspace, store, layer |
| GeoNode | Server and login | Title, name, permissions |
Download cannot be saved.
Credentials¶
Passwords, keys, and tokens are stored securely on the server. They are not shown back in full after save. Test checks that GeoJibe can reach the system without delivering data.
You need to be signed in to create or use saved connections.
Manage¶
Open Sources or Destinations in the sidebar.
- Add Source / Add Destination
- Edit, Test, Save
- Delete — blocked if a Job still uses that connection
Manage Sources and Manage Destinations from Canvas Properties open the same lists.