Deploy our API on your server #

To deploy our API on your server you only need to create a .env file and fill it with your secret phrase to allow for token autentification. This file should be located in the root folder. You can also set request limits in that file.

The example file should look like this:

RATE_LIMIT_TTL_SEC=60 
RATE_LIMIT_REQ_COUNT_PUBLIC=20
RATE_LIMIT_REQ_COUNT_AUTH=100
JWT_SECRET_KEY=YourSecretPhrase
RECAPTCHA_SECRET_KEY=YourRecaptchaSecretKey
PORT=YourHTTPServerPort
DB_HOST=localhost
DB_PORT=5432
DB_USER=YourUser
DB_PASS=YourPassword
DB_NAME=YourDBName
EMAIL_ADDRESS_SENDER=sender@gmail.com
EMAIL_ADDRESS_RECIPIENT_ARR=admin1@gmail.com,admin2@gmail.com
EMAIL_CLIENT_ID=YourClientId
EMAIL_CLIENT_SECRET=YourClientSecret
EMAIL_REDIRECT_URI=YourRedirectUri
EMAIL_REFRESH_TOKEN=YourClientRefreshToken
MIXPANEL_PROJECT_TOKEN=YourMixPanelToken
SENTRY_DSN=YourSentryToken

What each line in the file means (every line must be configured otherwise API won't start):

• RATE_LIMIT_TTL_SEC: Line specifies how much time is allowed to pass before the request counter is reset.
• RATE_LIMIT_REQ_COUNT_PUBLIC: Line specifies users without token authentification and how many requests they are allowed to do per specified time.
• RATE_LIMIT_REQ_COUNT_AUTH: Line specifies users with token authentification and how many requests they are allowed to do per specified time.
• JWT_SECRET_KEY: Key, that has to be set before the server is launched. Secret from which all tokens are hash-derived.
• RECAPTCHA_SECRET_KEY: Secret key for your ReCaptcha. A guide on how it can be obtained can be found here. Make sure to select reCAPTCHA v2 when generating new key.
• PORT: Specifies the port on which the API server will be running. This parameter is optional and if now added API will default to port 3001
• DB_HOST: Specifies host for your Postgresql database.
• DB_PORT: Specifies the port for your Postgresql database.
• DB_USER: Specifies database superuser username.
• DB_PASS: Specifies database superuser password.
• DB_NAME: Specifies your Postgresql database name.
• EMAIL_ADDRESS_SENDER: Specifies the email address that will send responses to filled forms.
• EMAIL_ADDRESS_RECIPIENT_ARR: Specifies the email address that will receive responses from filled forms. There can be multiple emails set and you can observe in the example above how to insert them.
• EMAIL_CLIENT_ID: These are required for nodemailer find out more in this tutorial.
• EMAIL_CLIENT_SECRET: These are required for nodemailer find out more in this tutorial.
• EMAIL_REDIRECT_URI: These are required for nodemailer find out more in this tutorial.
• EMAIL_REFRESH_TOKEN: These are required for nodemailer find out more in this tutorial.
• MIXPANEL_PROJECT_TOKEN: This token is for statistics that track requests (Not saving amounts and wallet addresses to keep the privacy of users intact). This parameter is optional.
• SENTRY_DSN: This token is for sentry - statistics tool that tracks errors produced by API to create easier debugging for developers. This parameter is optional.

More on this feature can be found in the following Pull request

NOTE BEFORE DEPLOYING: Database must be specifically POSTGRESQL #

Make sure to also test every form before deploying to ensure everything is configured correctly.

If we configured everything correctly we should receive emails similar to the one showcased below. These should be received at email addresses we specified in the EMAIL_ADDRESS_RECIPIENT_ARR configuration line.

Based on the UserID received in the email we can edit the maximum request amount for specific API key. NOTE: Database overrides maximum request count. If the value is left on null the user can generate a default of 100 requests per minute just like before as Captcha verified user.

Setting up sentry #

Recently LightSpell introducet sentry error tracking service implementation. This guide covers how to use it.

• First step is to register at this website.
• Create new project to get DSN token for .env file used by LightSpell
• Monitor your issues through dashboard, if you receive any unhandled issues you should be notified by email also

How to trigger sentry error #

Open your rest API client, client we use is Insomnia.

Paste in following details and input following link to test out sentry: http://localhost:3001/sentry-test

LightSpell have integrated this test for you so you can test out error 500 in localhost mode. Once you pasted the link into browser sentry should notify you about new error 500. It should look like this in your project:

You can see, that exact line of where error was triggered is shown and you can even try to ask AI for help with resolving the task for you.

This confirms, that the sentry is working correctly.