rubendel
commented
10 years ago - Cool
- Yes you will have to change the code to facilitate this. I can see how an option to not store the incoming files at all could be useful so I will implement that in BIMserver 1.4.
- Same as 2. Did you have a look at the documentation about the home directory? Storing it in the Tomcat directory is not really recommended. https://github.com/opensourceBIM/BIMserver/wiki/Install-on-Ubuntu#setting-the-homedir
- Same as 2
- BIMserver does this already when deserializing the IFC file. If its not a proper IFC file it will tell you before running the IFC engine and before storing any data (except maybe the incoming files directory, but that's easy to cleanup every now and then, it's mostly there for debugging anyways)
- BIMserver 1.3 does not support IFC4, BIMserver 1.4 will. BIMsurfer should work with both 1.3 and 1.4
Requirement : 1) Want to create a projects into the BIMServer per IFC file and that can goes till 10000 projects(files). 2) Want to store the incoming files on to different mount like /opt/incoming1 or opt/incoming2 than the default location /opt/tomcat/webapps/ROOT/WEB-INF/incoming/admin@bimserver.org/ [to solve the disk-space issue] 3) Want to store the database to the different mount than to its default location /opt/tomcat/webapps/ROOT/WEB-INF/database [to solve the diskspace issue] 4) Want to write a daily or weekly schedular that will hard delete the projects which are not used in last 2/3 months. [to minimise the disk space] 5) Can we prehand(before generating the geomentry) check if the given IFC file is a proper IFC file supported by the bim server so that we can avoid the geomentry generation task? 6) We have the bimsurfer implemetaion with bimserver 1.2 now we want to move to the bimserver 1.3 [IFC4 impementation] do we need to change the bimsurfer implemetation in this scenario?
To chnage the paths in step 2 and 3 do we need any configuration changes or need to change the code? For the issue mention in step 4 what kind of code needs to wrire?