Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Training: Add production scripts #4

Open
stephlocke opened this issue Mar 13, 2017 · 11 comments
Open

Training: Add production scripts #4

stephlocke opened this issue Mar 13, 2017 · 11 comments

Comments

@stephlocke
Copy link
Member

For the skeleton docs (#1), have a script that produces them and sends to gh-pages branch or docs/

This could then be added to .travis.yml

@stephlocke
Copy link
Member Author

I'm thinking of trying to integrate this into the training projects - or adding a presentation package
https://github.com/lockedata/pres-stub
(blog post scheduled on how this works)

What do you think @jonmcalder

@jonmcalder
Copy link
Contributor

Looks cool to me - maybe I should wait to see the blog post, but for now I'm wondering how best to approach this given that some of the process/code infrastructure could or should be shared between this and #5?

I think modularity/extensibility is key in all of these building blocks for pRojects, given that the future plan is to come up with neat system for creating and maintaining personal templates for many of the pRoject parameters/settings etc as indicated in #14

In the case of this piece of functionality that would mean template values (including package dependencies where necessary) for things like the theme in _output.yml in addition to sourcing the applicable AUTHORNAME & AUTHOREMAIL params and allowing for override of the sample template etc.

Not sure if this feedback helps in any way?

@maelle
Copy link
Contributor

maelle commented Jul 9, 2018

@stephlocke
Copy link
Member Author

happy to use other packages that can help us get stuff CI/CDing easily, tho it needs to support non-web outputs fwiw

@maelle
Copy link
Contributor

maelle commented Nov 21, 2018

@stephlocke do you have an example of a repo whose setup you like?

I'm thinking of "simply" writing tic.R templates and using travis::use_tic().

@maelle maelle mentioned this issue Jan 25, 2019
Merged
@maelle
Copy link
Contributor

maelle commented Feb 5, 2019

Currently trying the setup with a PDF output. First time did not go well, trying now with an explicit install of texlive in the config file. That part is not supported by starters itself.

@maelle
Copy link
Contributor

maelle commented Feb 5, 2019

PDF output works if one adds this time-consuming line in before_install:


- sudo apt-get -qq update && sudo apt-get install -y --no-install-recommends texlive-full

at the moment I'm thinking this tweak should be documented in a vignette.

@maelle
Copy link
Contributor

maelle commented Feb 5, 2019

@stephlocke
Copy link
Member Author

didn't yihui make a tinytex or something 🤔 might be able to help keep the times down

@maelle
Copy link
Contributor

maelle commented Feb 5, 2019

yes but as far as I know if you install tinytex you need to install LaTeX packages by hand?

@stephlocke
Copy link
Member Author

I think the packages might autodeploy but regardless, it should be enough to compile the basics - if folks find they need full LaTeX then they can alter the process

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants