# Workflow ideas for moving app from developer sandbox to general roster

**URL:** <https://discourse.openondemand.org/t/workflow-ideas-for-moving-app-from-developer-sandbox-to-general-roster/4754>\
**Category:** Get Help\
**Tags:** question\
**Created:** [February 12, 2026, 3:55pm UTC](https://discourse.openondemand.org/t/workflow-ideas-for-moving-app-from-developer-sandbox-to-general-roster/4754 "2026-02-12T15:55:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![omar.valerio](https://avatars.discourse-cdn.com/v4/letter/o/df705f/32.png) [@omar.valerio](https://discourse.openondemand.org/u/omar.valerio)\
**Post date:** [February 12, 2026, 3:55pm UTC](https://discourse.openondemand.org/t/workflow-ideas-for-moving-app-from-developer-sandbox-to-general-roster/4754/1 "2026-02-12T15:55:59Z")

</div>

Dear OOD Team,

Congrats for the new release. Looking forward to try it out. I’m posting today with a request for help. I will explain.

At our institute I have become the self-appointed OOD Ambassador. 🙂

As part of my now self-inflicted duties, I’m trying to establish a workflow that I can use to deploy and test my own OOD apps, moving them from the developer sandbox into general use.

I use source control to develop the OOD apps. Therefore, for me the most natural thing is to `git pull` to the `/var/www/ood/apps/sys/%MY_OOD_APP%` once I’m ready to test.

What I’m currently doing is to `git clone` the app directory into the `/var/www/ood/apps/sys` directory. Then I ask the OOD admin in our institute to run a series of commands that will allow me to do a `git pull` on that directory, while relinquishing the ownership of the folder and keeping write access to the directory using the group membership.

`sudo chown -R root:ood-dev /var/www/ood/apps/sys/my-ood-app`  
`sudo chmod -R g+w /var/www/ood/apps/sys/my-ood-app`  
`sudo find /var/www/ood/apps/sys/my-ood-app -type d -exec chmod g+s {} ;`  
`sudo -u valerio git -C /var/www/ood/apps/sys/my-ood-app config core.sharedRepository group`

Please let me know if you see any issues with this approach. Also happy to hear how other OOD developers reduce this flow friction.

Thanks & regards,  
~ Omar

---

<div class="post-metadata">

**Author:** ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)\
**Post date:** [February 12, 2026, 5:29pm UTC](https://discourse.openondemand.org/t/workflow-ideas-for-moving-app-from-developer-sandbox-to-general-roster/4754/2 "2026-02-12T17:29:54Z")

</div>

Hi and welcome!

I would say automation could help you here. Both ansible and puppet support installing specific app versions. Ansible through `git` as you’ve set this up here and I believe puppet through packages (like .deb or .rpm).

In that way - you could just publish a new version, have your administrator run the automation with the version update and have it all handled by computers. In this way you’re less error prone to human mistakes typing things out in the configuration lines and what’s more you don’t need special permissions here and there. They can all continue continue to be root owned and managed exclusively by your administrator.

In any case - that’s just my 2 cents. Automation really pays off long term.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/b/bae70bd0ed39a3ae769c2108155f4cb3e9da8385.png) [@system](https://discourse.openondemand.org/u/system)\
**Post date:** [August 11, 2026, 5:29pm UTC](https://discourse.openondemand.org/t/workflow-ideas-for-moving-app-from-developer-sandbox-to-general-roster/4754/3 "2026-08-11T17:29:55Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.