#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 kevin):
So after irc discussions last night I am trying to figure the best way to
handle things. :)
Some more questions:
* 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 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.
* 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?
* 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?
--
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/3860#comment:3>
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
