I'd really like to see this use Scap for deployment.

For our planning purposes, what kind of timeline should we plan for to be able to deploy the portal via scap3?

In T114694#1703156, @mmodell wrote:

I'd really like to see this use Scap for deployment.

If they want content on all Apache servers this seems like a job for scap/sync-dir today. All of the docroots are managed by scap in /srv/mediawiki/docroot

When we initially discussed it in #wikimedia-releng on IRC, there were shitloads of several conflicting opinions and disagreements, leading me to end up with an extreme lack of understanding, that is to say that I had/have essentially no clue what is actually desired and/or required.

If the portals are to live in /srv/mediawiki (which is what I originally suggested) and get deployed by wikidev, then indeed, it could be deployed with regular scap and there really isn't much to do here.

Again, during IRC discussion, there seemed to be a great deal of disagreement about whether it would be ok to require the help of a SWAT deployer to do the updates. I got the impression that the portals needed separate permissions, specifically, people without wikidev group membership should be able to deploy the portals, and do so independently from the mediawiki deployments.

Separate deployment groups, with separate shared ssh keys, is a feature that will be supported with Scap, however, it's unfortunately not ready to go quite yet. We could probably have that ready in the next week or two, optimistically.

In T114694#1730214, @mmodell wrote:

When we initially discussed it in #wikimedia-releng on IRC, there were shitloads of several conflicting opinions and disagreements, leading me to end up with an extreme lack of understanding, that is to say that I had/have essentially no clue what is actually desired and/or required.

Then perhaps as product owner I can clear up this confusion. :-)

If the portals are to live in /srv/mediawiki (which is what I originally suggested) and get deployed by wikidev, then indeed, it could be deployed with regular scap and there really isn't much to do here.

Again, during IRC discussion, there seemed to be a great deal of disagreement about whether it would be ok to require the help of a SWAT deployer to do the updates. I got the impression that the portals needed separate permissions, specifically, people without wikidev group membership should be able to deploy the portals, and do so independently from the mediawiki deployments.

That is the ideal. But it is not a requirement for the MVP.

Separate deployment groups, with separate shared ssh keys, is a feature that will be supported with Scap, however, it's unfortunately not ready to go quite yet. We could probably have that ready in the next week or two, optimistically.

I would prefer to go with regular scap then, and migrate over to scap3 (with all its nice features) later. This has taken much longer than I'd hoped, so if there's anything we can do to get it working sooner, I'd definitely want to go with that.

As far as I know this is ready to go on our end, I just need the go-ahead and I can start deploying this repo along with the train.

added @MaxSem as a subscriber as he is now leading up the backend portion of the portals work.

Does deploying MW with scap3 actually block this? Or can we migrate portals before we migrate MW itself?

portals are completely independent from MW, the submodule just happens to live in the mediawiki-config repository because that's also where the docroot used by our apache's lives. We can almost certainly migrate them before

Currently weekly portal deploys happen thanks to @Jdrewniak - how's the current process? Thanks.