tales of king arch

It has been like more than 2 years now since I started working on Meteor JS. In my early learning days in Meteor JS, I was excited to learn new things. But the biggest issue I faced at that time, was Meteor was still a new framework and its community support on its own forum was not as good as stack overflow. So when I was struggling through the Logical flow, syntaxes and many more things, I bombarded meteor forum with like 30 posts (In last 1 year). I don't know whether I was fortunate or not, but I got replies on 22 posts. Now the question was, many in Meteor community complain that Meteor forum lacks in providing support. I was also one of them. But after completing like 2 years with Meteor JS now, I have a different perspective. Now I realize the problem was never with meteor JS (Forum or community support anywhere). The problem was in me or let's say in us (developers). The forum is not a mine where you go and start digging for stuff and start getting some outpu

Working Conf {   /**    * General configuration of Orthanc    **/   // The logical name of this instance of Orthanc. This one is   // displayed in Orthanc Explorer and at the URI "/system".   "Name" : "MyOrthanc",   // Path to the directory that holds the heavyweight files (i.e. the   // raw DICOM instances). Backslashes must be either escaped by   // doubling them, or replaced by forward slashes "/".   "StorageDirectory" : "OrthancStorage",   // Path to the directory that holds the SQLite index (if unset, the   // value of StorageDirectory is used). This index could be stored on   // a RAM-drive or a SSD device for performance reasons.   "IndexDirectory" : "OrthancStorage",   // Enable the transparent compression of the DICOM instances   "StorageCompression" : false,   // Maximum size of the storage in MB (a value of "0" indicates no   // limit on the storage s