Insert/Copy curl of request #3615

Closed
opened 2026-02-28 03:35:30 -05:00 by deekerman · 9 comments
Owner

Originally created by @unuchak on GitHub (Sep 18, 2024).

no

🏷️ Feature Request Type

New monitor, Change to existing monitor

🔖 Feature description

Add possibility to insert new monitor as curl and add possibility to copy curl of request.

✔️ Solution

Add possibility to insert new monitor as curl and add possibility to copy curl of request.

Alternatives

No response

📝 Additional Context

No response

Originally created by @unuchak on GitHub (Sep 18, 2024). ### 📑 I have found these related issues/pull requests no ### 🏷️ Feature Request Type New monitor, Change to existing monitor ### 🔖 Feature description Add possibility to insert new monitor as curl and add possibility to copy curl of request. ### ✔️ Solution Add possibility to insert new monitor as curl and add possibility to copy curl of request. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
Author
Owner

@CommanderStorm commented on GitHub (Sep 22, 2024):

Inserting as curl is fairly difficult given the plethora of protocols/crypto-backends/.. that curl supports.
Partial support via parsing of the command would create a different can of worms. I don't think we should touch this at the moment.

Copying the command (and generally better debugging functionality) is something that I would love to see a PR on. => Marking as a good first issue because I think this should be fairly straightforward. I think a good basis would be a debug button next to the safe button which opens a modal (to have a place to put explainaining text) with a copyable text field with the curl command. No backend changes should be nessesary

@CommanderStorm commented on GitHub (Sep 22, 2024): Inserting as curl is fairly difficult given the plethora of protocols/crypto-backends/.. that curl supports. Partial support via parsing of the command would create a different can of worms. I don't think we should touch this at the moment. Copying the command (and generally better debugging functionality) is something that I would love to see a PR on. => Marking as a good first issue because I think this should be fairly straightforward. I think a good basis would be a `debug` button next to the safe button which opens a modal (to have a place to put explainaining text) with a copyable text field with the curl command. No backend changes should be nessesary
Author
Owner

@nekojanai commented on GitHub (Sep 23, 2024):

I would like to take this on if possible

  I think a good basis would be a debug button next to the safe button which opens a modal (to have a 
  place to put explainaining text) with a copyable text field with the curl command. No backend 
  changes should be nessesary

I would implement it exactly as described above.
src/components/Confirm.vue
seems to already use some form of modal I would take the template from there and adjust it for this use case.

For DNS I would use something like dig instead since you have to build curl with this capability specifically enabled to make dns requests (I didn't even know curl could do that)

I guess this request only pertains to http requests only?

@nekojanai commented on GitHub (Sep 23, 2024): I would like to take this on if possible ``` I think a good basis would be a debug button next to the safe button which opens a modal (to have a place to put explainaining text) with a copyable text field with the curl command. No backend changes should be nessesary ``` I would implement it exactly as described above. `src/components/Confirm.vue` seems to already use some form of modal I would take the template from there and adjust it for this use case. For DNS I would use something like `dig` instead since you have to build curl with this capability specifically enabled to make dns requests (I didn't even know curl could do that) I guess this request only pertains to http requests only?
Author
Owner

@CommanderStorm commented on GitHub (Sep 24, 2024):

I would implement it exactly as described above.

Thanks, much appreciated. The template to go from seems like a good bet ^^

For DNS I would use something like dig instead

Yea, that would make sense. Have not thought about this.
If you have time for that, that would be awsome (if not, someone else can do this in another PR => loadsharing is a superpower of open source)

@CommanderStorm commented on GitHub (Sep 24, 2024): > I would implement it exactly as described above. Thanks, much appreciated. The template to go from seems like a good bet ^^ > For DNS I would use something like `dig` instead Yea, that would make sense. Have not thought about this. If you have time for that, that would be awsome (if not, someone else can do this in another PR => loadsharing is a superpower of open source)
Author
Owner

@CommanderStorm commented on GitHub (Sep 24, 2024):

Our contribution guide (includes how to setup a dev environment) is here. Feel free to ping me if there is anything unclear (being unclear in the docs is a bug too) or you have other questions 😉

@CommanderStorm commented on GitHub (Sep 24, 2024): Our contribution guide (includes how to setup a dev environment) is [here](https://github.com/louislam/uptime-kuma/blob/b287a25de735d14c6e078d57e99b4587f10697cd/CONTRIBUTING.md). Feel free to ping me if there is anything unclear (being unclear in the docs is a bug too) or you have other questions 😉
Author
Owner

@Anurag0218 commented on GitHub (Oct 1, 2024):

is this issue still open? is anyone working on it? If not, can I take it up?

@Anurag0218 commented on GitHub (Oct 1, 2024): is this issue still open? is anyone working on it? If not, can I take it up?
Author
Owner

@CommanderStorm commented on GitHub (Oct 1, 2024):

Shure, nobody else has commented or provided a PR for this ❤️

@CommanderStorm commented on GitHub (Oct 1, 2024): Shure, nobody else has commented or provided a PR for this ❤️
Author
Owner

@devmuse7 commented on GitHub (Oct 1, 2024):

Hi @CommanderStorm I want to work on this issue. Kindly assign this to me.

@devmuse7 commented on GitHub (Oct 1, 2024): Hi @CommanderStorm I want to work on this issue. Kindly assign this to me.
Author
Owner

@nekojanai commented on GitHub (Oct 2, 2024):

@Itachii27 @Anurag0218 I'm already working on this?
see https://github.com/louislam/uptime-kuma/issues/5116#issuecomment-2369864760

@nekojanai commented on GitHub (Oct 2, 2024): @Itachii27 @Anurag0218 I'm already working on this? see https://github.com/louislam/uptime-kuma/issues/5116#issuecomment-2369864760
Author
Owner

@nekojanai commented on GitHub (Oct 2, 2024):

Is there an easy way to update translation strings?
To answer myself: Yes.
github.com/louislam/uptime-kuma@b287a25de7/CONTRIBUTING.md (can-i-create-a-pull-request-for-uptime-kuma)

language keys need to be added to en.json to be visible in weblate. If this has not happened, a PR is appreciated.

I guess, I'll just add Debug to the en.json

@nekojanai commented on GitHub (Oct 2, 2024): ~Is there an easy way to update translation strings?~ To answer myself: Yes. https://github.com/louislam/uptime-kuma/blob/b287a25de735d14c6e078d57e99b4587f10697cd/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma ``` language keys need to be added to en.json to be visible in weblate. If this has not happened, a PR is appreciated. ``` I guess, I'll just add `Debug` to the `en.json`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3615
No description provided.