From: Rajko Albrecht <elektritter-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc - gitlab - authentication token
Date: Sat, 14 Oct 2017 00:59:11 -0700 (PDT) [thread overview]
Message-ID: <8994b4ee-2b9c-4b53-b6cd-109bfae40189@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
Hi, I searched for days and didn't found a solution.
I generate pdf from a gitlab project wiki. The markdown files are localy
checked out, so no problem using
pandoc wiki/home.md -t latex -o example.pdf
But the problem starts when the md has images insight which are rendered by
gitlab on access (pipline status etc.). Then I just get the error
[pandoc warning] Could not find image 'https://gitlab.xxxx/coverage.svg',
skipping ....
I tried various variants giving the authentication information to pandoc,
.netrc isn't read (and not usefull), gitlab requires a header
"PRIVATE-TOKEN: XXXXXXXXX" for download. With curl I can set it and it
works. Using wrapper script eg pipline does not work 'cause wiki pages are
stored inside a git.
So - is there any solution giving pandoc authorisation tokens on
commandline for retrieving remote content? I didn't found something in any
documentation...
Bye
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/8994b4ee-2b9c-4b53-b6cd-109bfae40189%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 3092 bytes --]
next reply other threads:[~2017-10-14 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 7:59 Rajko Albrecht [this message]
[not found] ` <8994b4ee-2b9c-4b53-b6cd-109bfae40189-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-16 3:28 ` John MacFarlane
[not found] ` <20171016032842.GB45185-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-10-16 5:15 ` John MacFarlane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8994b4ee-2b9c-4b53-b6cd-109bfae40189@googlegroups.com \
--to=elektritter-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).