SphereServer BugTracker - SphereServer |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002024 | SphereServer | new feature request | public | 01-09-11 19:25 | 16-09-11 22:47 |
|
| Reporter | wuffel | |
| Assigned To | | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | |
| Platform | | OS | | OS Version | |
| Product Version | 20-09-2009, 0.56b Prerelease | |
| Target Version | | Fixed in Version | | |
| Nightly Version | Not Available |
| Experimental Flags | None |
| Option Flags | None |
| Internal Build Number | |
|
| Summary | 0002024: Output path of serv.export / extract |
| Description | - Line in Sphere.ini to define a output-path for serv.export / extract
|
| Steps To Reproduce | |
| Additional Information | Actually i solve this with a chron-job - but maybe it isnt the highest effort to make it dynamic. in the moment state every extract/export is placed in the spheresrv-folder. |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 01-09-11 19:25 | wuffel | New Issue | |
| 15-09-11 01:16 | MrSugarCube | Note Added: 0001263 | |
| 15-09-11 16:17 | wuffel | Note Added: 0001269 | |
| 16-09-11 22:47 | MrSugarCube | Status | new => closed |
| 16-09-11 22:47 | MrSugarCube | Resolution | open => no change required |