On 12/09/2017 11:51 PM, Robert Varga wrote: > On 10/12/17 00:47, Andrew Grimberg wrote: >> The bailing wire and bubble gum that is making javadocs.opendaylight.org >> function properly does not make it possible to have a domain name per >> project. Plus it would be an extra amount of administrative overhead on >> us to do this as it would require extra configuration of puppet >> configuration for each project if I could figure out the extra magic needed. >> >> Each of the projects can be referenced at >> https://javadocs.opendaylight.org/${project_short_code} which maps to >> the actual official URL of >> https://javadocs.opendaylight/${group_id}.${project} > > Fair enough, though there is one slight snag -- maven javadoc plugin is > relying on javadocs to be present at a fixed location, > ${project.url}/apidocs. I am not sure what else the project's URL is > used for -- right now we point to the project's wiki page. > > Would it be possible to add some URL rewrite scheme on the > infrastructure side, so that we can pretend to the outside world we have > a mavenesque per-project structure (say, > http://opendaylight.org/yangtools/) and remap requests to appropriate > hosts (say, http://opendaylight.org/yangtools/**/apidocs -> > javadocs.opendaylight.org/yangtools/)?
Given what I know about our website (www.opendaylight.org) I know we can't put that in place. It would all be manual updates for every project and it's not something that the Release Engineering team can do as we have no control over the website itself. As I stated, you've already got a fixed location for the projects on javadocs. I'm wondering if it would be apropos to move the project info from the wiki into the projects themselves and have a static site get built that gets pushed to another site repo on the nexus system with some magic similar to the javadocs repo. We would be able to add in some extra rewrites on the Apache site handler for it to rewrite **/apidocs to the javadocs site then. Perhaps projects.opendaylight.org This would give you the benefit of making sure that your Committer information and such isn't getting gamed by someone that isn't a committer. Not that we've run into that. I know that we're currently working with OPNFV (and ONAP is interested in) a YAML configuration INFO file for project stats that would make it possible to automate a lot of stuff like basic site creation and reporting. See [0] for the current proposal to OPNFV. -Andy- [0] https://gerrit.opnfv.org/gerrit/#/c/48413/ -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/infrastructure
