Skip to main content

Configuration

Successfully starting the platform does not mean it will display content the way you want. It's still early in the day, and we have some work to do. Let's start by configuring our SaaS site.

Configure Basic Platform

Configure basic information about the platform so that all places where basic information is displayed are related to you.

Please find config.js in the root directory. Here, you can modify basic information about the platform, such as the site name, description, domain name, and whether the site is internationalization or not. The prompts in this file can help you make the necessary settings. It looks like this:

config.js
const config = {
// The three items here are mandatory and are basic information about your startup that is vital for SEO.
// The domain name part is not required “https://”, “www”, and finally no slash. just the naked domain.
// The contact email is used for the support email in the app, and also for the Resend integration (if you use it).
appName: "OneDay.Build",
appDescription: "OneDay.Build provides individual developers or startups with a set of basic functionality packages for building a SaaS platform.The NextJS boilerplate with all you need to build your SaaS, AI tool, or any other web app.",
domainName: "OneDay.Build",
contactEmail: "bassnova@gmail.com",
};

export default config;

Configure Features

Many of the features provided by OneDay.Build for your SaaS platform, such as Auth and payment, are implemented using third-party tools. Therefore, to communicate with these tools smoothly, the platform needs to store the API information of each third-party tool. During the local debugging phase, you can complete this by recording this API information in the .env file in the root directory.

Open the .env file. We have preset some field names for services that you might use. You can register with the corresponding service provider and then fill in the API information here. If you encounter any problems during the registration process, our documentation will also provide you with corresponding guidance. The .env file also contains URLs for relevant help information.

.env

# ===============================================================
# MangoDB: https://docs.oneday.build/docs/features/Database
# +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DATABASE_URL= " "


# ===============================================================
# Auth: https://docs.oneday.build/docs/features/Auth
#
# +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SECRET = ' '

GITHUB_CLIENT_ID =
GITHUB_CLIENT_SECRET =
GOOGLE_CLIENT_ID =
GOOGLE_CLIENT_SECRET =