I am an admitted 'newb' in the process of installing Springboard in the above environment (AWS EC2 Cloud Instance (server) running the Bitnami-Drupal LAMP Stack, v. 6.26). My assumption has been that it's possible for me to treat the install as "new" and install Springboard using the 'drush make' build file via github. It's appeared to have been working fine, although I did spend quite a bit of time in Drupal 7.18 before learning Springboard only operates with the D6 core.

But when I enter the EC2 domain name, the standard Drupal installation window opens, not Springboard's. I've tried going to /subdir, in this case "http://ec2-23-20-44-172.compute-1.amazonaws.com/drupal/htdocs/sites/all/..." and also tried "http://ec2-23-20-44-172.compute-1.amazonaws.com/drupal/htdocs/sites/all/..."... however both "return page not found".

Is it necessary to get rid of Bitnami altogether and build a standard drupal installation, then run drush make on the build file, or can I keep running the Stack and only change configuration, permission or database settings... or all three?

Thanks in advance,

Lee

Comments

Lee Gordon’s picture

Lee Gordon commented
Status: Active » Closed (works as designed)

Response kindly provided via Drupal/Springboard developer Allen Freeman:

"If you have a pre-existing Drupal instance it may be simplest to clone the springboard modules repo and then check out the 6.x-3.3-dev or rc1 branches directly into sites/all/modules. This avoids confusion with drush and gets you the latest version of Springboard."

Although I need to install, enable and configure modules individually, the installation appears stable. I look forward to fleshing out this site for a wonderful Rio orphanage unsupported by government funds in English, Portuguese and Spanish (German or French).

Lee