# Rancher catalog

**URL:** <https://forums.suse.com/t/rancher-catalog/1096>\
**Category:** Rancher 1.x\
**Created:** [November 26, 2015, 10:18pm UTC](https://forums.suse.com/t/rancher-catalog/1096 "2015-11-26T22:18:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![thbeh](https://avatars.discourse-cdn.com/v4/letter/t/e0b2c6/32.png) [@thbeh](https://forums.suse.com/u/thbeh)\
**Post date:** [November 26, 2015, 10:18pm UTC](https://forums.suse.com/t/rancher-catalog/1096/1 "2015-11-26T22:18:43Z")

</div>

Can I build my own service in catalog? If so, are there any guides on this?

---

<div class="post-metadata">

**Author:** ![antmanler](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/antmanler/32/365_2.png) [@antmanler](https://forums.suse.com/u/antmanler)\
**Post date:** [November 27, 2015, 1:07am UTC](https://forums.suse.com/t/rancher-catalog/1096/2 "2015-11-27T01:07:04Z")

</div>

> <https://github.com/rancher/rancher/issues/2672>
>
> Currently one need to update the API via a POST request to change the location o…f the rancher-catalog repo location. While it works fine, it would be good to have the feature enabled via UI screen. Also, it would be a great feature to set catalog per environment...for example, it our use case, we would like to create an environment for different product groups and have each product group have their own catalog. It could be a scenario like Catalog items marked as generally available to all + items limited to a product group/environment. By default all environments would inherit default catalog but admin could change that to specific repo...

> Configuring the catalog URL(s) in the UI for admins will probably ship with that. (Side note: you can go to the API and change the setting with just a browser, you don’t actually need API keys and curl or similar… User menu → API & Keys → click Endpoint link and then navigate to /v1/settings/catalog.url and click the blue Edit button)  
> Access controls for different catalog items for different people/environments is not in the immediate roadmap. The catalog service runs as a separate API that has no information about what user or environment the request is for.