# Projects on bluemix

**URL:** https://discourse.nodered.org/t/projects-on-bluemix/14399
**Category:** General
**Created:** [16 August 2019 15:25 UTC](https://discourse.nodered.org/t/projects-on-bluemix/14399 "2019-08-16T15:25:28Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![vittali](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vittali/32/10940_2.png) [@vittali](https://discourse.nodered.org/u/vittali)
#### Post date: [16 August 2019 15:25 UTC](https://discourse.nodered.org/t/projects-on-bluemix/14399/1 "2019-08-16T15:25:28Z")

</div>

Can projects be used when running on bluemix ?  
I have problems getting credentials to work.  
I have disabled credentials, and running locally show this:

```auto
16 Aug 15:42:18 - [debug] red/runtime/nodes/credentials.load : using active project key - disabled
16 Aug 15:42:18 - [debug] red/runtime/nodes/credentials.load : keyType=disabled

```

However, when running on bluemix, I get this:

```auto
    2019-08-16T15:37:43.59+0200 [APP/PROC/WEB/0] OUT 16 Aug 13:37:43 - [debug] red/runtime/nodes/credentials.load : no user key present
   2019-08-16T15:37:43.59+0200 [APP/PROC/WEB/0] OUT 16 Aug 13:37:43 - [debug] red/runtime/nodes/credentials.load : using default key
   2019-08-16T15:37:43.59+0200 [APP/PROC/WEB/0] OUT 16 Aug 13:37:43 - [debug] red/runtime/nodes/credentials.load : keyType=system

```

In the later case, decrypting the creds fails.

Thanks  
Peter

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [16 August 2019 15:49 UTC](https://discourse.nodered.org/t/projects-on-bluemix/14399/2 "2019-08-16T15:49:08Z")

</div>

Projects are not a good fit for using directly in the Bluemix environment.

The blog posts you have read ([Creating a Node-RED deployment pipeline to IBM Cloud · knolleary](https://knolleary.net/2018/06/01/creating-a-node-red-deployment-pipeline-to-ibm-cloud/)) explains why.

> The boilerplate is optimised for ease of use and getting started. Applications running in the Cloud Foundry part of IBM Cloud cannot treat their local file system as persistent storage - any time the application is restarted the file system is wiped back to its original state. This is why the Node-RED boilerplate comes with an instance of the Cloudant database service; giving it somewhere to store its flows.

The projects feature relies on the local file system being persistent so it can maintain a git repository there. When running in a Cloud Foundry environment, that file system will be reset whenever the application is restarted.
