Pat Allan on 01 Nov, 2014 10:59 AM
Sorry I've not responded to this sooner! (A combination of
jetlag, events and an out-of-control inbox).
Unfortunately there's nothing in place at this point in time to
directly support Flying Sphinx on EC2 without Heroku. Technically,
you could have an app sitting there in Heroku for just this
purpose, and use the appropriate environment variables on EC2 - I
can't see any reason why it wouldn't work - but the one catch is
that if the server your Sphinx daemon is on requires maintenance or
unexpectedly restarts (neither are super common, though they
certainly happen) then there's no way to notify your EC2 app that
the server address/port has changed.
If you're happy with that limitation (which would involve
updating your EC2 app manually in those situations) then I guess
that's an option. It's certainly not ideal though.
Could you enable something in which an email notification is sent about maintenance -- ideally beforehand when possible -- with the new parameters? That would make the EC2 option much less nerve-wracking...