https://github.com/devloop01/todoit

a simple todo app powered by svelte
https://github.com/devloop01/todoit

Last synced: 20 days ago
JSON representation

a simple todo app powered by svelte

• Host: GitHub
• URL: https://github.com/devloop01/todoit
• Owner: devloop01
• Created: 2023-07-21T13:53:42.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-11-16T05:21:47.000Z (almost 1 year ago)
• Last Synced: 2023-11-17T05:32:20.313Z (12 months ago)
• Language: Svelte
• Homepage: https://dub.sh/todoit
• Size: 1.01 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# todoit

A minimal todo app, powered by [`svelte`](https://github.com/sveltejs/svelte).

## Run Locally

after cloning the project run `pnpm i` (or `npm install` or `yarn`), start a development server:

```bash

pnpm dev

```

To run the `database` locally on your comuter

```bash

pnpm db:start

```

## Generating & Pushing migrations

I'm using Drizzle ORM to generate and push database migrations (both local & production)

run below command to `generate` migrations

```bash

pnpm db:generate

```

run below command to `push` the migrations

```bash

pnpm db:push

```

or instead of running separately run below command to do both (`generate` and `push`)

```bash

pnpm db:migrate

```

## Setup with Vercel

After importing the project from github in vercel add your `environment` variables

In the `Build and Output Settings` toggle `override` and set the build command to

```bash

pnpm db:migrate && vite build

```

This will create the migrations and push them to the connected `local` or `production` database

It's better to generate migrations and test locally before pushing the migrations.

PS: sometimes vercel tries to use the generated cache and that results in build error you can disable new builds to use cache using  `VERCEL_FORCE_NO_BUILD_CACHE`, and setting this value to `1`