An open API service indexing awesome lists of open source software.

https://github.com/zatarain/crm-dupkiller

CRM DupKiller - Hack Night @ Cloudflare 2025 ft. Fiberplane, Claude, Elevenlabs
https://github.com/zatarain/crm-dupkiller

ai anthropic artificial-intelligence claude claude-ai cloudflare elevenlabs fiberplane hack-night-2025 hackathon london prototype

Last synced: 3 months ago
JSON representation

CRM DupKiller - Hack Night @ Cloudflare 2025 ft. Fiberplane, Claude, Elevenlabs

Awesome Lists containing this project

README

          

# CRM DupKiller

This is the prototype I built during the Hack Night @ Cloudflare 2025 ft. Fiberplane, Claude \ Anthropic & Elevenlabs.

This repository includes an `SPEC.md` generated by the AI, but I also made some tweaks in the styling with Markdown.

Additionaly, when I interact with AI for coding I like to save and include the log of the conversation I had, so I added this in the `chat.ai.log.md`, so other people can follow if they are interested. All the quantities are fake.

Following screenshot is the preview of the generated dashboard:

![image](https://github.com/user-attachments/assets/6579e47c-8ae7-4270-b546-134beb56401c)

## πŸͺΏ HONC

This is a project created with the `create-honc-app` template.

Learn more about the HONC stack on the [website](https://honc.dev) or the main [repo](https://github.com/fiberplane/create-honc-app).

There is also an [Awesome HONC collection](https://github.com/fiberplane/awesome-honc) with further guides, use cases and examples.

### Getting started
[D1](https://developers.cloudflare.com/d1/) is Cloudflare's serverless SQL database. Running HONC with a D1 database involves two key steps: first, setting up the project locally, and second, deploying it in production. You can spin up your D1 database locally using Wrangler. If you're planning to deploy your application for production use, ensure that you have created a D1 instance in your Cloudflare account.

### Project structure

```#
β”œβ”€β”€ src
β”‚ β”œβ”€β”€ index.ts # Hono app entry point
β”‚ └── db
β”‚ └── schema.ts # Database schema
β”œβ”€β”€ .dev.vars.example # Example .dev.vars file
β”œβ”€β”€ .prod.vars.example # Example .prod.vars file
β”œβ”€β”€ seed.ts # Optional script to seed the db
β”œβ”€β”€ drizzle.config.ts # Drizzle configuration
β”œβ”€β”€ package.json
β”œβ”€β”€ tsconfig.json # TypeScript configuration
└── wrangler.toml # Cloudflare Workers configuration
```

### Commands for local development

Run the migrations and (optionally) seed the database:

```sh
# this is a convenience script that runs db:touch, db:generate, db:migrate, and db:seed
npm run db:setup
```

Run the development server:

```sh
npm run dev
```

As you iterate on the database schema, you'll need to generate a new migration file and apply it like so:

```sh
npm run db:generate
npm run db:migrate
```

### Commands for deployment

Before deploying your worker to Cloudflare, ensure that you have a running D1 instance on Cloudflare to connect your worker to.

You can create a D1 instance by navigating to the `Workers & Pages` section and selecting `D1 SQL Database.`

Alternatively, you can create a D1 instance using the CLI:

```sh
npx wrangler d1 create
```

After creating the database, update the `wrangler.toml` file with the database id.

```toml
[[d1_databases]]
binding = "DB"
database_name = "honc-d1-database"
database_id = ""
migrations_dir = "drizzle/migrations"
```

Include the following information in a `.prod.vars` file:

```sh
CLOUDFLARE_D1_TOKEN="" # An API token with D1 edit permissions. You can create API tokens from your Cloudflare profile
CLOUDFLARE_ACCOUNT_ID="" # Find your Account id on the Workers & Pages overview (upper right)
CLOUDFLARE_DATABASE_ID="" # Find the database ID under workers & pages under D1 SQL Database and by selecting the created database
```

If you haven’t generated the latest migration files yet, run:

```shell
npm run db:generate
```

Afterwards, run the migration script for production:
```shell
npm run db:migrate:prod
```

Change the name of the project in `wrangler.toml` to something appropriate for your project:

```toml
name = "my-d1-project"
```

Finally, deploy your worker

```shell
npm run deploy
```