Download the Code Files

If you purchased MetaJob from JS Template, you will receive the complete codebase and a license activation token directly via email.

If you purchased from ThemeForest, please email us to request your activation token for installation and setup.

A valid license token is required to run the project.

Before getting started, make sure you have:
✅ MetaJob Codebase (full project files)
✅ License Activation Token

Open the project in your preferred code editor (e.g., VS Code (opens in a new tab))

🔧 Configuring Environment Variables

To set up your environment variables, follow these steps:

Rename the Example Environment File

In the root of your project, locate the example.env file and rename it to .env.

mv example.env .env

Set Up Backend Environment Variables

Navigate to the backend directory and rename the environment file:

mv apps/backend/example.env apps/backend/.env

Activation Required

If you don't have an activation token to run the project, please contact us.

If you have an activation token, follow the steps below to configure it.

Using the Registry

npm config set @jstemplate:registry=https://api.keygen.sh/v1/accounts/88de7a21-b541-48e5-8727-f992ebeb43fa/artifacts/
npm config set "//api.keygen.sh/v1/accounts/88de7a21-b541-48e5-8727-f992ebeb43fa/artifacts/:_authToken" "$KEYGEN_TOKEN"

For example, KEYGEN_TOKEN could be a license token for an end-user.

Avoiding Hardcoded Tokens in .npmrc

If you'd rather not store your token in your global .npmrc, you can tell npm to pull the token from an environment variable. For example, this would pull the token from a KEYGEN_TOKEN env var:

(Note the single quotes)

npm config set @jstemplate:registry 'https://api.keygen.sh/v1/accounts/88de7a21-b541-48e5-8727-f992ebeb43fa/artifacts/'
npm config set '//api.keygen.sh/v1/accounts/88de7a21-b541-48e5-8727-f992ebeb43fa/artifacts/:_authToken=${KEYGEN_TOKEN}'

Project-Specific .npmrc for CI/CD

Use a project-specific .npmrc file with a variable for your token to securely authenticate your CI/CD server. Project-specific .npmrc files can be safely checked into version control since the token is not hardcoded:

@jstemplate:registry=https://api.keygen.sh/v1/accounts/88de7a21-b541-48e5-8727-f992ebeb43fa/artifacts/
//api.keygen.sh/v1/accounts/88de7a21-b541-48e5-8727-f992ebeb43fa/artifacts/:_authToken=${KEYGEN_TOKEN}

✅ Install Dependencies

Once everything is set up, you're ready to install project dependencies:

pnpm install

Now, you're all set to run the project! 🚀

🚀 Running the Project

Before starting the frontend, make sure the backend is running first to avoid connection issues.

Start the Backend (Strapi API Server)

Run the following command to start the Strapi backend:

pnpm -F backend dev

Once started, you can access the Strapi Admin Panel at:
🔗 http://localhost:1337/ (opens in a new tab)

🔑 Generate an API Access Token

1. Create an admin account in Strapi.
2. Navigate to Settings → API Tokens.
3. Generate a new Full Access API Token.
4. Copy this token and add it to your root .env file:

export STRAPI_API_TOKEN="Your_Generated_Token_Here"

Start the Frontend (Next.js UI)

Once the backend is up and configured, start the Next.js frontend:

pnpm -F core dev

Your frontend will now be available at:
🔗 http://localhost:3000/ (opens in a new tab)

Now, you're ready to explore MetaJob! 🚀