7a4599321b
## Architecture Detail The goal is to merge the two TypeORM schemas. Having two schemas prevent doing things like fieldMetadata.workspace in TypeORM, and create useless debates since there is no clear line (is a serverlessFunction core or metadata? What about events? etc.) ### Before ``` ┌───────────────────┐ ┌───────────────────┐ │ core schema │ │ metadata schema │ ├───────────────────┤ ├───────────────────┤ │- User │ │- ObjectMetadata │ │- Workspace │ │- FieldMetadata │ │- UserWorkspace │ │- RelationMetadata │ │- etc. │ │- etc. │ └───────────────────┘ └───────────────────┘ ``` ### After the Migration ``` ┌───────────────────────────────────────────┐ │ engine schema │ ├───────────────────────────────────────────┤ │- User - ObjectMetadata │ │- Workspace - FieldMetadata │ │- UserWorkspace - RelationMetadata │ │- etc. - etc. │ └───────────────────────────────────────────┘ ``` ## Strategy 1. During 0.53 we backfill the *_typeorm_migrations* table of the core schema with all metadata migrations 2. That way in 0.54 we can move the metadata migrations from the metadata folder to the core folder. We will also edit the migration files to reference "core" instead of "metadata". For people doing a fresh install this will run smoothly and create the tables in Core directly. For people on an existing install, this migrations will not run because they were added to the *_typeorm_migrations* in 0.53 3. In 0.55 we will rename "core" to something else (for example "engine") Note: if someone jumps version, for example skips to 0.54 directly without having run 0.53 then this could cause issue. In 0.54 we should consider gating the "migrate:prod" in the docker file so that it's controlled and run by the upgrade command (and not run if the command wasn't executed properly)
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See:
🚀 Self-hosting
🖥️ Local Setup
Does the world need another CRM?
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in Open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
We're currently developing Twenty's beta version.
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Add, filter, sort, edit, and track customers
- Create one or several opportunities for each company
- See rich notes tasks displayed in a timeline
- Create tasks on records
- Navigate quickly through the app using keyboard shortcuts and search
Add, filter, sort, edit, and track customers:
Create one or several opportunities for each company:
Track deals effortlessly with the email integration:
Tailor your data model to meet business needs:
See rich notes displayed in a timeline:
Create tasks on records
Navigate quickly through the app using keyboard shortcuts and search:
Connect your CRM to all your tools through our APIs and Webhooks.
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Recoil, Emotion and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!