was originally using these buildpacks:
got this error when i pushed: Collectstatic configuration error. To debug, run …..
when i ran: heroku run …. collectstatic everything was fine!!!
so i had to patch the python buildpack: https://github.com/mattharley/heroku-buildpack-python/commit/807ac1344b01daa8ccc5da0774adeb55fae3b6f5
then i got when i pushed:
—–> Preparing static assets Traceback (most recent call last):
django.core.exceptions.ImproperlyConfigured: Could not import user-defined GEOMETRY_BACKEND “geos”.
so i found a newer fork of heroku-geo-buildpack which had two newer commit to fix everything:https://github.com/Tekco/heroku-geo-buildpack/commits/master
To this stack overflow post Heroku/Django: Could not import user-defined GEOMETRY_BACKEND “geos”
An acoustic cover version of Elton John’s Your Song for the first dance of a wedding
I like Leo Laporte‘s idea of 1-2-3 backup solutions.
- Local Copy – I keep anything local that i need to access quickly. every time i format the hard drive or buy a new computer, i only copy across the bare essentials. everything else, i grab from the external drive when needed.
- Cloud Copy – I use Backblaze for unlimited backup including external drives!
- Different Hard Drive – I use a simple rsync script, triggered nightly by a cron job, to backup to my external hard drive (which I plug in every night). The rcync script goes something like this:
#!/bin/sh rsync --progress --recursive -a --exclude="*.Trash*" --exclude="Downloads/*" /Users/matt/ "/Volumes/laptop-2tb/matt-2013/" Pretty simple hey?
Include the Libraries You Need
Firstly, if you jump directly into the API Reference, wherever you see the word library after the heading in the table of contents, e.g. Places Library, you need to make sure you load that library when you load the API.
Geocoding versus Places Search
Geocoding is the process of turning an address – e.g. 123 Fake Street – into a geographic point (latitude/longitude). If you want to search for a location by name – e.g. Lucky Donut Shop – similar to what you can do in the search box on Google Maps, you need to use TextSearchRequest in the Places Library. Here’s how I implemented a text search for places near the user’s current location:
Just to summarise our current situation:
- We have 1 Android and 3 iOs developers working hard on version 2 of the app
- These guys and me (sometimes) are the only people hitting the new API
- The new version of the app will be hitting the new AWS Elastic Beanstalk setup
Here are a few roadblocks and successes we hit along the way:
- Setup using this excellent guide from Grigory Kruglov but each of the .config files, change commands: from commands: to container_commands:. This cost be a few frustrating and headbangingly awful days
- The official docs get you started with a simple example, but in my opinion are really lacking
- The whole config system is wack. The options are spread across two seperate files and one of them seems to update from AWS at random times. Uhh, it sucks and leads to so many headaches.
One thing I wanted to talk about was cost. There’s a guide that is on the Amazon site which estimates costs at something ridiculous – in the $1000s of dollars – and way outside the range of a lean startup. You definitely want to monitor your expenses using a Cloudwatch alarm.
So far, Hpflsk has been charged around $50 AUD a month with only a grand total of 5 people hitting the API regularly. This includes the free tier. This may seem like not that much, but it definitely discourages developers from creating a bunch of apps and seeing what sticks – which seems to be the lean startup model. So if you want to keep everything super lean and mean, you’re better off with a VPS (~$100 AUD per year). It’s that not much of a pain in the ass to setup – took me around a day – and can be used to host multiple projects.
edit: sorry, was playing around with If That Then That