Open shams265 opened 1 year ago
Also after dropping the Cmdbuild database by using above script, and changing the value of CMDBUILD_DUMP=empty.dump.xz, openmait loads up with empty but if we do any changes, saved them and recreate the containers, all saved data is deleted and an empty container is generated again. I want to persist my db data on the hard drive instead of volumes so that if the container is re-created in any case, the data should be safe.
I'll ask a college he knows how to solve this.
I've tried on 2 different machines the docker compose with demo and with empty and both load well but any new input i get this generic error. my guess it can't write to db...
Hi, I am trying to use openmaint and successfully executed the docker-compose file located in openmaint-2.0-3.2.1 directory. The demo data is launched successfully, but when i try to drop the demo data using the command given below and change the CMDBUILD_DUMP=my_db and relaunch the container as guided here (https://github.com/itmicus/cmdbuild_docker#how-drop-cmdbuild-database) After relaunching the container, i get a screen with lot of patches on it and when i press the patch button, it simply gives a generic error and get stuck on that screen like this Any help regarding how to link a new db after dumping the demo would be highly appreciated.