https://github.com/mmvergara/threads-clone

Simple threads clone made using remix, drizzle, sqlite.
https://github.com/mmvergara/threads-clone

drizzle drizzle-orm react remix remixjs sqlite sqlite3 threads threads-clone uploadthing

Last synced: 10 months ago
JSON representation

Simple threads clone made using remix, drizzle, sqlite.

• Host: GitHub
• URL: https://github.com/mmvergara/threads-clone
• Owner: mmvergara
• License: mit
• Created: 2024-12-08T23:18:41.000Z (about 1 year ago)
• Default Branch: master
• Last Pushed: 2025-01-17T00:16:57.000Z (about 1 year ago)
• Last Synced: 2025-04-09T22:15:36.929Z (10 months ago)
• Topics: drizzle, drizzle-orm, react, remix, remixjs, sqlite, sqlite3, threads, threads-clone, uploadthing
• Language: TypeScript
• Homepage:
• Size: 4.1 MB
• Stars: 2
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.MD

Awesome Lists containing this project

README

          
Created: Dec 8, 2024

Threads Clone










Simple Threads Clone with Remix and Drizzle



---

### Stack

- Remix

- Drizzle

- Sqlite

- Uploadthing

### Installation

Fill in the .env file with the correct values.

then

```bash

# Install dependencies

npm install

# Create local.db

touch local.db

# Push schema to local.db

npx drizzle-kit push

# Run

npm run dev

# Open studio for database visualization

npx drizzle-kit studio

```

---

### Screenshots

![Screenshot 1](./screenshots/1.png)

![Screenshot 2](./screenshots/2.png)

![Screenshot 3](./screenshots/3.png)

![Screenshot 4](./screenshots/4.png)

![Screenshot 5](./screenshots/5.png)

![Screenshot 6](./screenshots/6.png)

![Screenshot 7](./screenshots/7.png)

![Screenshot 8](./screenshots/8.png)

![Screenshot 9](./screenshots/9.png)

#### Thoughts upon developing (probably irrelevant)

- Remix has a straightforward logic, only took me a few days to understand the concepts of Remix.

- Execessive use of toast notifications, but it's just for the sake of learning.

- They kinda stick to web standards, so it's easy to understand.

- No middlewares, so we have to check for user session in every route for authorization.

  > https://remix.run/docs/en/1.19.3/pages/faq#how-can-i-have-a-parent-route-loader-validate-the-user-and-protect-all-child-routes