Sur d’autres sites (12630)

• Upload audio file, convert bitrate, save to S3 | server side options ?

  29 septembre 2011, par Jonathan Coe

  Currently using PHP 5.3.x & Fedora

  Ok. I'll try to keep this simple. I'm working on a tool that allows the upload & storing of audio files on S3 for playback. Essentially, the user uploads a file (currently only allowing mp3 & m4a) to the server, and the file is then pushed to S3 for storage via the PHP SDK for amazon aws.

  The missing link is that I would like to perform a simple bitrate & format conversion of the file prior to uploading the file. (ensuring that all files are 160kbs and .mp3).

  I've looked into ffmpeg, although it seems that the PHP library only allows for reading bitrates and other meta, not for actual conversion.

  Does anyone have any thoughts on the best way to approach this ? Would running a shell_exec() command that performs the conversion be sufficient to do this, or is there a more efficient/better way of doing this ?

  Thanks in advance ! Any help or advice is much appreciated.

• Berlin website owners need consent for using Google Analytics

  19 novembre 2019, par Joselyn Khor — Uncategorized

  Website owners in Berlin need consent for using Google Analytics

  According to the Berlin Data Protection Office, if you’re a website owner collecting and sending data to third-party services (like Google Analytics) who are also using that data “for own purpose uses” in Berlin, you are now required to ask for specific consent from visitors in order to collect that information. 

  This means you can only use Google Analytics or similar services once you’ve gotten consent from visitors. In contrast, Matomo does not use information from Cloud or On-Premise users for “own purpose uses”.

  Consent is also needed when keystrokes or mouse movements are recorded. That means you need users to consent to your usage of features like Heatmaps and Session Recordings.

  It’s advised that website owners in Berlin should check their websites for third-party content and tracking mechanisms. If you do use these third-party functions that require consent, you must either get consent or remove the functions. Consent is only effective if the visitor (whose data you’re collecting) is informed and agrees to their data being processed.

  Currently this applies to website owners in Berlin, and should likely be applied for the whole of Germany to be on the safe side.

  Further reading :

  • Learn more about Matomo’s Cloud Data Processing Agreement
  • Read about asking for consent in Matomo
  • To use Matomo Analytics and be compliant with the regulation we recommend you learn how to make Matomo GDPR compliant in 12 steps.

  And learn more about all the features in our GDPR user guide and privacy user guide. You can also learn more about GDPR through our blog posts.

• How to debug GitHub Action failure

  9 décembre 2022, par Meltemi

  Just yesterday a stable GitHub Action (CI) started failing rather cryptically and I've run out of tools to debug it.

  


  All I can think of is our BUNDLE_ACCESS_TOKEN went bad somehow but I didn't set that up. It's an Action secret under Repository Secrets that are not visible in GitHub UI. How can I test to see if it's valid ?

  


  Or maybe it's something else ?!? "Bad credentials" is vague...

  


  Here's the meat of the action we're trying to run :

  


  #my_tests.yml
jobs:
  my-test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:13.4
        env:
          POSTGRES_USERNAME: postgres
          POSTGRES_PASSWORD: postgres
          POSTGRES_DB: myapp_test
        ports:
          - 5432:5432
        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
    env:
      RAILS_ENV: test
      POSTGRES_HOST: localhost
      POSTGRES_USERNAME: pg
      POSTGRES_PASSWORD: pg
      GITHUB_TOKEN: ${{ secrets.BUNDLE_ACCESS_TOKEN }}
      BUNDLE_GITHUB__COM: x-access-token:${{ secrets.BUNDLE_ACCESS_TOKEN }}
      CUCUMBER_FORMAT: progress
    steps:
      - uses: actions/checkout@v2
      - uses: FedericoCarboni/setup-ffmpeg@v1
      ...


  


  And with debug turned on here's the Failure (line 20) from GitHub Actions :

  


  Run FedericoCarboni/setup-ffmpeg@v1

1 ------- ##[debug]Evaluating condition for step: 'Run FedericoCarboni/setup-ffmpeg@v1'
2 ##[debug]Evaluating: success()
3 ##[debug]Evaluating success:
4 ##[debug]=> true
5 ##[debug]Result: true
6 ##[debug]Starting: Run FedericoCarboni/setup-ffmpeg@v1
7 ##[debug]Loading inputs
8 ##[debug]Loading env
9 Run FedericoCarboni/setup-ffmpeg@v1
10   with:
11   env:
12     RAILS_ENV: test
13     POSTGRES_HOST: localhost
14     POSTGRES_USERNAME: pg
15     POSTGRES_PASSWORD: pg
16     GITHUB_TOKEN: ***
17     BUNDLE_GITHUB__COM: x-access-token:***
19     CUCUMBER_FORMAT: progress
20 Error: Bad credentials
21 ##[debug]Node Action run completed with exit code 1
22 ##[debug]Finishing: Run FedericoCarboni/setup-ffmpeg@v1


  


  Thanks for any help.