HappyBean Legacy (ASP.NET Core + Angular)¶
The previous-generation product, still in production while we migrate customers to HappyBean 2.0.
Multi-tenant via subdomain
The legacy app is multi-tenant. Each customer (tenant) gets their own subdomain of happybean.app. To log in, you go to <tenant-name>.happybean.app and use a user account that exists in that tenant.
Customer-facing URLs (what users actually use)¶
Production¶
| Tenant | URL |
|---|---|
| Admin tenant (host-level, manages all tenants) | https://admin.happybean.app |
| Demo tenant (sandbox for sales / training) | https://demo.happybean.app |
| Customer tenant | https://<tenant-name>.happybean.app |
Dev¶
Same model as production — there's an admin tenant and a demo tenant, with the same admin username on each. Ask a developer for the current dev subdomain pattern (or the raw App Service URL below).
Underlying Azure App Service hostnames¶
These are the raw Azure URLs behind the friendly subdomains. Most people don't need these — use the customer-facing URLs above.
| Dev (Canada Central) | Production (Canada Central) | |
|---|---|---|
| Web | https://app-happybean-web-dev-cc.azurewebsites.net | https://app-happybean-web-prod-cc.azurewebsites.net |
| API | https://app-happybean-api-dev-cc.azurewebsites.net | https://app-happybean-api-prod-cc.azurewebsites.net |
How login works¶
- Go to the tenant's subdomain (e.g. https://demo.happybean.app).
- Enter the username and password for an account on that tenant.
- Each tenant has its own separate users —
adminondemo.happybean.appis not the same account asadminonadmin.happybean.app.
Tech stack¶
- Frontend: Angular
- Backend: ASP.NET Core
- Hosting: Azure App Service (Canada Central)
- Multi-tenancy: Subdomain-based (
<tenant>.happybean.app)
→ See Accounts for usernames.