Configure the attach debug for Quarkus in Visual Studio Code

This blog post is a short cheat sheet for:

  • How to simply organize workspaces and the debugging configuration separated from source code saved in GitHub.
  • How to simply configure attach debug for Quarkus in Visual Studio Code

The advantage with that organization is:

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.

Continue reading

How to setup a self-signed SSL certificate for a Cloud Foundry application on IBM Cloud

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.


In my example situation I want to access my Node-RED instance with a custom domain and a self-signed SSL certificate.

Normally you would create a certificate signing request to get public key certificate to encrypt the communication with https provided by a certificate authority for example “Let’s encrypt”, as you see simplified in the image below.

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.

Overview of the needed steps

Here is an overview of the major needed steps:

  1. Create a custom domain and map it with the CNAME (this will result in the fully qualified domain name)
  2. Register the created custom domain in your Cloud Foundry org and region
  3. Create a route with your custom domain for your Cloud Foundry app
  4. Create a self-signed SSL certificate for custom domain
  5. Upload the self-signed certificate to IBM Cloud
  6. Invoke URL in a browser on a machine
  7. Copy the self-signed certificate from your browser to your computer
  8. Import the self-signed SSL certificate to the keychain of your operating-system on your local machine
  9. Restart the browser and see now your communication is encrypted
Continue reading

How to setup a custom Domain for a Node-RED instance on IBM Cloud

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-RED Node.js instance in IBM Cloud and the invocation in a browser.

Cloud Foundry App InstanceNode-RED invocation in a browser
Continue reading