Project Status:
Inspired by sylveon
- Deploy on Netlify
- Deploy on your own web server
- How to block users
- How to create your own custom questions
- Adding Email Functionality to appeals form
- Generating a Personal Access Token
- Deny and Block Feature
- Differences between this repo and sylveon's
- Feature Roadmap
REQUIREMENTS
- Have a server where you are able to:
- Make channels
- Create Webhooks
- Invite bots
NOTE: If you already have a custom bot in your server and access to its credentials, skip the first step
- Create a custom bot inside your server. You can register/invite one here. Keep that window handy.
- Click the "Deploy to Netlify" button.
- You will be asked to link your GitHub account then enter values for all the environment variables. (See Environment Variable Information Table)
- Set the environment variables from your Discord bot application page (
REACT_APP_CLIENT_ID,REACT_APP_CLIENT_SECRET,REACT_APP_DISCORD_BOT_TOKEN) - Choose a channel (or create a new one) where you want all the ban appeals to appear and copy its ID into
APPEALS_CHANNEL - Copy your server's ID into
REACT_APP_GUILD_ID - Make a random JWT Secret or generator one here and set inside
REACT_APP_JWT_SECRET - Set
REACT_APP_ENABLE_HCAPTCHAtofalseunless you intend to add hCaptcha - Set
REACT_APP_ENABLE_SENDGRIDtofalseunless you intend to use Sendgrid for unban notifications. - Make and set the
GITHUB_PAT(see table for information on how) - Deploy your application
- Lastly we'll want to make sure users can login using Discord
- First make any changes to the netlify.app deployment URL you wish, or set up your own custom one!
- From the Discord Developer Application page Select the OAuth tab
- Click on Add Redirect and enter
https://[site-url]/callbackwhere[site-url]is the site name netlify assigned you, or the one you changed it to.
| Environment Variable | Description | Optional? |
|---|---|---|
| REACT_APP_CLIENT_ID | Client ID of a Discord Application | No |
| REACT_APP_CLIENT_SECRET | Client Secret of a Discord Application | No |
| REACT_APP_DISCORD_BOT_TOKEN | The Bot token of a Discord Application | No |
| REACT_APP_GUILD_ID | The Server/Guild ID where you are accepting ban appeals | No |
| REACT_APP_JWT_SECRET | A really long string of characters used to establish a secure line of communication with the API of this app. I would recommend using a password generator to create this. You don't have to remember what its set to |
No |
| REACT_APP_SKIP_BAN_CHECK | If set to "true" the application will not check if a user is banned before allowing them to fill out an appeal form |
Yes |
| REACT_APP_BANNER_URL | Add a custom banner behind your server icon. Must be a direct link to an image (usually ends in .jpeg or .png etc.) |
Yes |
| REACT_APP_SITE_TITLE | Use a custom title for your site (defaults to {server_name}'s Discord Ban Appeal Application if none is set) | Yes |
| REACT_APP_SITE_DESCRIPTION | Use a custom SEO description for your site (defaults to {server_name}'s Discord Ban Appeal Application if none is set) | Yes |
| APPEALS_CHANNEL | The channel where you want appeals to appear in | No |
| REACT_APP_ENABLE_HCAPTCHA | Do you want to use hCaptcha in the form? (true/false) | Yes |
| REACT_APP_HCAPTCHA_SITE_KEY | The hCaptcha site key generated by hCaptcha | Yes |
| REACT_APP_HCAPTCHA_SECRET_KEY | The secret on your hCaptcha profile | Yes |
| REACT_APP_GOOGLE_ANALYTICS_ID | Google Analytics Tracking ID like UA-000000-01. | Yes |
| REACT_APP_ENABLE_SENDGRID | Sends users an email when they are unbanned (true/false) See Wiki if you don't know how to set this up | No |
| SENDGRID_API_KEY | API Key for Sendgrid | Yes |
| SENDGRID_SENDER_EMAIL | Single Sender Verification Email | Yes |
| INVITE_URL | Discord invite that can be used in email template to unbanned users | Yes |
| GITHUB_PAT | Github Personal Access Token for Deny and Block feature to work. Make sure it never expires and to select the repo scope |
No |
This if by far not the prettiest way to do this which is why I recommend you use netlify, but if you're smart enough to deploy this on your own then go for it!
Be aware this project uses serverless functions as its API layer. All the API requests are directed at /.netlify/functions because support issues with netlify's redirect rules. To deploy this yourself you will need to create a serverless API using AWS Lambda or an equivalent from Azure or GCP. I will go into specifics below.
- Fork this repo
- Copy
.env.exampleto.envand fill in each value - Run
yarn installto install the dependencies - Run
yarn buildto compile a production build - Direct your webserver to serve the
./build/directory
- Create a new serverless API in your cloud provider with 4 endpoints.
- Each File in
/functionswill be an endpoint, and most of them will require both the files in the/functions/helpersfolder
- Each File in
- Make sure all the packages from
package.jsonare installed and available for each function - Find and replace all occurrences of
/.netlify/functions/with your endpoint for each function
I've oversimplified a lot of the serverless portion here since it will vary based on your cloud provider but this covers the jist of things.
- Server icon and custom banner on landing page
- Only allow users who are actually banned to submit an appeal
- Ability to disable this check
- Custom meta tags for better SEO and visibility.
- IMO a cleaner approach to custom questions.
- Email integration for unban notification
- Deny and block users from discord embed
- Allow users to be blocked from submitting a ban appeal
- Add better meta tag support
- Custom Questions defined by the user
- add hCaptcha/reCaptcha
- Integrate some means of alerting users who are unbanned
- Additional Actions such as "Deny Ban appeal".
- Optional Google Analytics tracking
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent
