246 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
root	a947e48c49	Fixed the dashboard sidebar redirect issue by making browser-side dashboard API calls always go through the same-origin proxy at /dashboard/api/v1	2026-07-02 15:02:10 -04:00
root	6913c298ad	Route storefront marketplace under /storefront ... Replace the legacy /explore marketplace route with /storefront across the storefront app and production routing. - move the marketplace index page to the storefront root route - move company and vehicle detail pages from /explore/* to /* internally - update marketplace links, renter dashboard links, saved company links, and header navigation to target /storefront - remove remaining explore route references and wording from storefront code - configure production Traefik to route /storefront and strip the prefix before forwarding to the storefront service - set the storefront production asset prefix to /storefront so Next chunks load from /storefront/_next instead of the shared root /_next path - redirect locale entry paths such as /storefront/fr back to /storefront while persisting the selected language cookie - update middleware tests for the locale redirect and adjusted redirect mock Verification: - npm run test --workspace @rentaldrivego/storefront - npm run build --workspace @rentaldrivego/storefront	2026-07-02 14:47:50 -04:00
root	b45f84d62b	The dashboard middleware was treating /dashboard/api/v1/* as protected dashboard pages, so even the login request: ... /dashboard/api/v1/auth/employee/login was getting 307 redirected to /dashboard/sign-in. That meant sign-in could never set/read the employee_session cookie, and every dashboard page kept bouncing back to sign-in.	2026-07-02 14:19:45 -04:00
root	781512399b	Update homepage routes to include language and mode	2026-07-02 14:10:17 -04:00
root	56c3bcf666	fix homepage storefront proxy and CSP	2026-07-02 13:55:10 -04:00
root	9c11f3660d	Fix dashboard redirects leaking internal port	2026-07-02 13:34:28 -04:00
root	7c1bd2d0c0	Support insecure VPN registry pulls	2026-07-02 12:06:01 -04:00
root	1fd1ddf3f2	Support registry token for VPN image pulls	2026-07-02 11:49:58 -04:00
root	0394f0ea2a	Update production registry pull over VPN ... Configure production defaults to pull images directly from the VPN registry at 10.0.0.4, with the VPS reachable at 10.0.0.1, and disable archive handoff by default.	2026-07-02 11:36:35 -04:00
root	2993dd5b57	fix: return baseline menu for full-access accounts	2026-07-02 03:31:14 -04:00
root	e93b988146	fix: align dashboard guard with fallback menu access	2026-07-02 03:18:42 -04:00
root	ea2bd215f6	fix: align dashboard guard with fallback menu access	2026-07-02 03:06:45 -04:00
root	13b54f07de	fix: normalize homepage API URL and enforce expired trial access	2026-07-02 02:45:08 -04:00
root	75a1d39050	fix: enforce expired trial subscription menu access	2026-07-02 02:32:37 -04:00
root	0dcbe18c54	fix production API and storefront routing ... Normalize dashboard API base URLs so bare API origins still call /api/v1 endpoints. Reuse the shared dashboard API base on email verification. Update production storefront URL examples to use the root domain and route footer, policy, and workspace storefront paths through Traefik.	2026-07-02 02:02:31 -04:00
root	8ef61d7005	I also hardened the dashboard API helper so a bare origin	2026-07-02 01:43:27 -04:00
root	56984c4ea7	fix the acme email	2026-07-02 01:05:32 -04:00
root	330fc11791	Updated the homepage CSP for the new browser error.	2026-07-02 00:30:30 -04:00
root	0ddf67c754	Fix the remaining CSP errors. The repeated hash was from Next’s generated <Image> markup: style="color:transparent".	2026-07-01 23:52:09 -04:00
root	bcfe518af2	Fix the homepage CSP inline-style violations by removing React style attributes from the homepage app and moving them into CSS modules.	2026-07-01 23:33:37 -04:00
root	30631504f1	fix production domain	2026-07-01 22:51:46 -04:00
root	757ad41c9b	add image pull to production	2026-07-01 22:25:00 -04:00
root	97d5ecfcf0	pull docker image	2026-07-01 22:12:49 -04:00
root	63f8df1e38	fix production	2026-07-01 22:06:02 -04:00
root	e2b564aea5	fix prod	2026-07-01 09:18:14 -04:00
root	184a4bac8b	fix production storfront and homepage	2026-07-01 09:02:31 -04:00
root	9703de974a	fix api tests	2026-07-01 01:43:36 -04:00
root	5dfd5b1814	fix prod deployment	2026-07-01 01:37:37 -04:00
root	13d0512048	registry fix	2026-06-30 09:01:18 -04:00
root	b0c78ad8a2	registry fix	2026-06-30 08:49:09 -04:00
root	d8b7b92cb1	fixed registry secure	2026-06-30 01:38:01 -04:00
root	fb77e91730	fix registry creation image	2026-06-30 01:22:26 -04:00
root	9ad92765c1	fix test failure	2026-06-30 00:23:31 -04:00
root	f22e0d45e1	fix subscription page	2026-06-29 23:15:55 -04:00
root	a752a399c2	fix payment customer and dashboard settings	2026-06-29 22:15:34 -04:00
root	e1e2f55c93	add list of cities for car pick drop off locations	2026-06-29 20:32:08 -04:00
root	85d1aad956	fix test build cpu issue	2026-06-29 20:03:07 -04:00
root	26ab64e473	add test yml	2026-06-29 18:52:58 -04:00
root	1e100cf367	fix cpu dependencies	2026-06-29 18:25:10 -04:00
root	3d6607e6c8	make the booking in many steps	2026-06-29 08:54:41 -04:00
root	ae10f5272f	fix: resolve homepage unit test failures — React runtime, TS target, and pricing currency ... Three fixes: 1. React/ReactDOM version mismatch (root cause of 11 test failures): @testing-library/react (hoisted to root) resolved react-dom@18.3.1 from root node_modules, but homepage components use React 19. React 19 JSX elements cannot be rendered by react-dom 18, producing 'Objects are not valid as a React child' errors. Fix: added react-dom@^19.2.0 to root package.json, making root-level react-dom v19.2.7. @testing-library/react now resolves react-dom@19, matching the homepage's React 19 components. 2. TypeScript target (warning elimination): Changed homepage tsconfig target from ES2024 to ES2022. The installed Vite/esbuild version does not recognize ES2024. 3. Pricing currency test (test/configuration mismatch): The production pricing-config.ts uses currency 'MAD' (Moroccan dirham). Updated the test expectation from 'USD' to 'MAD' to match. Validation: - Focused tests: 6/6 files, 14/14 tests pass - Full homepage: 16/16 files, 51/51 tests pass - Full API: 150/150 files, 716/716 tests pass (no regressions)	2026-06-29 00:38:21 -04:00
root	a8472ddeed	fix: add emailVerified to employee test fixture and add unverified-employee negative test ... Root cause: the employee fixture used by the 'logs in active employees with a signed token and company context' test did not include emailVerified: true, so the auth.employee.service.login guard at line 108 correctly rejected the login with 401 email_not_verified. Changes: - Added emailVerified: true to the shared employee fixture - Added a new negative test that verifies login rejects employees with emailVerified: false (401 email_not_verified) The production email-verification guard in auth.employee.service.ts remains unchanged and strictly enforced.	2026-06-29 00:33:33 -04:00
root	6de0690b76	Fix the admin TypeScript error	2026-06-28 16:07:31 -04:00
root	0c9f3f8635	fix: resolve TS18046 errors for React 19 element props type ... React 19 types React.ReactElement props as unknown instead of any. Test helper functions that access element.props.children, .className, or .href need explicit props type parameters on React.ReactElement and isValidElement. Changes: - admin/PublicShell.test.ts: add WithChildren type, use React.ReactElement<WithChildren> - dashboard/PublicShell.test.ts: same pattern for childTypes and contentWrapper - dashboard/StatCard.test.ts: add ElementWithClass type for className access - dashboard/public-auth-pages.test.ts: add ElementWithHref type for href access No any, @ts-ignore, or type assertion bypass used.	2026-06-28 01:21:36 -04:00
root	8aab968e09	refactor: rename marketplace to storefront across the entire monorepo ... Comprehensive rename of all marketplace references to storefront: - API module: apps/api/src/modules/marketplace/ → storefront/ - Components: MarketplaceHeader → StorefrontHeader, MarketplaceShell → StorefrontShell, MarketplaceFooter → StorefrontFooter - Types: marketplace-homepage.ts → storefront-homepage.ts - Test files: employee-marketplace-* → employee-storefront-* - All source code identifiers, imports, route paths, and strings - Documentation (docs/), CI config (.gitlab-ci.yml), scripts - Dashboard, admin, storefront workspace references - Prisma field names preserved (isListedOnMarketplace, marketplaceRating, marketplaceFunnelEvent) as they map to database schema Validation: - API type-check: 0 errors - Storefront type-check: 0 errors - Dashboard type-check: 0 errors - Full monorepo type-check: only pre-existing admin TS18046	2026-06-28 01:14:46 -04:00
root	bffda95a7c	fix: resolve TS2339 jest-dom matcher errors in homepage tests ... Root cause: @vitest/coverage-v8@^4.1.0 forced vitest@4.1.9 into apps/homepage/node_modules, creating two vitest installations (v2 at root, v4 in homepage). @testing-library/jest-dom's vitest.d.ts augmented the root vitest v2 module, but homepage tests imported vitest v4 — so the type augmentation for matchers (toBeDisabled, toHaveAttribute, etc.) never applied. Fix: downgrade @vitest/coverage-v8 from ^4.1.0 to ^2.1.9 to match vitest 2.x used by the rest of the monorepo. This unifies vitest at v2.1.9 across all workspaces, allowing the jest-dom type augmentation to take effect. Validation: - npm ls vitest: single v2.1.9 installation (no nested vitest in homepage) - Homepage type-check (tsc --noEmit): 0 errors (all TS2339 resolved) - Existing setup.ts and vitest.config.ts were already correctly configured	2026-06-28 00:30:51 -04:00
root	ad88fe0148	fix: resolve TS2769 errors in invoicePdfService by eliminating duplicate @types/react ... Root cause: apps/api declared react@18 but @types/react@19, creating a nested apps/api/node_modules/@types/react@19.2.17 that conflicted with @react-pdf/renderer's type resolution from root node_modules/@types/react. Changes: - Removed react-dom from apps/api dependencies (unused) - Removed @types/react and @types/react-dom from apps/api devDependencies - Both API code and @react-pdf/renderer now resolve @types/react from a single root copy (v19), eliminating the TS2769 contextType incompatibility errors - Regenerated package-lock.json with deduped dependency tree Validation: - npm ls shows single @types/react installation - No nested @types/react under apps/api/node_modules - API type-check (tsc --noEmit): 0 errors - API build: succeeds - Docker build (Dockerfile.production): all 6 packages build successfully	2026-06-28 00:20:58 -04:00
root	df83c9876d	FIX PRODUCTION PAGES	2026-06-28 00:05:39 -04:00
root	abb3a18345	add: NEXT_PUBLIC_STOREFRONT_URL and NEXT_PUBLIC_HOMEPAGE_URL. Remove NEXT_PUBLIC_MARKETPLACE_URL.	2026-06-27 23:52:34 -04:00
root	a486f891cf	fix tests run	2026-06-27 23:40:40 -04:00