Recherche avancée

Sur d’autres sites (13273)

• How To Install FFMPEG on Elastic Beanstalk

  26 mars 2020, par Nick Lynch

  This is not a duplicate, I have found one thread, and it is outdated and does not work :
  Install ffmpeg on elastic beanstalk using ebextensions config.

  I have been trying to install this for some time, nothing seems to work.
  Please share the config.yml that will make this work.

  I am using 64bit Amazon Linux 2016.03 v2.1.6 running PHP 7.0 on Elastic Beanstalk

  ---

  My current file is

  branch-defaults: 
  
    default: 
  
      environment: Default-Environment
  
    master: 
  
      environment: Default-Environment
  
  global: 
  
    application_name: "My First Elastic Beanstalk Application"
  
    default_ec2_keyname: ~
  
    default_platform: "64bit Amazon Linux 2016.03 v2.1.6 running PHP 7.0"
  
    default_region: us-east-1
  
    profile: eb-cli
  
    sc: git
  
  packages: ~
  
  yum: 
  
    ImageMagick: []
  
    ImageMagick-devel: []
  
    commands: 
  
      01-wget: 
  
        command: "wget -O /tmp/ffmpeg.tar.gz http://ffmpeg.gusari.org/static/64bit/ffmpeg.static.64bit.2014-03-05.tar.gz"
  
      02-mkdir: 
  
        command: "if [ ! -d /opt/ffmpeg ] ; then mkdir -p /opt/ffmpeg; fi"
  
      03-tar: 
  
        command: "tar -xzf ffmpeg.tar.gz -C /opt/ffmpeg"
  
        cwd: /tmp
  
      04-ln: 
  
        command: "if [[ ! -f /usr/bin/ffmpeg ]] ; then ln -s /opt/ffmpeg/ffmpeg /usr/bin/ffmpeg; fi"
  
      05-ln: 
  
        command: "if [[ ! -f /usr/bin/ffprobe ]] ; then ln -s /opt/ffmpeg/ffprobe /usr/bin/ffprobe; fi"
  
      06-pecl: 
  
        command: "if [ `pecl list | grep imagick` ] ; then pecl install -f imagick; fi"

• How To Install FFMPEG on Elastic Beanstalk

  13 avril 2017, par Nick Lynch

  This is not a duplicate, I have found one thread, and it is outdated and does not work :
  Install ffmpeg on elastic beanstalk using ebextensions config.

  I have been trying to install this for some time, nothing seems to work.
  Please share the config.yml that will make this work.

  I am using 64bit Amazon Linux 2016.03 v2.1.6 running PHP 7.0 on Elastic Beanstalk

  ---

  My current file is

  branch-defaults: 
  
    default: 
  
      environment: Default-Environment
  
    master: 
  
      environment: Default-Environment
  
  global: 
  
    application_name: "My First Elastic Beanstalk Application"
  
    default_ec2_keyname: ~
  
    default_platform: "64bit Amazon Linux 2016.03 v2.1.6 running PHP 7.0"
  
    default_region: us-east-1
  
    profile: eb-cli
  
    sc: git
  
  packages: ~
  
  yum: 
  
    ImageMagick: []
  
    ImageMagick-devel: []
  
    commands: 
  
      01-wget: 
  
        command: "wget -O /tmp/ffmpeg.tar.gz http://ffmpeg.gusari.org/static/64bit/ffmpeg.static.64bit.2014-03-05.tar.gz"
  
      02-mkdir: 
  
        command: "if [ ! -d /opt/ffmpeg ] ; then mkdir -p /opt/ffmpeg; fi"
  
      03-tar: 
  
        command: "tar -xzf ffmpeg.tar.gz -C /opt/ffmpeg"
  
        cwd: /tmp
  
      04-ln: 
  
        command: "if [[ ! -f /usr/bin/ffmpeg ]] ; then ln -s /opt/ffmpeg/ffmpeg /usr/bin/ffmpeg; fi"
  
      05-ln: 
  
        command: "if [[ ! -f /usr/bin/ffprobe ]] ; then ln -s /opt/ffmpeg/ffprobe /usr/bin/ffprobe; fi"
  
      06-pecl: 
  
        command: "if [ `pecl list | grep imagick` ] ; then pecl install -f imagick; fi"

• FFMPEG on Heroku exceeds memory quota in testing

  5 juillet 2022, par Patrick Vellia

  After following this tutorial, and getting it to work locally on my own development environment, before really getting my hands dirty and working deeper on my own project implementation, I decided to push it up to Heroku to test in a staging environment.

  


  I had to have Heroku add the FFMPEG build-pack and turn on the Redis Server for ActionCable to work.

  


  I didn't link the staging to a cloud storage bucket on Google or Amazon yet, just allowed it to upload directly to the dymo disk for testing. So it would go into the storage directory as it would in development for now.

  


  the test MOV file is 186 MB in size.

  


  The system uploaded the file fine.

  


  According to the logs, it then copied the file from storage to tmp as the tutorial has us do.

  


  Then it called streamio-ffmpeg's transcode method.

  


  At this point, Heroku forcibly kills the dymo because it far exceeds the memory quota.

  


  As this is a test environment, it's only on the free tier of Heroku.

  


  I'm thinking I won't be able to directly process video projects on Heroku itself, unless I'm wrong ? Would it be better to call an API like Cloud Functions or Amazon Lambda, or spin up a Compute Engine long enough to process the FFMPEG command ?