Website Deployment and GIS Uploads
- Role
- Built
- Status
- SHIPPED
- Stack
- AWS S3, Leaflet
The problem
Can a teammate update the website and GIS files without wrestling with S3 and AWS each time?
A fellow developer who runs the company website and a BI tool found uploading to S3 and pushing changes live slow and fiddly.
The system
- Folder and file upload to S3 with structure preserved, a preview of what will change, file browsing and cache clearing.
- Dedicated GIS upload pages, with Leaflet maps on three pages.
Engineering decisions
- Show what will change before writing
- A preview prevents accidental overwrites.
- Folder uploads keep their structure
- A whole landing page can go up in one step, exactly as built.
- Clear the cache from the same screen
- Updates go live straight after upload.
Impact
He drops the files in, they update and go live.
AHA Smart Homes screens on this site are recreated with dummy data.
Want to talk through how I built this?
I'm happy to walk through the decisions, what failed and what I'd change.