3:47 p.m.
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.
kevin
4:56 p.m.
On Mar 4, 2017, at 10:47 PM, Kevin Fenzi <kevin(a)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.
Regards,
bex
>
> kevin
> _______________________________________________
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
5:02 p.m.
On Sat, 4 Mar 2017 23:56:56 +0100
"Brian (bex) Exelbierd" <bex(a)pobox.com> wrote:
> On Mar 4, 2017, at 10:47 PM, Kevin Fenzi <kevin(a)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:
https://pagure.io/docs-fp-o/
ok, thanks and sorry for the noise.
kevin
5:44 p.m.
On March 4, 2017 6:02:43 PM EST, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Sat, 4 Mar 2017 23:56:56 +0100
"Brian (bex) Exelbierd" <bex(a)pobox.com> wrote:
> > On Mar 4, 2017, at 10:47 PM, Kevin Fenzi <kevin(a)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:
https://pagure.io/docs-fp-o/
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.
6:01 p.m.
On Sat, 04 Mar 2017 18:44:55 -0500
Zach Oglesby <zach(a)oglesby.co> wrote:
On March 4, 2017 6:02:43 PM EST, Kevin Fenzi <kevin(a)scrye.com>
wrote:
>On Sat, 4 Mar 2017 23:56:56 +0100
>"Brian (bex) Exelbierd" <bex(a)pobox.com> wrote:
>
>> > On Mar 4, 2017, at 10:47 PM, Kevin Fenzi <kevin(a)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:
>
>https://pagure.io/docs-fp-o/
>
>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.
kevin
8:26 p.m.
On March 4, 2017 7:01:43 PM EST, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Sat, 04 Mar 2017 18:44:55 -0500
Zach Oglesby <zach(a)oglesby.co> wrote:
> On March 4, 2017 6:02:43 PM EST, Kevin Fenzi <kevin(a)scrye.com> wrote:
> >On Sat, 4 Mar 2017 23:56:56 +0100
> >"Brian (bex) Exelbierd" <bex(a)pobox.com> wrote:
> >
> >> > On Mar 4, 2017, at 10:47 PM, Kevin Fenzi <kevin(a)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:
> >
> >https://pagure.io/docs-fp-o/
> >
> >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.
kevin
Sorry was writing that just before taking off on a flight. As far as I am aware the git
repo for docs web is still configured to pull fedorahosted.
6:17 a.m.
On Sat, 4 Mar 2017 17:01:43 -0700
Kevin Fenzi <kevin(a)scrye.com> wrote:
On Sat, 04 Mar 2017 18:44:55 -0500
Zach Oglesby <zach(a)oglesby.co> wrote:
> On March 4, 2017 6:02:43 PM EST, Kevin Fenzi <kevin(a)scrye.com> wrote:
> >On Sat, 4 Mar 2017 23:56:56 +0100
> >"Brian (bex) Exelbierd" <bex(a)pobox.com> wrote:
> >
> >> > On Mar 4, 2017, at 10:47 PM, Kevin Fenzi <kevin(a)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:
> >
> >https://pagure.io/docs-fp-o/
> >
> >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
11:07 a.m.
On 03/06/2017 05:17 AM, Petr Kovar wrote:
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 can get the data back if you like. We still have it available.
I guess we should set up a temporary web.git repo in pagure and
update the
publish scripts for http://docs.fedoraproject.org/ accordingly.
ok. If someone does this, please let me know so I can change the pull
location in infrastructure.
It just seems bad to me that we currently don't have any way of updating
that content and don't seem to have the new setup ready yet.
kevin
6:23 p.m.
On 6/4/17 02:07, Kevin Fenzi wrote:
On 03/06/2017 05:17 AM, Petr Kovar wrote:
>
> 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 can get the data back if you like. We still have it available.
> I guess we should set up a temporary web.git repo in pagure and update the
> publish scripts for http://docs.fedoraproject.org/ accordingly.
ok. If someone does this, please let me know so I can change the pull
location in infrastructure.
It just seems bad to me that we currently don't have any way of updating
that content and don't seem to have the new setup ready yet.
If the system replacing publican isn't ready then it might be worth
considering a less cumbersome way of using publican for fdocs.
I think it'd be reasonably easy to get jenkins [1] to build the books,
say using a git trigger, rebuild the site, and push the site out to the
web head ... assuming ACLs can be set up to grant jenkins rights to scp
to the right place (assumes using [2] there are plenty of other plugins
for publishing artifacts).
This way you just push/tag the right way in the books/brands source
repos and some time later it appears on the site without the
intermediate git repo even existing. If it all goes pear shaped and you
need to regenerate the site from scratch for some reason, you just
manually trigger the scp or the builds as required.
Extra bonus is that Jenkins has EL7/F25 hosts, so you can switch to a
newer publican without affecting the infra team as the generated site is
OS agnostic, so no changes need to occur on the docs web hosts.
There maybe some effort required to fix books though as there are some
incompatibilities between older XML and publican major versions.
Cheers, Jeff.
1: https://jenkins.fedorainfracloud.org/
2: https://wiki.jenkins-ci.org/display/JENKINS/SCP+plugin
6:52 a.m.
I have been doing a POC on a new publishing method using the Budget
website. We are able to build the site and need to do some CSS cleanup
and automation.
I believe that we will be able to publish in AsciiDoc if we so desire,
possibly manually.
regards,
bex
On Thu, Apr 6, 2017, at 01:23 AM, Jeff Fearn wrote:
> On 6/4/17 02:07, Kevin Fenzi wrote:
> > On 03/06/2017 05:17 AM, Petr Kovar wrote:
> >>
> >> 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 can get the data back if you like. We still have it available.
> >
> >> I guess we should set up a temporary web.git repo in pagure and update the
> >> publish scripts for http://docs.fedoraproject.org/ accordingly.
> >
> > ok. If someone does this, please let me know so I can change the pull
> > location in infrastructure.
> >
> > It just seems bad to me that we currently don't have any way of updating
> > that content and don't seem to have the new setup ready yet.
>
> If the system replacing publican isn't ready then it might be worth
> considering a less cumbersome way of using publican for fdocs.
>
> I think it'd be reasonably easy to get jenkins [1] to build the books,
> say using a git trigger, rebuild the site, and push the site out to the
> web head ... assuming ACLs can be set up to grant jenkins rights to scp
> to the right place (assumes using [2] there are plenty of other plugins
> for publishing artifacts).
>
> This way you just push/tag the right way in the books/brands source
> repos and some time later it appears on the site without the
> intermediate git repo even existing. If it all goes pear shaped and you
> need to regenerate the site from scratch for some reason, you just
> manually trigger the scp or the builds as required.
>
> Extra bonus is that Jenkins has EL7/F25 hosts, so you can switch to a
> newer publican without affecting the infra team as the generated site is
> OS agnostic, so no changes need to occur on the docs web hosts.
>
> There maybe some effort required to fix books though as there are some
> incompatibilities between older XML and publican major versions.
>
> Cheers, Jeff.
>
> 1: https://jenkins.fedorainfracloud.org/
> 2: https://wiki.jenkins-ci.org/display/JENKINS/SCP+plugin
>
> _______________________________________________
> docs mailing list -- docs(a)lists.fedoraproject.org
> To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org
> Email had 1 attachment:
> + signature.asc
> 1k (application/pgp-signature)
10:24 a.m.
On Wed, 5 Apr 2017 10:07:39 -0600
Kevin Fenzi <kevin(a)scrye.com> wrote:
On 03/06/2017 05:17 AM, Petr Kovar wrote:
>
> 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 can get the data back if you like. We still have it available.
Thank you. I think we should get the data back just in case the new
publishing platform is not ready in time for the Fedora 26 GA release.
Actually, we might need to cover beta, as well?
Does anyone object to this?
> I guess we should set up a temporary web.git repo in pagure and
update the
> publish scripts for http://docs.fedoraproject.org/ accordingly.
ok. If someone does this, please let me know so I can change the pull
location in infrastructure.
Can you push the backup data to a new repo on pagure? Or, do we need to set
up a new repo first?
It just seems bad to me that we currently don't have any way of
updating
that content and don't seem to have the new setup ready yet.
Exactly.
Cheers,
pk
10:24 p.m.
On 04/06/2017 09:24 AM, Petr Kovar wrote:
On Wed, 5 Apr 2017 10:07:39 -0600
Kevin Fenzi <kevin(a)scrye.com> wrote:
> On 03/06/2017 05:17 AM, Petr Kovar wrote:
>>
>> 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 can get the data back if you like. We still have it available.
Thank you. I think we should get the data back just in case the new
publishing platform is not ready in time for the Fedora 26 GA release.
Actually, we might need to cover beta, as well?
Does anyone object to this?
>> I guess we should set up a temporary web.git repo in pagure and update the
>> publish scripts for http://docs.fedoraproject.org/ accordingly.
>
> ok. If someone does this, please let me know so I can change the pull
> location in infrastructure.
Can you push the backup data to a new repo on pagure? Or, do we need to set
up a new repo first?
I created and pushed the git info to:
https://pagure.io/fedora-docs-web/
I've made a few folks admins, hopefully they can add anyone else that
needs it or I can do so if asked.
I have switched infrastructure to pull from and publish this content
now, so changes there should take effect.
Let me know if there's anything else to do on this now...
kevin
7:05 a.m.
On Fri, 7 Apr 2017 21:24:55 -0600
Kevin Fenzi <kevin(a)scrye.com> wrote:
On 04/06/2017 09:24 AM, Petr Kovar wrote:
> On Wed, 5 Apr 2017 10:07:39 -0600
> Kevin Fenzi <kevin(a)scrye.com> wrote:
>
>> On 03/06/2017 05:17 AM, Petr Kovar wrote:
>>>
>>> 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 can get the data back if you like. We still have it available.
>
> Thank you. I think we should get the data back just in case the new
> publishing platform is not ready in time for the Fedora 26 GA release.
> Actually, we might need to cover beta, as well?
>
> Does anyone object to this?
>
>>> I guess we should set up a temporary web.git repo in pagure and update the
>>> publish scripts for http://docs.fedoraproject.org/ accordingly.
>>
>> ok. If someone does this, please let me know so I can change the pull
>> location in infrastructure.
>
> Can you push the backup data to a new repo on pagure? Or, do we need to set
> up a new repo first?
I created and pushed the git info to:
https://pagure.io/fedora-docs-web/
I've made a few folks admins, hopefully they can add anyone else that
needs it or I can do so if asked.
I have switched infrastructure to pull from and publish this content
now, so changes there should take effect.
Let me know if there's anything else to do on this now...
Thank you, Kevin. It turns out I'm unable to test the new repo with my old
Fedora 18 + publican 2 setup since pagure.io no longer allows for
connections with the dated ssh version shipped in F18...
pk
2560
days inactive
2607
days old
12 comments
6 participants
participants (6)
-
Brian (bex) Exelbierd -
Brian Exelbierd
-
Jeff Fearn -
Kevin Fenzi -
Petr Kovar -
Zach Oglesby