dronedock

Getting Started

Environment Variables

Create a .env file in the root directory with the following variables:

# Clerk
NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=
CLERK_SECRET_KEY=

# Database
DATABASE_URL=

# Trigger.dev
TRIGGER_SECRET_KEY=

# Docusign
DOCUSIGN_BASE_PATH=
DOCUSIGN_CLIENT_ID=
DOCUSIGN_CLIENT_SECRET=
DOCUSIGN_USER_ID=
DOCUSIGN_ACCOUNT_ID=
DOCUSIGN_PUBLIC_KEY=
DOCUSIGN_PRIVATE_KEY=

# Vercel KV
KV_REST_API_URL=http://localhost:8079
KV_REST_API_TOKEN=example_token

# Vercel Blob
BLOB_READ_WRITE_TOKEN=

# Mapbox
NEXT_PUBLIC_MAPBOX_ACCESS_TOKEN=

# OpenAI
OPENAI_API_KEY=

Run the development server:

npm run dev

Docusign eSignatures API

1. Create App in Apps and Keys
2. Copy Private Key, only displayed once
3. Manually go to URL to provide consent (https://www.docusign.com/blog/developers/oauth-jwt-granting-consent)

SERVER/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=CLIENT_ID&redirect_uri=REDIRECT_URI

Where

SERVER is https://account.docusign.com (production) or https://account-d.docusign.com (developer demo).

CLIENT_ID is your app’s integration key.

The REDIRECT_URI is a URI. It must exactly match one of the redirect URIs you defined for the app’s integration key in the Docusign eSignature Administration tool. The URI value must be encoded.

The URL will request individual consent for the two scopes: signature and impersonation. %20 is the encoded value for a space character.

Docusign Connect

1. Log in to your Docusign eSignature developer environment and select Admin.
2. In the left nav under INTEGRATIONS, select Connect.
3. Select ADD CONFIGURATION, then Custom. The Add Custom Configuration page opens.
4. Choose a Name for the configuration.
5. Choose a URL to Publish. This is the URL where your webhook listener will receive the event messages sent by Connect. For test purposes, you can use a URL from an online webhook test tool to receive and examine Connect events. For example, to get a test URL from an online test tool such as webhook.site, open the tool’s page in the browser and copy your unique test listener URL into the Connect URL to Publish field.

Docusign Navigator API

1. Enroll in private beta
2. Add adm_store_unified_repo_read scope while generating the JWT.

Import Airport GeoJSON into MongoDB

./mongoimport --db dronedock -c usaAirports --type json ./us_airports.geojson --uri mongodb+srv://username:password@host --jsonArray