Yeah absolutely right, I'm just using the pipeline for my static files (i.e. styles, images, js) not for data pages. One more caveat I forgot to put in the post but should be mentioned is the collectstatic command. If you have a huge collection of static assets, collectstatic is painfully slow copying its files directly to the S3 bucket. In my case, I don't have a huge number of assets so it's not a big issue, but if anyone has any ideas for making collectstatic faster, I'd love to hear them
Of course. So a lot of things are in the works right now, but in a nutshell, I'm currently scraping data about (nearly) every taxi company in the U.S and feeding that data into an admin panel which lays out the data in a way conducive to finding items which have been reported as lost in a given geographical area..theres still a lot of work to be done on that front, but that's the core concept...as for scaling, yes I definitely think it has the potential to be globally scalable in the future, but for the moment I'm concentrating on the U.S as a proof of concept...if I can get it working here, though, I would definitely be interested in introducing it globally later.