CARULY / TECHNICAL REPORT
Caruly — Project Handoff
Start here to continue development on another computer.
1. Start Here
Back to contents ↑Caruly repository: https://github.com/ekatsov/Caruly
Website: https://caruly.com
This document is a portable project summary, not a synchronized chat transcript. It contains no account credentials, cookies, private user photos, or production data. The owner supplied six HTML reference reports. Their format informed this report; Caruly facts come from its source and verified project history.
2. Development Setup
Back to contents ↑Install a Node runtime satisfying package.json (currently >=22.18.0), clone the repository, run npm install, then npm start. The default port is 3000. On Windows PowerShell, use $env:PORT='3041'; npm start for the familiar preview port. Open http://127.0.0.1:3041 when using that port. APP_ORIGIN must match the browser origin for API writes; with no override the local server expects http://127.0.0.1 plus the configured port.
Run npm test. Run npm run backup for a daily SQLite backup. Do not copy production data into a public repository.
3. Current Experience
Back to contents ↑Demo plate 1111111 (also 6NDN265) returns the supplied 2009 Toyota Avalon, VIN 4T1BK36B89U340561. The displayed estimate is a sample, not a valuation service. Code 111 is a demonstration; no SMS is sent. Seller phone, name, and email gate the initial form. Returning sessions work in the same browser while its cookie remains available; cross-device account recovery is not implemented.
Photos: 12 categories, with four images for the tire category. Damage: eight Yes/No questions; Yes requires a saved photo. All No opens a confirmation. Inspection: 12 groups, including required Electrical/Transmission descriptions, modification photos for Yes, and individual tire dropdowns when tires differ. My Listings restores server-calculated progress.
4. Outstanding Work
Back to contents ↑Real SMS and account login/recovery; multiple vehicles; seller document uploads; minimum selling price; auction submission; real valuation/plate lookup; competing-offer submission; referral operations; off-site backups. Documents and price still open placeholders. Add Vehicle preserves the current draft and reports that multiple vehicles are pending.
5. Next-Developer Instructions
Back to contents ↑Read README.md and the Tech library, inspect git status, and run tests before editing. Keep changes local until the owner requests publication. A prior publish request authorized that particular release, not all later changes. Never include .env secrets or data/ in a commit. Do not claim demo verification is real authentication. Maintain Caruly branding; several informational/legal links still point to external reference sites and need owner review.
6. Release State
Back to contents ↑The last release before this documentation work was d23f62e. The Tech library and these documents are local additions until a separate publish operation is completed. Check GitHub/Render for the actual current revision rather than treating this historical note as deployment status.
7. Accomplishments And Release History
Back to contents ↑314689d: initial Caruly site and Render configuration.
a7414ec: vehicle information, offer form, condition and details.
420728c: seller name, email and optional referral.
b7dacc9: phone-gated contact fields and disabled Continue until valid.
c991a86: sample instant-estimate page.
2d28753: SQLite storage, owner-scoped photo uploads, disk and backups.
5dd7a87: eight-category damage page and saved damage answers/photos.
d23f62e: inspection flow and returning seller dashboard, including all-No confirmation, required damage photos, modification upload/capture, electrical/transmission descriptions, uneven-tire dropdowns and My Listings.
Current local work: Tech menu, six Caruly reports, multi-format preview/download library and library tests. Exact historical task start/finish times were not recorded; no elapsed durations are invented.
8. Test And Release Checklist
Back to contents ↑Run npm test, then exercise the changed browser path against the local Node server. Test drafts should be isolated from user listings. Publishing requires the owner's instruction. When publishing is authorized, commit only source/documents, push to the existing main branch, wait for Render, and verify the deployed revision with read-only checks. The previous live check verified current HTML, health, and anonymous session behavior. Creating synthetic production data was blocked by approval review; this is distinct from the successful deployment.
9. Sources And Maintenance
Back to contents ↑Prepared from the Caruly source tree and recorded development work on September 13, 2026. Reference report structure supplied by the owner. Update this snapshot when routes, schema, security, or deployment behavior changes. Do not copy unrelated project findings into this report.