This is a project to keep and maintain all of the projects to be at gardnerwebtech.com in the future. Currently, I have 2 versions of the Recipes-Web app (one with auth, one without) as well as the recipes-cms project and the beginnings of my personal website. The guest app is being hosted at recipes-guest.vercel.app with fake recipes. The full app is a white-listed application that is not for public use.

The projects are:

• recipes-cms
• recipes-guest (port 3001)
• recipes-web (port 3000)
• web (port 3002)

This is an official Yarn v1 starter turborepo.

This turborepo uses Yarn as a package manager. It includes the following packages/apps:

• recipes-cms: a Sanity app
• recipes-guest: a Next.js app without authentication
• recipes-web: another Next.js app with authentication
• web: yet another Next.js stubbed out for my future personal application.
• ui: a stub React component library shared by both web and docs applications
• config: eslint configurations (includes eslint-next, postcss.config, and tailwind.config)
• tsconfig: tsconfig.jsons used throughout the monorepo

This turborepo has some additional tools already setup for you:

• TypeScript for static type checking
• ESLint for code linting
• Jest test runner for all things JavaScript
• Prettier for code formatting

Turborepo can use a technique known as Remote Caching (Beta) to share cache artifacts across machines, enabling you to share build caches with your team and CI/CD pipelines.

By default, Turborepo will cache locally. To enable Remote Caching (Beta) you will need an account with Vercel. If you don't have an account you can create one, then enter the following commands:

cd my-turborepo
npx turbo login

This will authenticate the Turborepo CLI with your Vercel account.

Next, you can link your Turborepo to your Remote Cache by running the following command from the root of your turborepo:

npx turbo link

Learn more about the power of Turborepo:

• Pipelines
• Caching
• Remote Caching (Beta)
• Scoped Tasks
• Configuration Options
• CLI Usage