#3860: Test box for Publican 3
---------------------+------------------------------------
Reporter: sparks | Owner: sysadmin-main-members
Type: task | Status: new
Priority: major | Milestone: Fedora 19
Component: Systems | Version: Test
Severity: Normal | Resolution:
Keywords: | Blocked By:
Blocking: | Sensitive: 0
---------------------+------------------------------------
Comment (by rlandmann):
Replying to [comment:4 sparks]:
> Replying to [comment:3 kevin]:
> > * Currently we pull from the docs git repo every hour and sync that to
our proxies. Under this new setup, changes would be committed to git, then
a koji build would be run, then we would need to sign/compose that build
into a repo and update the rpms. I can't see this happening every hour.
What is the desired update frequency on the produced docs packages?
>
> I think there is confusion here. What we would publish would be rolled
into an SRPM for koji and would not need to go to a git repo. The web
instance on the backend should be installing those packages that koji
built to then be sent to the proxies.
Correct
>
>
> > * I have 0 desire to install publican and it's dep stack on all our
proxy servers. Is there any way to take the content in the new git repo
and build the static files needed in one place and sync that out as
content instead of rpms? Building rpms in koji could be still done and
fine, we just don't need to use them ourselves.
>
> You shouldn't have to install publican on the proxy servers. The SRPMs
contain all the HTML data (and PDFs and ePubs) that goes to the backend
server.
Correct
>
> > * If there's no way to do what was in the last point, is there any way
one of the rpm subpackages could be the full content without requiring
publican?
>
> Unless the process has been completely misrepresented to me there isn't
a need to install publican on the backend. If I'm mistaken I wish someone
would draw me a picture because I just don't see it.
Almost correct. The backend server (the "staging server", ie, this box)
does need to run Publican, because Publican (running on the back end)
automatically generates and updates the site navigation pages. (For those
of us like Sparks who have built a site manually with Publican, this is
what happens during the "publican install_book" action; Publican is
triggered to do this in %post. Conversely, it runs its remove_book action
by %postun)
> > * Mention was made that publican3 is required and that you would want
to stay pretty bleeding edge on publican. Where is this el6 publican3
package? Who maintains it?
>
> I no longer have a RHEL box to play with but I know that P3 was built
for CSB. The builds exist *somewhere* if not already in EPEL.
Unfortunately, not in EPEL6 and never can be; we have perl deps that are
newer than what's shipped in RHEL6. This is why I've requested (and now
mostly have...) a separate buildroot for Publican 3 (this is el6-docs in
Koji) -- https://fedorahosted.org/rel-eng/ticket/5214 -- as soon as rel-
eng turns on SRPM builds there, that part is done.
Cheers,
Rudi
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/3860#comment:8>
Fedora Infrastructure <http://fedoraproject.org/wiki/Infrastructure>
Fedora Infrastructure Project for Bugs, feature requests and access to our source code.
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
