I can give you my use case to help a bit with next steps! I’ve added a discourse endpoint to the “helpme” client → HelpMe | HelpMe - a command line tool for helping you out. and Journal of Open Source Software: HelpMe Command Line Helper Utility so that users can ask for help from the command line w…

I see, I am open to a PR here that makes your use case somewhat easier: helpme discourse somesite.com You have no authentication token to somesite.com to create one visit: http://somesite.com/api_key/new?application_name=helpme&public_key=ABCD&nonce=NONCE&client_id=client_id&auth_redirect... Then…

Ah, fantastic! Let me start to look over the development docs and I’ll see what I can do. The example usage is spot on, even better than the old school “log in and generate” that I had in mind!

Do you have any tips/ examples/ templates that could help me? I have no idea what I’m doing, the most I can tell is that I might add @headless = params[:headless] but then I don’t actually know what that’s doing… :confused: I think I would want to: add the parameter headless, with option to be…

heyo! My awesome collaborator is helping me out, so hopefully we can put our heads together and have a PR, maybe sometime over the weekend? I’ll ping you here if we run into trouble! His main language is Ruby, and he’s awesome, so I think for now we’re good! (and having fun too!) ---- edited! hey @…

Easiest way to get started is [이미지] Install Discourse for development using Docker Developer Guides Developing using Docker Since Discourse runs in Docker, you should be able to run Discourse directly from your source directory using a Discourse development co…

hey @sam ! This is fine if I just want to run the released discourse, but if I want to run a (development) version, from my Github repository, well I’ve been parsing through the dockerfiles this morning and it’s a nightmare - everything is a custom tool or command that has so many layers to reverse e…

You do not want to run your own version of Discourse from your own github repo. I promise. For many of the reasons that you have pointed out. You want to develop a plugin. Maybe you should see Install Discourse for development using Docker and Developing Discourse Plugins - Part 1 - Create a basic p…

haha yes, that describes all my frustrations quite well. So - an update to the controller script that @sam pointed out here: discourse/app/controllers/user_api_keys_controller.rb at 06d1b19ca2d8994d444ebfa3bb17634a4ae5ea7b · discourse/discourse · GitHub You are saying this should be done by way …

The only case that it makes sense to change the codebase rather than make changes in a plugin is if your change will be accepted in core. Otherwise, you’ll have to merge Discourse changes into your own, everyone who has done so was very sorry and spent lots of time and money undoing those changes. Y…

Correct - that is my use case. I am testing code that will be a PR to core, and I’d like to have a development server to test before doing a PR. I could PR blindly but that is not something I have ever done, it seems like bad practice.

Adding command line tools support for user api keys

개발

sam (Sam Saffron) 12월 8, 2018, 12:46오전 6

Easiest way to get started is

글		댓글	조회수
User API keys specification Integrations rest-api , reference	69	37363	9월 22, 2025
Create apikey for user programmatically as admin Development rest-api	8	2079	2월 26, 2024
Allow API use by regular users, not just admins Development rest-api	6	1508	2월 14, 2023
Discourse Keybase Proof Feature pr-welcome	73	6733	5월 28, 2021
Use the Discourse API ruby gem Integrations rest-api , how-to	0	24707	7월 15, 2014

Adding command line tools support for user api keys

Related topics