Proton allows users to download a Wikipedia article as PDF. It supports both desktop and mobile-friendly prints.
- Queue system that queues all requests (as PDF generation is both resource and time-intensive job)
- Renderer code which instructs Puppeteer to print requested page as PDF.
PUPPETEER_EXECUTABLE_PATH environment variable is used to point to chromium executable.
Note: for some users, the PDF they get from browser print and the one they get from Proton service might differ a bit as fonts configuration on user system can have specific settings related to fonts hinting/kerning.
The Queue system is the heart of Proton renderer. It handles the flow of each job through waiting/processing/timeout logic. Each job in the queue can have two states - waiting and processing. The queue system not only allows a specific amount of jobs to run at the same time but it also handles job timeouts and job cancellation. Because of the queue complexity, we had to implement the solution that allows us to:
- limit the number of waiting jobs
- after a defined amount of seconds reject the waiting job
- limit the number of rendering jobs (as PDF rendering requires lots of resources)
- a safety net to reject rendering jobs that takes too much time
- to save resources, when the request is aborted queue will try to cancel the job, doesn't matter which state the aborted job is (processing/rendering).
The Renderer is a simple facade to access
page.pdf() method from puppeteer library. Renderer is responsible for setting proper chromium environment and browser viewport, requesting the Wikipedia page, calling the
page.pdf() function. Plus it keeps an eye on the browser process. Each render starts new Chromium instance, and after successful render, the chromium process exits. To save resources, and keep our system in good state Renderer asks Chromium to shut down and if because of any reason browser still keeps processing the request it will send the
SIGKILL to browser process to make sure it doesn't use any more CPU nor the memory.
When a job fails because the queue is full or job timeouts in any state the Proton service will return
503 Service Unavailable response with Retry-After header. The Retry-After header instruments load balancer to depool given Proton node so it can finish processing current jobs. System sets Retry-After header to
app.config.render_queue_timeout configuration value. After that time all processing jobs should finish, and the system should be able to pick up new jobs.
Proton utilizes the BBPromise cancellation feature. Cancellation feature is disabled by default, to enable promise cancellation BBPromise.config() has to be called with
cancellation:true flag. The trick is that the BBPromise config has to be set before any promise is created. But because Proton uses the Service-runner, and Service-runner uses BBPromises for everything, even reading configuration files this wasn't easy to implement. The
cancellation flag cannot be set in the Proton application, because the Proton code is executed after Service-runner initialization. It also couldn't be defined in config, as Service-runner uses promises when reading the config. In version 2.6.6 of Service-runner introduces use of the
APP_ENABLE_CANCELLABLE_PROMISES environment variable, which has to be set to truthy value.
If the environment variable is not set, Proton initialization will fail with error.
Development happens in the Proton service Git repository. Code review happens in Gerrit. See Gerrit/Getting started to set up an account for yourself. Service uses the ServiceTemplateNode project template and follows all Service development rules.
Running the testsEdit
To run all swagger tests and mocha tests:
To run all coverage test:
npm run coverage
- README.MD has the documentation about Proton internals and configuration variables.
- ServiceTemplateNode/Deployment How to deploy Proton service
- Reading/Web/Projects/Print_Styles Print styles and limitations are identical to Browser print styles.