Skip to content

Allow commands to run in user-installed context #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Aug 12, 2024
Merged

Allow commands to run in user-installed context #89

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
389e6f3
Update discord-api-types + workers-discord
MattIPv4 Aug 12, 2024
20f9beb
Allow user-install for all commands
MattIPv4 Aug 12, 2024
412344c
Add notes to README for user-install commands
MattIPv4 Aug 12, 2024
a600fdf
Improve command registration debugging
MattIPv4 Aug 12, 2024
3c3577a
Add new invite for user-install
MattIPv4 Aug 12, 2024
9d3ffd2
Don't scope staging to a specific guild
MattIPv4 Aug 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/workflows/deployment-staging.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,6 @@ jobs:
CLIENT_ID: ${{ secrets.STAGING_CLIENT_ID }}
CLIENT_SECRET: ${{ secrets.STAGING_CLIENT_SECRET }}
CLIENT_PUBLIC_KEY: ${{ secrets.STAGING_CLIENT_PUBLIC_KEY }}
TEST_GUILD_ID: ${{ secrets.STAGING_TEST_GUILD_ID }}
SENTRY_AUTH_TOKEN: ${{ secrets.STAGING_SENTRY_AUTH_TOKEN }}
SENTRY_ORG: ${{ secrets.STAGING_SENTRY_ORG }}
SENTRY_PROJECT: ${{ secrets.STAGING_SENTRY_PROJECT }}
Expand Down
15 changes: 13 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

---

1.1.1.1 works from a Discord server, thanks to the 1.1.1.1 bot. [Invite the bot to your Discord server](https://dns-over-discord.v4.wtf/invite) to start using DNS over Discord.
1.1.1.1 works from a Discord server, thanks to the 1.1.1.1 bot. [Invite the bot to your Discord server](https://dns-over-discord.v4.wtf/invite) to start using DNS over Discord. Or, [add the bot to your Discord account](https://dns-over-discord.v4.wtf/invite/user) to use it anywhere in Discord.

## Perform DNS lookups

Expand Down Expand Up @@ -301,8 +301,9 @@ Example:

### `invite` command

The `/invite` command provides the user with a quick link to invite the 1.1.1.1 DNS over Discord bot to another Discord server.
The `/invite` command provides the user with a quick link to invite the 1.1.1.1 DNS over Discord bot to another Discord server, or to add it to a Discord account.
The bot can be invited at any time with [https://dns-over-discord.v4.wtf/invite](https://dns-over-discord.v4.wtf/invite).
The bot can also be added to accounts with [https://dns-over-discord.v4.wtf/invite/user](https://dns-over-discord.v4.wtf/invite/user).

```txt
/invite
Expand Down Expand Up @@ -361,6 +362,16 @@ node
5. Develop with the worker by running `npm run dev`.
6. (Optional) Start an HTTP tunnel to your local development server by running `npm run tunnel`, using [cloudflared](https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/run-tunnel/trycloudflare).

### User-installed commands

To test the user-installed commands functionality, you'll need to make sure your Discord application has the User Install option enabled.

You'll then need to make sure that the `TEST_GUILD_ID` in `development.env` is commented out, as user-installed commands need to be registered globally.

After that, start the worker as usual with `npm run dev`, install the application to your Discord user, and test the commands.

If you no longer wish to have the commands registered globally, leave `TEST_GUILD_ID` commented and update `webpack.config.js` to pass an empty array to the `registerCommands` call, then start the worker again to remove the global commands.

## Deployments

`wrangler.toml` and this repository is currently designed for a staging deployment and a production deployment.
Expand Down
Loading