gl return null on Heroku
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 374
- PR merge metrics
- No merged PRs in 30d
Description
I'm currently facing the same error shown on https://github.com/mifi/editly/issues/33
I tried:
xvfb-run -s "-ac -screen 0 1280x1024x24" <node program>
But I got the error:
xvfb-run command not found
I got the core ffmpeg package working on Heroku using child_process module like following:
const { exec } = require("child_process");
exec(
"ffmpeg -safe 0 -f concat -protocol_whitelist file,https,tls,tcp -i ${urlListPath} -c copy ${outPath}",
(error, stdout, stderr) => {
...
});
How do I make editly run on a Heroku instance?
I'm using:
Node version: v14.7.0
Editly version: v0.11.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced issue #33 and reproducing the documented xvfb-run command in a Heroku environment using the reported Node and Editly versions. Trace how Editly launches its rendering process and verify whether the required display and ffmpeg dependencies are available; done means Editly can render successfully on Heroku or the unsupported requirements are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100