Updated readme and removed t3 content from page
This commit is contained in:
parent
25162f8b50
commit
927a18baba
36
README.md
36
README.md
|
|
@ -1,29 +1,11 @@
|
|||
# Create T3 App
|
||||
This is my attempt at a ecommerce site selling wine.
|
||||
|
||||
This is a [T3 Stack](https://create.t3.gg/) project bootstrapped with `create-t3-app`.
|
||||
TODO (in no particular order for now):
|
||||
|
||||
## What's next? How do I make an app with this?
|
||||
|
||||
We try to keep this project as simple as possible, so you can start with just the scaffolding we set up for you, and add additional things later when they become necessary.
|
||||
|
||||
If you are not familiar with the different technologies used in this project, please refer to the respective docs. If you still are in the wind, please join our [Discord](https://t3.gg/discord) and ask for help.
|
||||
|
||||
- [Next.js](https://nextjs.org)
|
||||
- [NextAuth.js](https://next-auth.js.org)
|
||||
- [Prisma](https://prisma.io)
|
||||
- [Drizzle](https://orm.drizzle.team)
|
||||
- [Tailwind CSS](https://tailwindcss.com)
|
||||
- [tRPC](https://trpc.io)
|
||||
|
||||
## Learn More
|
||||
|
||||
To learn more about the [T3 Stack](https://create.t3.gg/), take a look at the following resources:
|
||||
|
||||
- [Documentation](https://create.t3.gg/)
|
||||
- [Learn the T3 Stack](https://create.t3.gg/en/faq#what-learning-resources-are-currently-available) — Check out these awesome tutorials
|
||||
|
||||
You can check out the [create-t3-app GitHub repository](https://github.com/t3-oss/create-t3-app) — your feedback and contributions are welcome!
|
||||
|
||||
## How do I deploy this?
|
||||
|
||||
Follow our deployment guides for [Vercel](https://create.t3.gg/en/deployment/vercel), [Netlify](https://create.t3.gg/en/deployment/netlify) and [Docker](https://create.t3.gg/en/deployment/docker) for more information.
|
||||
- [] Top nav
|
||||
- [] define (and draw?) db schemas
|
||||
- [] side product nav
|
||||
- [] product cards
|
||||
- [] cart
|
||||
- [] auth & login
|
||||
- [] user profile page
|
||||
|
|
|
|||
|
|
@ -2,35 +2,9 @@ import Link from "next/link";
|
|||
|
||||
export default function HomePage() {
|
||||
return (
|
||||
<main className="flex min-h-screen flex-col items-center justify-center bg-gradient-to-b from-[#2e026d] to-[#15162c] text-white">
|
||||
<div className="container flex flex-col items-center justify-center gap-12 px-4 py-16 ">
|
||||
<h1 className="text-5xl font-extrabold tracking-tight text-white sm:text-[5rem]">
|
||||
Create <span className="text-[hsl(280,100%,70%)]">T3</span> App
|
||||
</h1>
|
||||
<div className="grid grid-cols-1 gap-4 sm:grid-cols-2 md:gap-8">
|
||||
<Link
|
||||
className="flex max-w-xs flex-col gap-4 rounded-xl bg-white/10 p-4 text-white hover:bg-white/20"
|
||||
href="https://create.t3.gg/en/usage/first-steps"
|
||||
target="_blank"
|
||||
>
|
||||
<h3 className="text-2xl font-bold">First Steps →</h3>
|
||||
<div className="text-lg">
|
||||
Just the basics - Everything you need to know to set up your
|
||||
database and authentication.
|
||||
</div>
|
||||
</Link>
|
||||
<Link
|
||||
className="flex max-w-xs flex-col gap-4 rounded-xl bg-white/10 p-4 text-white hover:bg-white/20"
|
||||
href="https://create.t3.gg/en/introduction"
|
||||
target="_blank"
|
||||
>
|
||||
<h3 className="text-2xl font-bold">Documentation →</h3>
|
||||
<div className="text-lg">
|
||||
Learn more about Create T3 App, the libraries it uses, and how to
|
||||
deploy it.
|
||||
</div>
|
||||
</Link>
|
||||
</div>
|
||||
<main className="">
|
||||
<div className="container ">
|
||||
<h1>Yes hello</h1>
|
||||
</div>
|
||||
</main>
|
||||
);
|
||||
|
|
|
|||
82
src/env.js
82
src/env.js
|
|
@ -1,44 +1,44 @@
|
|||
import { createEnv } from "@t3-oss/env-nextjs";
|
||||
import { z } from "zod";
|
||||
// import { createEnv } from "@t3-oss/env-nextjs";
|
||||
// import { z } from "zod";
|
||||
|
||||
export const env = createEnv({
|
||||
/**
|
||||
* Specify your server-side environment variables schema here. This way you can ensure the app
|
||||
* isn't built with invalid env vars.
|
||||
*/
|
||||
server: {
|
||||
POSTGRES_URL: z.string().url(),
|
||||
NODE_ENV: z
|
||||
.enum(["development", "test", "production"])
|
||||
.default("development"),
|
||||
},
|
||||
// export const env = createEnv({
|
||||
// /**
|
||||
// * Specify your server-side environment variables schema here. This way you can ensure the app
|
||||
// * isn't built with invalid env vars.
|
||||
// */
|
||||
// server: {
|
||||
// POSTGRES_URL: z.string().url(),
|
||||
// NODE_ENV: z
|
||||
// .enum(["development", "test", "production"])
|
||||
// .default("development"),
|
||||
// },
|
||||
|
||||
/**
|
||||
* Specify your client-side environment variables schema here. This way you can ensure the app
|
||||
* isn't built with invalid env vars. To expose them to the client, prefix them with
|
||||
* `NEXT_PUBLIC_`.
|
||||
*/
|
||||
client: {
|
||||
// NEXT_PUBLIC_CLIENTVAR: z.string(),
|
||||
},
|
||||
// /**
|
||||
// * Specify your client-side environment variables schema here. This way you can ensure the app
|
||||
// * isn't built with invalid env vars. To expose them to the client, prefix them with
|
||||
// * `NEXT_PUBLIC_`.
|
||||
// */
|
||||
// client: {
|
||||
// // NEXT_PUBLIC_CLIENTVAR: z.string(),
|
||||
// },
|
||||
|
||||
/**
|
||||
* You can't destruct `process.env` as a regular object in the Next.js edge runtimes (e.g.
|
||||
* middlewares) or client-side so we need to destruct manually.
|
||||
*/
|
||||
runtimeEnv: {
|
||||
POSTGRES_URL: process.env.POSTGRES_URL,
|
||||
NODE_ENV: process.env.NODE_ENV,
|
||||
// NEXT_PUBLIC_CLIENTVAR: process.env.NEXT_PUBLIC_CLIENTVAR,
|
||||
},
|
||||
/**
|
||||
* Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation. This is especially
|
||||
* useful for Docker builds.
|
||||
*/
|
||||
skipValidation: !!process.env.SKIP_ENV_VALIDATION,
|
||||
/**
|
||||
* Makes it so that empty strings are treated as undefined. `SOME_VAR: z.string()` and
|
||||
* `SOME_VAR=''` will throw an error.
|
||||
*/
|
||||
emptyStringAsUndefined: true,
|
||||
});
|
||||
// /**
|
||||
// * You can't destruct `process.env` as a regular object in the Next.js edge runtimes (e.g.
|
||||
// * middlewares) or client-side so we need to destruct manually.
|
||||
// */
|
||||
// runtimeEnv: {
|
||||
// POSTGRES_URL: process.env.POSTGRES_URL,
|
||||
// NODE_ENV: process.env.NODE_ENV,
|
||||
// // NEXT_PUBLIC_CLIENTVAR: process.env.NEXT_PUBLIC_CLIENTVAR,
|
||||
// },
|
||||
// /**
|
||||
// * Run `build` or `dev` with `SKIP_ENV_VALIDATION` to skip env validation. This is especially
|
||||
// * useful for Docker builds.
|
||||
// */
|
||||
// skipValidation: !!process.env.SKIP_ENV_VALIDATION,
|
||||
// /**
|
||||
// * Makes it so that empty strings are treated as undefined. `SOME_VAR: z.string()` and
|
||||
// * `SOME_VAR=''` will throw an error.
|
||||
// */
|
||||
// emptyStringAsUndefined: true,
|
||||
// });
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user