# Slicer custom application deployment to many computers

**URL:** https://discourse.slicer.org/t/slicer-custom-application-deployment-to-many-computers/18019
**Category:** Development
**Tags:** slicelet
**Created:** [February 11, 2021, 3:59pm UTC](https://discourse.slicer.org/t/slicer-custom-application-deployment-to-many-computers/18019 "2021-02-11T15:59:23Z")
**Posts on this page:** 1
**Showing post:** 21

<div class="post-metadata">

### Author: ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [February 19, 2021, 6:31pm UTC](https://discourse.slicer.org/t/slicer-custom-application-deployment-to-many-computers/18019/21 "2021-02-19T18:31:22Z")

</div>

> [@SlicerQR Development](https://discourse.slicer.org/t/slicerqr-development/15954/22):
>
> Question: Do any of you know my friend, Hunter Downs?

Don’t believe I do, no.

> [@lassoan](#):
>
> A very simple solution is to use files to communicate. QREADS could ask Slicer to load an image by creating a json file in a designated folder.

This could also work fine for the local environment, for about the same amount of work.

> [@SlicerQR Development](https://discourse.slicer.org/t/slicerqr-development/15954/20):
>
> Slicer reside on the QREADS server?

No, we were thinking it would still run on the client machine, but controlled by QREADS via an agreed communication protocol. Running on the server adds more trouble than it’s worth I think.

Either with the web or file based approach @spycolyf you’ll need to map out the interactions you want Slicer to be able to support and come up with a small python script to implement them.

---

_[View the full topic](https://discourse.slicer.org/t/slicer-custom-application-deployment-to-many-computers/18019)._