EOxServer
EOxServer is a Python application and library for presenting Earth Observation (EO) data and metadata.
EOxServer implements the OGC Implementation Specifications EO-WCS and EO-WMS on top of MapServer's WCS and WMS implementations. EOxServer is released under the EOxServer Open License an MIT-style license and written in python and entirely based on open source software including:
More information is available at https://eoxserver.org. Documentation is available at readthedocs
Docker
To run with SpatiaLite database simply run:
docker run -it --rm -p 8080:8000 eoxa/eoxserver
EOxServer is now accessible at http://localhost:8080/.
And you can login to the Admin Client using:
- username: admin
- password: admin
The following environment variables control configuration:
DB: Specify the used database type. eitherspatialiteorpostgisDB_PW,DB_NAME,DB_HOST,DB_USER: these credentials will be used to establish a connection to the postgres database when DB is set topostgisin order to wait for it to come onlineINSTANCE_NAME: the name of the instance passed toeoxserver-instance.py- defaults toinstanceINSTANCE_DIR: the directory of the instance. Defaults to/opt/instanceDJANGO_USER,DJANGO_MAIL,DJANGO_PASSWORD: when set, these credentials will be used to create a superuser to be used for the Django Admin. By default, no user is createdCOLLECT_STATIC: if set to "true" (the default), static files will be collected upon initializationPREINIT_SCRIPTS: the list of commands that will be executed before the instance is initializedINIT_SCRIPTS: the list of commands that will be executed once when the instance is initializedSTARTUP_SCRIPTS: the list of commands that will be executed before the command is runGUNICORN_CMD_ARGS: gunicorn command arguments. Defaults to--config /opt/eoxserver/gunicorn.conf.py ${INSTANCE_NAME}.wsgi:application
Development
The autotest instance can be used for development and testing.
More information in ./autotest/README.md
3 maintainers
Metadata
3 maintainers
Release files for EOxServer 1.5.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| eoxserver-1.5.5.tar.gz | 3.4 MB | Without provenance | Details for eoxserver-1.5.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| eoxserver-1.5.5-py3-none-any.whl | Python 3 | none | any | Details for eoxserver-1.5.5-py3-none-any.whl |
Total release size: 7.1 MB
Release files / eoxserver-1.5.5.tar.gz
| Download URL | eoxserver-1.5.5.tar.gz |
|---|---|
| Size | 3.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46da317ac9284b47c4d5cda8e55115aa67e0ef7a6e1948cae607f6e1e5af8493
|
|
BLAKE2b-256 checksum How to use checksums |
c162800bc80b4da1ee1130dbf57948e695767c306b364ec0391fe4ebbf3238df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / eoxserver-1.5.5-py3-none-any.whl
| Download URL | eoxserver-1.5.5-py3-none-any.whl |
|---|---|
| Size | 3.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7aee1448927b4d771361d8fa169bd581461cf0c2ade83b855d37bee642f7027c
|
|
BLAKE2b-256 checksum How to use checksums |
07082befe268157be7a1c89a89915f41ca9eb040cf5a3bafb9a5a03b15797dc0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for EOxServer 1.5.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
