-
Notifications
You must be signed in to change notification settings - Fork 6
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
Puppeteer to gotenberg #1059
Puppeteer to gotenberg #1059
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It just works, really nice work!
Just one minor thing besides the one comment, there are a few other docker-compose files in this repo (in docs and and the test scripts thing), could you adapt these, too?
server/config/production.yml
Outdated
puppeteer: | ||
# Settings used for the gotenberg instance | ||
gotenberg: | ||
host: 'http://localhost' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you sure?
in production this should be deployed via docker / k8s, right?
shouldn't this then be sth like gotenberg or so (depending on one names the docker container)?
see above for database, there it is named tms_sql
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I adapted the files, hopefully as expected.
There are also mentions of puppeteer in the dockerfile and some docs files that reference build-test-docker/buildAndTestDocker.ts script as it existed only because of puppeteer. Should it be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbh lets just get rid of it
🎫 Description
Replace puppeteer with gotenberg