Properties

appName
string
required

The name of your application.

Example: 'LaunchIt'

appUrl
string
required

The URL of your application.

Example: process.env.NEXT_PUBLIC_SITE_URL ?? ''

appDescription
string
required

The description of your application. This uses a translation key.

Example: 'config.appDescription'

supportEmail
string
required

The email address for support inquiries.

Example: '[email protected]'

marketingEmail
string
required

The email address for marketing communications.

Example: '[email protected]'

twitterHandle
string

The Twitter handle for your application.

Example: '@yourhandle'

onboadingActive
boolean
required

If you wish to display an onboarding page after the user signs up, you can enable it here. This will per default ask the user for his first name and last name.

Example: true

blogFolder
string
required

The folder containing your blog content files.

Example: 'web/content/blog'

i18n
I18nConfig
required

Internationalization (i18n) configurations.

login
LoginConfig
required

Authentication configurations. LaunchIt supports multiple authentication methods that can be enabled or disabled based on your needs.

privacyPolicyUrl
string
required

The URL for the privacy policy. Necessary for legal compliance (Cookie consent banner) and footer.

Example: '/privacy'

tosUrl
string
required

The URL for the terms of service. Necessary for legal compliance (Cookie consent banner) and footer.

Example: '/tos'

Cookie consent banner configurations.

services
ServicesConfig
required

Additional service configurations.

pricing
PricingConfig
required

Pricing configurations. LaunchIt supports both subscription and one-time purchase models. The pricing configuration is one of the most complex parts of the setup.

navigation
NavigationConfig
required

Navigation configurations.

oAuth Providers

oAuthProviders
OAuthProvider[]
required

Array of OAuth provider configurations. See List of supported OAuth Providers.

This will be automatically used in the <OAuthSignIn /> component on the sign-in page.

Further Information

Validation Checks:

  • At least one authentication provider must be active (either password login, magic link login, or an OAuth provider).
  • The default login method must be active.