caspg
Joined 11 years ago
Joined 11 years ago
- Phoenix controllers for static content (route guides, listings)
- Phoenix LiveView for most of the forms
- React for the planner and interactive maps where high performance is critical
One of the bigger technical challenges was self-hosting all the infrastructure - I'm running my own map tile server and routing engine (Graphhopper) on beefy servers with lots of RAM to maintain full control over the cycling-specific routing algorithms. The memory requirements are substantial, especially for processing large-scale route data across multiple regions.
This approach lets me customize the routing to prioritize official cycling routes while still giving users flexibility when planning custom segments.
Happy to dive deeper into any specific aspect if there's interest!
So pretty simple flow, totally not scalable for bigger projects.
I need to read and check Cursor AI which can also use Claude models.
At least 95% of the code was generated by AI (I reached the limit so had to add final bits on my own).
EDIT: As for plans for veloplanner, I'll be adding some of the interactive features (comments etc) as LiveView.
https://www.linkedin.com/in/kacper-golinski-78aa3866