You can easily delete the source code saved in GitHub from your local machine, but you don’t lose the debugging or other configurations you did.
In case that you will work again on the source code of the deleted GitHub project, you don’t need to setup these configurations again, because you can just add/link cloned GitHub source code project once more to your Visual Studio Code workspace project, which is still on your local machine.
This blog post is about, how to setup a self-signed SSL certificate for an encrypted (https) communication with a Cloud Foundry application on IBM Cloud, if you are at a Hackathon. Keep in mind you don’t need to implement additional code inside of your Cloud Foundry application in this scenario. All is managed by IBM Cloud and you don’t need to modify your source-code. You need to have installed OpenSSL on your local machine and this example shows the setup on MacOS and Safari. You also need a Pay-As-You-Go or Trial-Account for the IBM Cloud to setup custom domain and ssl.
A certificate from a certificate authority can be costly, if you aren’t able to use a free certificate authority like for example “Let’s encrypt” supported by your domain provider. In my case the domain provider GoDaddy doesn’t support to request certificates directly from “Let’s encrypt”.
One easy solution to avoid additional costs is to create a self-signed certificate. This solution works well, if you only want to test and develop during a Hackathon and you have a very small count of users and you can give them the guidance to use the self-signed SSL certificate in their browser. As you can see you need to upload self-signed SSL certificate in this simplified picture.
This blog post is a short cheat sheet, how easy it is to configure/setup a custom domain for a Node-RED example instance on IBM Cloud for a Cloud Foundry App. To do this you need a Pay-As-You-Go or Trial-Account for the IBM Cloud.
The image below shows my Node-REDNode.js instance in IBM Cloud and the invocation in a browser.