Re: [Fedora Infrastructure] #3860: Test box for Publican 3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



#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:3 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.

 Exactly! :)

 1. Docs uses Koji to build the docs RPMs
 2. A staging server installs those RPMs and generates the static website
 (this lives under /var/www/html/docs) (the machine requested in this
 ticket is a test box for exactly such a stage; if the test works as
 expected, the machine requested here could even be repurposed as the
 production stage)
 3. the contents of the stage's /var/www/html/docs directory get synced out
 to the rest of the world

 > * 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?

 Current (3.1) spec and tarball are here:
 https://fedorahosted.org/releases/p/u/publican/

 I've uploaded builds of publican itself and its web content subpackage
 (publican-common-web) to http://rlandmann.fedorapeople.org/publican-3.1/

 I maintain Publican in Fedora; I'm happy to maintain the el6-docs version
 of it too. (and also happy for comaintainers).

 Cheers

 Rudi

-- 
Ticket URL: <https://fedorahosted.org/fedora-infrastructure/ticket/3860#comment:7>
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





[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Red Hat 9]     [Yosemite News]     [KDE Users]

  Powered by Linux