4e09352c09
Bring simple signup flow from the fizzy-saas gem
...
We skip the QB code and we fill external account ids automatically on creation with a sequence
See:
https://github.com/basecamp/fizzy-saas/pull/7
2025-11-28 15:53:58 +01:00
2630e4bd74
Extract 37id and QB controllers, models, and tests
2025-09-13 16:03:02 -04:00
15876b8762
Update Signup to use the queenbee_id for the tenant name
...
and not the subdomain. This change should have been in #665
2025-07-18 10:11:10 -04:00
d29bfb9f5a
Add a QB API endpoint for plans
...
- add the shared api token to all environments
- add a single FreeV1 subscription
- add QB routes
- allow the queenbee routes in the tenanting middleware
ref: https://3.basecamp.com/2914079/buckets/37331921/todos/8746302763
2025-06-20 15:16:57 -04:00
1be9ba6ee3
Signup workflow for existing identity
2025-06-20 15:16:57 -04:00
237830d91c
During signup, name beta accounts distinctly
...
because Launchpad will present both in the UI, but will not be able to
redirect to a beta fizzy account from production launchpad (or vice versa).
2025-06-20 15:16:57 -04:00
a8a64a2384
Link the seeds up to the signal_id fixture data
2025-06-20 15:16:57 -04:00
4d7cd3a8a7
Signup supports using an existing identity
2025-06-20 15:16:57 -04:00
73ba0c074f
Introduce a Signup model and integrate with QB/37id
...
- Creates a Queenbee::Account
- SignalId peer classes work properly
- Set up a basic template for the account (closure reasons, workflow, collection)
- Load signal_id fixtures during `bin/setup --reset`
- Update signal_id to pull in the Fizzy product
2025-06-20 15:16:57 -04:00
Jorge Manrubia