FWIW, direct socket access via an ssh tunnel is allowed on OpenShift, so connecting to the remote REPL (either nREPL or Swank) is simple and requires no HTTP transport, but all of Phil's general advice regarding the remote disk applies there, too.
For an example, see http://immutant.org/news/2012/12/11/openshift-postgresql/ Jim Phil Hagelberg <p...@hagelb.org> writes: > On Tue, Dec 11, 2012 at 6:55 PM, Jonathon McKitrick > <jmckitr...@gmail.com> wrote: >> Well, I've used slime with SBCL for quite a while, but this is my first >> foray into clojure and heroku. Are you basically saying the best approach >> is just to edit locally, push to heroku, and run? > > I suppose if you ensure everything gets required when you boot your > app and you limit yourself to commands which operate on the region > rather than loading from disk (and avoid reloads) then you should be > fine. It's just easy to get into an inconsistent state between what's > on disk locally and what's in memory during any repl-driven > development; throwing in a third factor of the remote disk just adds > more room for error. > > -Phil -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
