Thanks for this great AMI and tool to move data to persistent storage.
I hit a minor snag while installing. In your documentation you say that specifying
drupal_version=6.4
in the user data field ought to launch an instance with that version of Drupal. The instance comes up fine and I can SSH to it and see the Drupal install screen when I access the instance in the web browser. But no matter what user data I pass, the instance always comes up with Drupal 5.10.
I am using Elastic Fox to launch instances and it seems that the user data is not getting picked up. Is this a known problem, is there a typo somewhere or have a missed something?
TIA
Comments
Comment #1
akalsey commentedThis is indeed a bug. The version passed in the user data does not appear to affect the version of Drupal downloaded. It's getting 5.10 no matter what I use for drupal_version
Comment #2
jsteer commentedI have the same issue. I presume it has something to do with the fact that this is a hand-installed Drupal rather than one that uses the Fedora RPM's to do the install.
Any chance a 6.x version will be added ? I'd be happy with a separate 6.0 AMI..
This AMI is really handy for doing one-off experimentations. Launch the AMI, check out a module, kill the AMI.. $.10 is a cheap cost for this kind of experimentation.
Comment #3
robin van emden commentedJust got the AMI running, works perfectly!
But the possibility of installing 6.x versions would make a good thing even better...
Any chance of this in the near future?
Comment #4
akalsey commentedThis is solved now. Whatever version of Drupal you specify will now be installed.
The startup script creates a temp file with the user data in it and then reads from that temp file to get the installation parameters. We'd accidentally left the file on the AMI. This was causing the startup script to think it had already been run and wold install using the parameters that were in the file instead of those in the user data.