Google appengine best way to get rails running

Ruby JRuby
1

anyone has experience to get rails running on google appengine - as
ORM I will use datamapper since there is dm-appegine-adapter
available.

using warbler and add everything I need.

or

is it better to use Google Code Archive - Long-term storage for Google Code Project Hosting.

???

any one knows some maven support for the very same tasks.

thanx in advance
Kristian

To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
2

I’d say that the best option is to follow the instructions here

http://code.google.com/p/appengine-jruby/wiki/RunningRails

There are descriptions of other options floating around, but the
appengine-jruby project is actively developed.

//Peter
http://peter.lind.be

3

On Thu, Jan 21, 2010 at 4:41 AM, kristian [email protected] wrote:

???

any one knows some maven support for the very same tasks.

I have no experience for getting App Engine up and running, but I have
seen
it compared a lot
with Heroku http://heroku.com which is a Ruby Native cloud computing
environment.

4

I’d ensure that you’ve considered data migration options before fully
committing to GAE for serious apps. Just a heads up - it’s easy to get
started but who owns your data?

On 24 Jan 2010 17:39, “Ikai L.” [email protected] wrote:

App Engine and Heroku are similar in that they emphasize ease of
deployment.
You can have a development application literally pushed in less than 5
minutes.

Where App Engine and Heroku differ are in the persistence mechanisms.
Heroku
provides a MySQL instance, which, for most developers, is more than
adequate. App Engine provides a datastore layer that sites on top of
Google’s BigTable technology: a distributed key/value store.

As such, the biggest challenge for developing a truly scalable
application
on App Engine is understanding how to build and persist data in a
non-relational manner. Both appengine-jruby is maintained primarily by
Googlers, though not in an official capacity, and also uses data mapper
for
persistence.

On Thu, Jan 21, 2010 at 8:14 AM, Richard C.
[email protected]

5

App Engine and Heroku are similar in that they emphasize ease of
deployment.
You can have a development application literally pushed in less than 5
minutes.

Where App Engine and Heroku differ are in the persistence mechanisms.
Heroku
provides a MySQL instance, which, for most developers, is more than
adequate. App Engine provides a datastore layer that sites on top of
Google’s BigTable technology: a distributed key/value store.

As such, the biggest challenge for developing a truly scalable
application
on App Engine is understanding how to build and persist data in a
non-relational manner. Both appengine-jruby is maintained primarily by
Googlers, though not in an official capacity, and also uses data mapper
for
persistence.