RFC 6: Directory Structure¶
| Author: | Stephan Krause |
|---|---|
| Created: | 2011-02-24 |
| Last Edit: | 2011-09-15 |
| Status: | ACCEPTED |
| Discussion: | http://www.eoxserver.org/wiki/DiscussionRfc6 |
This RFC proposes a directory structure for the EOxServer distribution as well as EOxServer instances.
Introduction¶
RFC 1: An Extensible Software Architecture for EOxServer introduces a layered architecture for EOxServer as well as a separation of EOxServer distribution and instances. This RFC lays out a directory structure that is in line with this architecture.
Directory Structure¶
Distribution¶
core: contains the modules of the Core
util: contains utility modules to be used throughout the projectservices: contains the modules of the Service Layer
ows: contains implementations of OGC Web Servicesprocessing: contains the modules of the Processing Layer
processes: contains processesresources: contains the modules of the Data Integration Layer
coverages: contains the modules related to coverage resources
formats: contains the modules related to coverage formatsvector: contains the modules related to vector data
formats: contains the modules related to vector data formatscontrib: contains (links to) third party modulesconf: contains the default configuration
Instance¶
The instance directory contains the three Django project modules:
settings.pymanage.pyurls.py
And the following subdirectories
conf: configuration files
eoxserver.conf: the central EOxServer configurationtemplate.map: template MapFile for OWS requestsdata: database files
config.sqlite: SQLite database
Voting History¶
| Motion: | To accept RFC 6 |
|---|---|
| Voting Start: | 2011-07-25 |
| Voting End: | 2011-09-15 |
| Result: | +6 for ACCEPTED |
Traceability¶
| Requirements: | N/A |
|---|---|
| Tickets: | N/A |