PDF download for .md and .tex files from blob and blob edit view
Let users download PDF versions of .md or .tex files from the:
- blob view
- blob edit view for the current textarea content they are editing (serving as a preview).
Convert `.md` to `.tex` via kramdown.
PDF is compiled from tex via texlive 2009 at push time (there would be a compile queue).
Add links to the compilation logs, and new views with the logs.
Preprocess logs to filter / highlight errors.
We can introduce only the kramdown dependency, and let interested users install texlive themselves.
**Economic Viability Analysis**
I know this is a big feature and it will have large maintenance cost, but it is also a big opportunity to get some money / attention to gitlab.com:
- this is a great feature that GitHub does not have.
They are now moving to publishing through GitHub Pages, but the real deal of publishing is PDF output. We should get there before them.
- there are already simpler services which are profitable doing only tex -> PDF conversion: https://www.sharelatex.com/project
GitLab is way more powerful in every other sense, so if we had such a feature, I am confident that people would be willing to pay money for it.
I propose the following business plan:
- under project / settings, you can turn PDF output on / off per project.
- PDF output is free only for public projects. You have to pay for private projects.
- count and limit compilation execution CPU time for public projects. You have to pay to go over a certain time.
Key components of Sharelatex have gone open source now, so we may try to reuse them: https://www.sharelatex.com
I am considering maintaining a live GitLab fork to test the feasibility of this idea, see comments for updates.
@Ciro OK, please keep me posted.
@Sytse: there could be collaboration with: OERPUB.
They have an editor frontend (in alpha) that exports to PDF / EPUB / HTML and communicates with GitHub via API. The editor: http://editor.oerpub.org/
They might be interested in interfacing with GitLab but I haven't talked to them yet.
Nice find Ciro, let me see if I can get in touch https://twitter.com/sytses/status/439498406449659905
I am not the first one to try this: https://banyan.co/
They are exactly the same thing as I want: GitLab hack for publishing
However I could not sign up, and they seem either dead or stealth.
If you can disclose this information:
What are the main stumbling blocks towards GitLab CI Cloud? (e.g. product immaturity, other pressing issues (which?) ).
Does GitLab Team have a public roadmap / "high priority" list?
I can sort of deduce some things from merged features and blog posts, but its hard to see further ahead.
Thanks for your positive response. Indeed there is now GitLab CI Cloud now and there won't be for some months. We might introduce a paid/freemium one in the future.
I am very glad you guys consider this.
I had just started looking into GitLab CI to achieve this in connection to the other thread: http://feedback.gitlab.com/forums/176466-general/suggestions/4522830-allow-access-to-build-artifacts-of-gitlab-ci
I haven't been able to find a "GitLab CI Cloud" like GitLab Cloud. It is only installable locally, is that it?
If so, we could consider this idea in the context of opening a freemium GitLab CI cloud.
Hi Ciro, thanks, I find softcover very interesting, it seems the best open source PDF renderer. I've talked to Michael Hartl about it and he is open to suggestions.
Any PDF rendering will need to be added to GitLab CI (not GitLab CE).
Thanks *A LOT* for that link, checking out right now.
I also like what https://www.softcover.io/ is doing to make PDF publishing easier. They have a pretty sweet toolchain for it.
I meant: https://github.com/sharelatex ....