heroku-buildpack-apt | This project | Platform As A Service library

Heroku apps run server-side. they're web apps. users interact with them through browsers.

if you wanted to access a user's webcam, that would have to happen through the browser. that requires WebRTC or similar APIs. that means serving a web page that contains client-side javascript (or other) code which accesses the user's webcam through the browser, and then sends a video feed (or single pictures) of that back to the server.

you can only directly access server resources inside the web app, not client-side resources.

if you wanted to do eye tracking browser-side, there's OpenCV.js which runs completely in the browser. I don't know if the required procedures for eye tracking have been ported to OpenCV.js but it's worth a look. you could do the analysis client-side and just send back heatmaps or lists of coordinates.

I guess generally the fixes work like this:

If you have library errors like libGL.so.1 you should take the name of the library in lowercase (in this case 'libgl'), add the number at the end (in this case it's '1') so you get libgl1 and write it in Aptfile.

My apologies for the delay. I am assuming you are using pip to install OpenCV. The answer to your question is that for OpenCV 3.x, Mac OS and Linux (and ultimately the environment that Heroku is run under) do not link with FFMPEG which means that video support is not enabled for those platforms. However, it is enabled with Windows. This is the reason why there is an inconsistency between the platforms: What is the deal with `pip install opencv-python` is it a full opencv?

The solution is you will either need to build OpenCV 3.x from source, or use OpenCV 4 which now bundles FFMPEG with it. I would highly recommend you use OpenCV 4 unless there is something blocking you from using it. However to install OpenCV 4, use either pip install --upgrade opencv-python or pip install --upgrade opencv-contrib-python. I'm not sure which flavour you are using, but either one should work.

I have managed to solve my error by adding the buildpack

The solution was:

First try git init in the Heroku console (step 5 & 6), maybe git is already installed. If not:

1. Install this buildpack
2. Add a Aptfile (txt) to the root, similar to a Procfile
3. Add latest git source url to the Aptfile
4. Deploy
5. heroku run rails c
6. `git init` in the console

1. Heroku directed me to this buildpack. Easy to install. But initially gave me this error, without too much explanation:

I managed to figure it out eventually.

For posterity, there are 2 solutions that worked for me :

1 - The not-so-good-one was to execute the g++ command on a Linux computer with exactly the same environment as the Heroku server, push it to Heroku and make sure to never modify it afterwards. You can then call fastBPE with a subprocess like above ==> it works, but it's more of a DIY unstable solution. The associated GitHub main file is https://github.com/Tony4469/xlm-agir/blob/master/mlm_tlm_prod.py

2 - The best solution was to precompile everything on a Docker container with a Miniconda environment, you can install and run all the necessary commands and then push it easily to heroku. You can find the Dockerfile I used here : https://github.com/Tony4469/laser-agir/blob/master/Dockerfile

Unfortunately, Heroku can’t send the appropriate voice packets to discord, therefore you must self host or use a vps to use music. Somebody did find a loophole but idk if it was patched but chances are you won’t be able to get music https://i.stack.imgur.com/LWcF4.jpg

I created a pull request to build the .NET Core project as a self-contained exe and delete the .NET Core SDK afterwards.

With that, I passed from a 304MB to a 149MB slug size!

Looks like node_modules has no effect...

Add the JVM buildpack to your app: