Well, my script appears to be working, and as a result there are ~50 files in markdown format to upload to make our SF wiki have content that is virtually the same as our miscdebris wiki. Only problem is, I don't know of an efficient way to upload those files (and re-upload them if my script needs a further adjustment). (Of course, I could use cut and paste to fill in the SF form, but that is too error prone/tiring to be my first choice).
The very terse documentation at <http://sourceforge.net/p/forge/documentation/Allura API/> says the following about downloading/uploading wiki content: Endpoint: /rest/p/project_name/mount_point/ GET /rest/p/project_name/mount_point/ - returns a list of page titles GET /rest/p/project_name/mount_point/title - returns a JSON representation of a page POST /rest/p/project_name/mount_point/title - creates or updates the titled page parameter text: page text parameter labels: comma-separated list of page labels > From a one-line comment further on I can infer that for the PLplot wiki, the full URL corresponding to the above is https://sourceforge.net/rest/p/plplot/wiki and indeed if I wget that, I get the complete list of pages currently on that wiki, and if I access one of those pages like wget https://sourceforge.net/rest/p/plplot/wiki/Building_PLplot I do download a file named Building_PLplot with a JSON representation of that wiki page. So far so good! But what is the URL syntax you use for POST requests as "documented" above. Is it just https://sourceforge.net/rest/p/plplot/wiki/Building_PLplot?text=<full contents of local file> ? Surely that cannot be correct since that would be an enormous URL. In any case, I am not too interested in just posting text that way because pasting text is bad for 50 different files, and in any case there is a perfectly fine SF GUI to paste text if I want to fall back to that bad method of mass uploading. So from the above information, can you infer some way to use the POST method with a local filename that would be interpreted as "upload the contents of the file whose name is given by <filename>". If you can come up with something like that, it would be much easier for me to cut and paste file names compared to cutting and pasting contents of those files. The above may seem like a trivial question to you guys, and also the SF types that wrote the above "documentation" of the POST method thought that documentation should be enough, but I don't really know how to use a POST method so assume I am a complete newbie at doing that (which is the case), so any newbie-style help you can give me with the above question or any other ideas would be appreciated. If there is a simple answer with wiki file uploads using just a URL, that would be great because then I could post that URL in my iceweasel browser session that is already logged into SF which authenticates my POST requests. However, there is another so-called oauth method of obtaining authentication tokens, and the above documentation URL shows how to use that method from a python script. But the oauth gui that is referred to <https://sourceforge.net/auth/oauth/> simply asks you to register by name (which you have to spell out with no menu saying what application names would be appropriate here) applications that I want to authorize on my behalf. However, I have no clue what any of this security babble means, so if anyone does have a clue, please speak up! Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ _______________________________________________ Discuss mailing list disc...@vlug.org http://lists.vlug.org/mailman/listinfo/discuss ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
