Repository navigation
Replies: 1 comment
|
I went through the GeoLens source (at 1. Publishing tables from schemas in your existing PostgreSQLNot the way Martin does it. GeoLens only catalogs PostGIS tables in its own What you can do instead:
2. Using RustFS for filesYes. Storage is S3-compatible (boto3) and configured entirely through environment variables (config.py#L403-L414): STORAGE_PROVIDER=s3
S3_ENDPOINT=http://rustfs:9000
S3_BUCKET=geolens
S3_ACCESS_KEY_ID=...
S3_SECRET_ACCESS_KEY=...
S3_ADDRESSING_STYLE=path
# S3_PUBLIC_ENDPOINT=https://files.example.org # only if browsers can't resolve "rustfs"A few details from the code:
Also, the bundled MinIO-compatible |
Uh oh!
There was an error while loading. Please reload this page.
Question
Hello,
I would like to test GeoLens, however the docker-compose plan a full stack environment with installation of a database for system and business data, an other for backup, a Minio fork for object storage...
Can it be easily adapted to use a pre-existing configuration?
My "business" data is already stored on a PostgreSQL server (18). If I understand correctly, GeoLens will create a schema ("data") intended for business data, within its own system database? Is it possible to identify schemas outside its system database in the GeoLens configuration? Following the example of Martin:
"
postgres:
connection_string: ${DATABASE_URL}
auto_publish:
tables:
from_schemas: [map, cad]
"
My image files are currently stored in RustFS. Can I use it with the variables STORAGE_PROVIDER=s3, S3_ENDPOINT=http://rustfs:9000, S3_BUCKET, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY...?
Thank you in advance for your response.
Have a good day in this project that attracts curiosity.
What I've tried
No response
GeoLens version
1.26
Deployment method
Docker Compose
All reactions