# Customising job composer

**URL:** <https://discourse.openondemand.org/t/customising-job-composer/1982>\
**Category:** Get Help\
**Created:** [March 25, 2022, 8:44am UTC](https://discourse.openondemand.org/t/customising-job-composer/1982 "2022-03-25T08:44:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stdweird](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/stdweird/32/627_2.png) [@stdweird](https://discourse.openondemand.org/u/stdweird)\
**Post date:** [March 25, 2022, 8:44am UTC](https://discourse.openondemand.org/t/customising-job-composer/1982/1 "2022-03-25T08:44:37Z")

</div>

Hi all,

we are running ondemand 2.0 and have been focusing on interactive apps up until now.  
we did quite some customisations to deal with our not-so-standard cluster setups, and also to the way eg resources are requested.

however, it looks at first sight that the job composer is a different thing altogether wrt the way the app is managed/configured.

it’s slightly worse that it is also bundled as part of ondemand, and not as a separate app; so no easy fork and hacking.

i also found an older post [Job Composer Additional Fields](https://discourse.openondemand.org/t/job-composer-additional-fields/50), not sure if it is still relevant

any feedback is welcome,

stijn

---

<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:** [March 25, 2022, 1:49pm UTC](https://discourse.openondemand.org/t/customising-job-composer/1982/2 "2022-03-25T13:49:08Z")

</div>

Yea we’re working on a replacement for that app - looking to ship an alpha in 2.1. That discourse topic is very relevant indeed.

> <https://github.com/OSC/ondemand/issues/1245>
>
> This is an epic ticket for the alpha version of the new job composer. Sub ticke…ts could link to it for reference, but this comment should also include a running list of features we'd want to implement.
> 
> See this project https://github.com/OSC/ondemand/projects/6 for more details on the progress of this epic.
> 
> \* \[x\] #1773 
> \* \[x\] #1770
> \* \[x\] #1592
> \* \[\] #1790
> \* \[\] #1860
> \* \[\] #1861
> \* \[\] WYSIWYG type editor. Similar to how batch connect apps, users should be able to create forms, submit configs and maybe even template shell scripts. Basically everything a batch connect app is without the interactive sessions cards
> \* \[\] Support multiple paths. Lots of sites specific HOME or other NFS directories that are cluster specific. We need to support this case.
> 
> 
> 
> ┆Issue is synchronized with this \[Asana task\](https://app.asana.com/0/1201735133575781/1201737422342975) by \[Unito\](https://www.unito.io)

If you did want to fork the current job composer you could just `cp -r apps/myjobs ~/ondemand/dev/my-new-jobs` to copy the files to their own directory and start from that. Disable the old job composer and enable you’re new one so folks don’t get confused.

Hope that helps!

---

<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:** [September 21, 2022, 1:49pm UTC](https://discourse.openondemand.org/t/customising-job-composer/1982/3 "2022-09-21T13:49:49Z")

</div>

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