# SlicerQR Development

**URL:** <https://discourse.slicer.org/t/slicerqr-development/15954>\
**Category:** Development\
**Tags:** registration, build, segmentation, dicom, python\
**Created:** [February 11, 2021, 3:59pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954 "2021-02-11T15:59:22Z")\
**Posts on this page:** 1\
**Showing post:** 168

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [June 8, 2021, 5:52pm UTC](https://discourse.slicer.org/t/slicerqr-development/15954/168 "2021-06-08T17:52:01Z")

</div>

Done. The new topic is here:

> [@Slicer custom application deployment to many computers](https://discourse.slicer.org/t/slicer-custom-application-deployment-to-many-computers/18019):
>
> @jcfr @pieper @lassoan @superlib Good Morning. I’m starting to think about how to deploy SlicerQR to 25,000 PCs across the Mayo Enterprise. After building the package, it consists of over 7000 files at a total size of over 700MB. It would be seriously frowned-upon to propose deploying it to 25,000 PCs. So, my question is: Would there be any disadvantages to placing the installation in 1 place on a file share and have the users execute SlicerQR from a folder there? Would there be conflicts with …

---

_[View the full topic](https://discourse.slicer.org/t/slicerqr-development/15954)._
