New Octopus.cnf

Events happening in the community are now at Drupal community events on www.drupal.org.
AquaticDisorder's picture

I think the _USER variable being set in octopus.cnf was for me a source of confusion, it took me a while to realize why my OCTOPUS.sh settings weren't being honoured, don't get me wrong I know octopus.cnf is documented in CHANGELOG.txt, but I'm not sure it's best as a default setting because dealing with seperate satellite instances means re-configuring octopus.cnf and if forgotten attempts to install a new satellite instance go pear!
I have commented out _USER in octopus.cnf :)

Comments

Feel free to submit the

memtkmcc's picture

Feel free to submit the how-to to our docs/wiki in this group! :)

got bit by this

defiantbyte's picture

This might not be the right place for this comment, but this got me when trying to kick off another satellite instance for a different client. Along with the User variable you need to also comment out the domain variable or else it will point the o1 domain at the o2 aegir instance.

I probably don't have enough experience with the system yet, but would it make more sense to save the .cnf files under the user name? That way each Octopus instance can have a saved conf file for upgrades?

For example:
.user1.octopus.cnf
.user2.octopus.cnf

Then the script could look for the conf file related to the user set in the script.

Good idea. Could you post it

omega8cc's picture

Good idea. Could you post it as a feature request at http://drupal.org/project/issues/octopus ? Thanks.

BOA

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: