Hey,
I noticed we still have v1 API there. How do we generate that?
LZ
···
-- Later,Lukas “lzap” Zapletal
irc: lzap #theforeman
Hey,
I noticed we still have v1 API there. How do we generate that?
LZ
Lukas “lzap” Zapletal
irc: lzap #theforeman
If you are development, it will automatically generate the docs if you go to URL /apidoc
In production, I think the static doc files need to be first be generated by a rake task from apipie and then go to /apidoc
rake apipie:static
Joseph
Hey,
I noticed we still have v1 API there. How do we generate that?
LZ
–
Later,
Lukas “lzap” Zapletal
irc: lzap #theforeman
–
You received this message because you are subscribed to the Google Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Sorry Joseph for not being verbose
I mean this: Foreman
Do we have a Jenkins job for generating this?
LZ
–
Later,
Lukas “lzap” Zapletal
irc: lzap #theforeman
No, it needs updating in the web site repo, theforeman.org.
When I briefly looked while doing 1.2, I could generate static
documentation for a single version, so was thinking to generate it once
for v1, again for v2 and then add a dropdown menu to the site (like the
manuals link) to select the one you want.
The dynamic documentation has a link though between the two, so is this
just a limitation of the static docs?
–
Dominic Cleal
Red Hat Engineering