Comments (5)
@codingjoe thanks so much for the help! It's extremely useful to have this container for testing. The \includegraphics worked on it, so I guess on heroku it must be an issue with the image file or it's path or something along those lines, so we can probably close the issue.
from heroku-buildpack-tex.
@sschloesser I don't know if it might be helpful for your case but we had also an issue where some graphics stopped working with \includegraphics
. In our case it was because the graphics were some generated thumbnails and somehow TeX Live 2017 had a problem with that. Our fix was installing TeX Live 2016 because there it worked. You can tell the buildpack the path it should use for the installer. just how it is documented here: https://github.com/Thermondo/heroku-buildpack-tex#custom-tex-live-version
Maybe that helps your case as well. Btw, if it does help, please make sure you are referencing the buildpack in heroku with the version number because we might soon introduce a breaking change where the file path is changed. Just as a heads up.
from heroku-buildpack-tex.
@sschloesser it always uses the latest version by default. But you can freeze the repo to a certain version, as @anneFly suggested.
from heroku-buildpack-tex.
Hi @sschloesser I know debugging these can be hard. I did setup a little docker based test suite right here: #18
I would recommend adapting it to your needs and building it locally to debug your issues.
Here is how you can do that:
- Checkout the
tests
branch. - Add your
texlive.profile
ortexlive.packages
file to the repo root. - Run
docker build . -t heroku-tex
- Run
docker run -ti -v PATH/TO/TEST/TEX/FILE/DIR /app/examples heroku-tex
That will put you inside a heroku container with your exact packages installed. Can can than run your TeX commands and debug whatever is wrong.
I hope that helps you :)
Let me know if I can be of further assistance,
-Joe
from heroku-buildpack-tex.
Thanks @anneFly for the heads up! It turned out the problem was that I was using quotes around the image path \includegraphics{"path/to/image.png"}
and removing them fixed it. So this buildpack changed from using Tex Live 2016 to 2017? Maybe that's what broke it because it was working before.
from heroku-buildpack-tex.
Related Issues (13)
- handle release-upgrades (texlive 2012 -> 2013) HOT 12
- Use xelatex in addition to pdflatex HOT 1
- Testissue
- Stuck on 2012 HOT 2
- Trouble with fonts HOT 5
- Installation breaks after Make Install when calling tlmgr HOT 3
- Disable updating of tex live and tlmgr HOT 2
- Custom TeX live version - No access to cryptographic signature HOT 5
- option to pick mirror
- Buildpack breaks on Heroku's new Cedar-14 stack HOT 6
- How to use xelatex engine? HOT 1
- use binary wget for better compilation time HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from heroku-buildpack-tex.