Charles Bochet
3eeaebb0cc
## Summary The `--light` flag of `workspace:seed:dev` was supposed to seed a single workspace for thin dev containers, but it was only filtering the rich workspaces (Apple, YCombinator) — the `Empty3`/`Empty4` fixtures introduced in #19559 for upgrade-sequence integration tests were always seeded. So `--light` actually produced **3** workspaces: - Apple - Empty3 - Empty4 In single-workspace mode (`IS_MULTIWORKSPACE_ENABLED=false`, the default for the `twenty-app-dev` container), [`WorkspaceDomainsService.getDefaultWorkspace`](https://github.com/twentyhq/twenty/blob/main/packages/twenty-server/src/engine/core-modules/domain/workspace-domains/services/workspace-domains.service.ts) returns the most recently created workspace — Empty4 — which has no users. The prefilled `tim@apple.dev` therefore cannot sign in, which breaks flows that depend on the default workspace such as `yarn twenty remote add --local`'s OAuth handshake against the dev container. This PR makes `--light` actually skip the empty fixtures so the dev container ends up with a single workspace (Apple). The default (no flag) invocation, used by `database:reset` for integration tests, still seeds all four workspaces, so `upgrade-sequence-runner-integration-test.util.ts` keeps working unchanged.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
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
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria 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!