On Sat, 4 Mar 2017 17:01:43 -0700 Kevin Fenzi kevin@scrye.com wrote:
On Sat, 04 Mar 2017 18:44:55 -0500 Zach Oglesby zach@oglesby.co wrote:
On March 4, 2017 6:02:43 PM EST, Kevin Fenzi kevin@scrye.com wrote:
On Sat, 4 Mar 2017 23:56:56 +0100 "Brian (bex) Exelbierd" bex@pobox.com wrote:
On Mar 4, 2017, at 10:47 PM, Kevin Fenzi kevin@scrye.com wrote:
Greetings.
I know there's plans in progress to replace the fedoraproject docs, but the current process was:
Someone pulls docs git repo from fedorahosted Someone runs publican and pushes out the completed stuff to git repo. We sync that git repo and push it out to our proxies.
However, fedorahosted.org is now retired.
So, what do we want to do here?
- Setup a pagure repo that has the same data as the
fedorahosted
one
did and use that until we replace it.
- Just don't worry about it now, and try and get a replacement
pipeline in place.
- Something else.
The repos have all been migrated as far as I know.
Ah ha.
I missed it because of the name:
ok, thanks and sorry for the noise.
kevin
Publishing still happens from the fedorahosted repo unless some one changed it and I don't recall that happening.
Well, since fedorahosted is retired, there will not be any publishing from there. ;)
But if you mean infrastructure still pulls from there, yeah. I can change it to use the above pagure repo.
I'm afraid we don't have the same Publican web site data in https://pagure.io /docs-fp-o/ that used to be in https://git.fedorahosted.org/cgit/docs/web.git/log/ (which is no longer available).
Unless we get the data back from the old web.git repo, we won't be able to publish any new Publican content to http://docs.fedoraproject.org/, as documented in http://fedoraproject.org/wiki/Publishing_a_document_with_Publican.
I guess we should set up a temporary web.git repo in pagure and update the publish scripts for http://docs.fedoraproject.org/ accordingly.
Cheers, pk