Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.followed http://community.aegirproject.org/node/115 , create a platform on the remote, created a db, imported db, granted access, bootstraped site using a test vhost - worked. File permissions are aegir:aegir, so ran verify on the that platform, but the site does not get imported ( or ever get detected ).
Is that expected to be that way? ( only import sites on the aegir master? )
Comments
Comment #1
bwood CreditAttribution: bwood commentedI believe the hub-spoke model requires that we create all sites on the hostmaster server and then allow provision-verify to push the site to the remote web servers (spokes). I would attempt this import on the hostmaster server.
related: http://lists.aegirproject.org/pipermail/aegir/2011-January/000026.html
Comment #2
anarcat CreditAttribution: anarcat commentedI think that bwood's assesment is correct, but I would like this to be fixed in 2.0.
Comment #3
jpstrikesback CreditAttribution: jpstrikesback commentedsub
Comment #4
Steven Jones CreditAttribution: Steven Jones commentedIf we push more logic out to the remote servers, then that would naturally include drush, and some or all of provision, and then we could quite easily dump the DB and bring it back to the master for import.
Comment #5
Steven Jones CreditAttribution: Steven Jones commentedtagging
Comment #6
roxdra CreditAttribution: roxdra commentedHas this been fixed in current dev version of aegir-2.0? Any idea when would be stable aegir-2.0 be released?
Hub-spokes model is really not very mature in current 1.6 release.
Comment #7
ergonlogicNew features need to be implemented in Aegir 3.x, then we can consider back-porting to Aegir 2.x.