Recherche avancée

Sur d’autres sites (9175)

• Revision 86501 : la regexp de r86497 n’était pas valable car 1) le > n’était pas en fin ...

  5 décembre 2014, par maieul@… — Log

  la regexp de r86497 n’était pas valable car
  1) le > n’était pas en fin de phrase
  2) >< était encodés en HTML (#ENV passe par entites_html)

• Piwik 3 Release Candidate

  14 décembre 2016, par Piwik Core Team — Development

  The release candidate for Piwik 3 is now available.

  RC means we think we’re done, but it’s possible we’ve missed something. We hope to ship Piwik 3 on Sunday, December 18th (updated). If you haven’t tested Piwik 3 yet, now is the time ! To test Piwik 3, you can use the beta release channel or you can download the release candidate here (zip).

  Piwik 3 is a jam-packed release, with a number of features focused on security, performance, and more advanced analytics capabilities. Highlights include new UI design, responsive experience on mobile, better email reports, secure password storage, better tracking of downloads and outlinks, and more.

  Not sure where to start with testing ? Try setting up a new installation and taking notes on what you enjoyed and what got you stuck. For more details about what’s new in version 3.0, check out the beta 1, beta 2, beta 3, beta 4 changelogs as well as these blog posts : Piwik 3 overview, and Important notes and API breaking changes in Piwik 3.

  Think you’ve found a bug ? Please post to our Issues tracker. If any known issues come up, you’ll be able to search and find them there.

  Developers, please test your plugins and themes against Piwik 3 and update your plugin.json to require Piwik 3. An in-depth field guide to developer-focused changes and plugin migration is published on the Developer website.

  Do you speak a language other than English ? Help us translate Piwik into more than 50 languages !

  Happy testing !

• How to upload object to a bucket in Google Cloud Platform from Python script

  7 juillet 2016, par Bryan

  The goal of this script is to extract audio from a video file using ffmpeg and upload it into a bucket on Google Cloud Platform each time it is called. Eventually I will have to extract audio from a large list of videos, so ideally I would want my script to extract and subsequently upload it into the cloud.

  My confusion is how to use GCP API to upload my object into a bucket. Any advice would be greatly appreciated !

  Link for reference : https://cloud.google.com/storage/docs/json_api/v1/json-api-python-samples#setup-code

  import subprocess
  
  import sys
  
  import re 
  
  
  
  fullVideo = sys.argv[1]
  
  title = re.findall('^([^.]*).*', fullVideo)
  
  title = str(title[0])
  
  subprocess.call('ffmpeg -i ' + fullVideo + ' -vn -ab 128k ' + title + '.flac', shell = True)
  
  
  
  def upload_object(bucket, filename, readers, owners):
  
      service = create_service()
  
  
  
      # This is the request body as specified:
  
      # http://g.co/cloud/storage/docs/json_api/v1/objects/insert#request
  
      body = {
  
          'name': filename,
  
      }
  
  
  
      # If specified, create the access control objects and add them to the
  
      # request body
  
      if readers or owners:
  
          body['acl'] = []
  
  
  
      for r in readers:
  
          body['acl'].append({
  
              'entity': 'user-%s' % r,
  
              'role': 'READER',
  
              'email': r
  
          })
  
      for o in owners:
  
          body['acl'].append({
  
              'entity': 'user-%s' % o,
  
              'role': 'OWNER',
  
              'email': o
  
          })
  
  
  
      # Now insert them into the specified bucket as a media insertion.
  
      # http://g.co/dev/resources/api-libraries/documentation/storage/v1/python/latest/storage_v1.objects.html#insert
  
      with open(filename, 'rb') as f:
  
          req = service.objects().insert(
  
              bucket=bucket, body=body,
  
              # You can also just set media_body=filename, but # for the sake of
  
              # demonstration, pass in the more generic file handle, which could
  
              # very well be a StringIO or similar.
  
              media_body=http.MediaIoBaseUpload(f, 'application/octet-stream'))
  
          resp = req.execute()
  
  
  
      return resp