-
Notifications
You must be signed in to change notification settings - Fork 41
Roadmap to an external Database
OllisGit edited this page Aug 26, 2020
·
7 revisions
The following tasks describe the way which is needed to use external databases
-
Move Snapshot and Images from filesystem to database storage
- Implement local image cache
-
Implement Database-Settings dialog
- Copy printjob-data from one database to an other database
- Fix ResetSettingsUtils.js to support nested properties
-
Modify database model to collect OP-Instance Id/Key/Name
- Implement renaming function
-
Handle concurrent user modifications
- Add version columns and implement "OptimisticLockException", last user wins!
-
UI: Select-Option to select different OP-Instances in Filter-View
-
Upgrade mechanism
- On startup: check which database scheme is used in external DB. Ask user what to do, show him the 'Alter-Script' -> disable Plugin if not matched! All OP-Server needs to be used the same DB Scheme Version
-
Support of mySql (starting with postgres)
-
Thing about usage of an external "filesystem" for sqlite-file (DropBox, G-Drive)
- Handling AuthN/AuthZ
- activate write mode
- ...
Use the docker-compose.yml
in the root master branch.
Execute docker-compose up
to start the database
Connection settings:
host = localhost
port = 5432
database name = printjobhistory_database
user = Olli
password = illO