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.
Following up on #1468874: Split Eldir back out to a stand-alone project, we are thinking of splitting off hosting into a separate module back again.
The advantages are:
- people can more easily override the install profile by simply building their own and including hosting into it
- usage statistics will be published
- proper version numbers will be available here
The disadvantages are:
- we'll need to create more release nodes (see #1050618: Publish release nodes with tag message from corresponding Git tag to ease this)
- we have to change the hostmaster.make at every hosting release
- people will still be confused as to where to report issues
I am not sure it is worth it, and this will not be part of alpha1 just yet.
Comments
Comment #1
ergonlogicThe advantages speak for themselves, but I'll see if I can't rebut some of those disadvantages.
Yep, and that issue seems blocked on work in the 'project' project, and isn't linked to an issue under 'project', so it may be a while. Can we automate creating release nodes with Jenkins, maybe?
The two should probably be kept in sync, no? Even though hostmaster doesn't change much, it'll have to track changes in hosting.
People will likely always be confused by this. Short of starting an 'aegir' project just to triage issues, I don't see that this'll change.
Comment #2
anarcat CreditAttribution: anarcat commentedThat would require an account on Drupal.org with admin access to the projects.. Not sure Drupal.org people would like that. But it's an idea!
Hm... not necessarily. We *could* make the hostmaster.make file follow the latest hosting module, by not specifying a version, for example. Otherwise, yes, that means we need to release both every time.
I was hoping we could desynchronise away the hostmaster profile, since very little work happens there, the same way we don't need a new eldir release at every hosting release...
Comment #3
ergonlogicTo get a fixed platform build, a downstream makefile could just do:
So, I don't see any reason not to de-syncronise the components.
Comment #4
anarcat CreditAttribution: anarcat commentedThe problem here is that this will simply break "dev builds" - if the makefile specifies "use the latest version", then it will download the latest *stable* version and we won't be able to install aegir out of the box from git, unless we use a custom makefile.
In other words, hostmaster from git will not install hosting from git, but from stable. Ouch.
Comment #5
ergonlogicWell, we can pass in custom makefiles, right? To both 'hostmaster-install' and the .debs.
So, we could ship with a
hostmaster-dev.make
that has something like:Could that work?
Comment #6
anarcat CreditAttribution: anarcat commentedAh that's a good idea! Yes, it could just work! Then we'd need to fix the build scripts and documentation, otherwise this seems like a good idea.
Comment #7
ergonlogicI think this was partially blocked by #1917614: give ergonlogic access to the hosting module. That is, we didn't have control over adding maintainers to Hosting project. That's been fixed now though.
Comment #8
anarcat CreditAttribution: anarcat commentedi did this:
then i tried to do similar rebase than in the eldir mergeback, and failed:
I gave up there again, not sure why this is failing, again. So we just have a disconnected branch and that's it...
Now we need to change the makefile and remove the code from hostmaster.
Comment #9
anarcat CreditAttribution: anarcat commentedi have also moved over the 3.x branch. the remaining dev branches are ignored and left over to rot over to the hostmaster side. those includes the views integration stuff (#588728: Meta: Views integration redux), which will be rerolled in the hosting repo, and dev-1205458-move_sites_out_of_platforms (#1205458: Move modules/themes/libraries/files/private directories out of /sites/example.com), which will be rerolled if necessary. Other feature branches are either merged in or older than 12 months so considered dead.
Comment #10
anarcat CreditAttribution: anarcat commentedso this is only partly done. the problem we're having now is that a hostmaster install doesn't follow tags, unless we edit the hostmaster.make file on release, which is annoying (but may be the only option).
i reverted some work I tried to do to workaround all this, to quote:
we may postpone the proper fix to a latter alpha release, since this "works" now, it just installs any latest 2.x code...
Comment #11
anarcat CreditAttribution: anarcat commentedso this works: we have split hosting, now the only thing that remains is the release process, for which i'll create another issue (#2002114: fix release process and scripts).