Custom preview env URL + GitHub message

[mrnb (Cyril)]

Hi,

I’m trying out Qovery to see if it does fit to my company needs.

I’m setting up preview environments for our GitHub pull requests via GitHub Actions, which is working well.

Now, I would like to go further and:

---

1. Setup a custom human readable URL for these envs

Something like https://2804-staging.tesla.helpers.sh where:

• 2804 is the PR id
• staging is the parent branch of the PR
• tesla is the organization name

Is that doable? If so, how?

---

2. Customize the GH bot message

So far, the bot is posting the following message:

A preview environment was automatically created via Qovery.
Click on the link below to follow its deployment and use it.
[PR] branch - PR name - 2022-06-09T15:46:01Z

From my point of view, the core info is missing: the env link… We can access to the Qovery SaaS, login, click on the env URL. I don’t want this, I just want to see & click the preview env right away

Something like:

A preview environment was automatically created via Qovery:

2804-staging.tesla.helpers.sh

Deployment logs

Is that doable? If not, could you at least add the env URL in this message?

Best regards

[rophilogene (Romaric Philogene)]

Hi @mrnb , welcome here. Happy to see that you consider using Qovery for your company needs. I will respond inline.

@mrnb

1. Setup a custom human readable URL for these envs

Something like https://2804-staging.tesla.helpers.sh where:

• 2804 is the PR id
• staging is the parent branch of the PR
• tesla is the organization name

Is that doable? If so, how?

Today, it’s not doable but it’s something we plan to provide in a future release. cf product design → Temporary URL field

Temporarily workaround

However, I have a workaround used by some of our users to get a predictable preview env URL to set a custom domain programmatically via our API to the application. Then from that, you can set the URL of your choice with your own domain.

@mrnb

2. Customize the GH bot message

So far, the bot is posting the following message:

A preview environment was automatically created via Qovery.
Click on the link below to follow its deployment and use it.
[PR] branch - PR name - 2022-06-09T15:46:01Z

From my point of view, the core info is missing: the env link… We can access to the Qovery SaaS, login, click on the env URL. I don’t want this, I just want to see & click the preview env right away

Something like:

A preview environment was automatically created via Qovery:

2804-staging.tesla.helpers.sh

Deployment logs

Is that doable? If not, could you at least add the env URL in this message?

Best regards

It makes complete sense to me, the best would be to indicate all the public URLs (because you can have multiple apps within one preview environment) inside the comment. I can see with my team what we can do from that (I personally like your suggestion).

Side note: at some point, the preview env message would be also configurable.

cc @a_carrano @Florian_Lepont

[mrnb (Cyril)]

However, I have a workaround used by some of our users to get a predictable preview env URL to set a custom domain programmatically via our API to the application . Then from that, you can set the URL of your choice with your own domain.

=> I’m not sure to understand how it should be done via your API.
Is that different from Custom domain | Qovery ?

It makes complete sense to me, the best would be to indicate all the public URLs (because you can have multiple apps within one preview environment) inside the comment. I can see with my team what we can do from that (I personally like your suggestion).

=> Looking forward to this

Side note: at some point, the preview env message would be also configurable.

=> That would be really great.