Recherche avancée

Sur d’autres sites (3788)

• How to install a 3rd party software with electron ?

  26 décembre 2016, par niksmac

  How to install a 3rd party software along with installing of electron app ?

  My use case is, I want to use ffmpeg inside my electron app, which is supposed to take screenshot from a video.

  Can I package the app in such a way that the user have to install only my app. And my app is installing ffmpeg for the user without any manual action.

  I would like to automate the process of installing ffmpeg during the electron app install on different OSs, if possible.

• How to configure and validate a Funnel in Piwik Analytics

  16 janvier 2017, par InnoCraft — Community

  In the last blog post we have covered how the conversion Funnel plugin enriches your Piwik experience. This post will focus on how to configure and validate your funnel in Piwik so you get the correct data when you view the funnel reports. When you set up a funnel, it is crucial to have it configured correctly as the funnel report will be only as good as its configuration. When we built this Funnel feature, we focused on making the configuration and validation real simple because it is so important to get it right.

  To recap quickly : A Funnel defines a series of steps that you expect your visitors to take on their way to converting a goal or a sale. Funnels, a premium feature for Piwik developed by InnoCraft, lets you define funnels so you can improve your websites and mobile apps based on this data. Learn more about Funnel.

  Configuring a funnel

  As you will notice Funnels integrates nicely into the Piwik Goals management. You can configure a funnel whenever you create or update a goal. You can access the Goals Management either via “Administration => Goals” or via the reporting menu “Goals => Manage”. Then click on either “Add a new goal” or select an existing goal to edit it. At the bottom of the goal form, you will see a new row letting you configure a funnel. As with all our premium features we focused on displaying lots of inline help and explain directly in the UI what a funnel is about, what the steps are in order to configure a funnel, how a funnel helps you and more. This lets you use the Funnel feature even if you have never created or analyzed a funnel before.

  Preparing your Funnel configuration

  Before starting to configure a Funnel we usually have a brainstorm session identifying the funnels on a website or app and the paths we expect users to take there. Once we have identified each step, we click through those identified pages in our website and we note the URLs for each page as the URLs will be needed when you configure a funnel.

  Setting up a Goal

  Once we have finished the planning phase it is time to log into Piwik. We start by either adding a new goal or selecting an existing goal. If you are unfamiliar with setting up goals, have a look at the Piwik Goals user guide. At the bottom of a goal form when you create or update a goal, you can configure your funnel. The UI will first explain you everything about Funnels, what they are, how they help you and which steps you need to take in order to configure it.

  Configuring Funnel steps

  We start by configuring the steps we have identified in the planning phase. Those are the steps we expect our users to take when they convert a goal or purchase something. Now we need to add a step for each page we expect users to take, each step consists of a name and a pattern.

  The name will be shown to you in the funnel reporting so think of a good name that describes each step best, for example “Product”, “Cart”, “Checkout” and “Order”.

  The pattern is needed to define when a visitor will enter this step. Here it comes in handy to have already notes for each URL from the planning phase. You can select lots of different patterns based on “URL Path”, “URL” and “URL parameter”. For example “URL starts with”, “Path ends with”, “URL contains”, “URL matches the regular expression”, and more. Most tools make this configuration unnecessarily hard because they only allow you to choose from one or two patterns (only complicated pattern like regular expressions) and they don’t let you validate whether the URL you have in mind actually matches the pattern. There are three ways to validate your step configurations.

  

  Validating funnel steps

  When we configure a funnel, we validate our steps in the following three ways.

  1. Via the help icon next to the step configuration

  When you click on the help icon, you will receive valuable tips about configuring steps, what “required” means and how to match popular pages. It will also show you a list of all URLs that were tracked in your Piwik in the past and match your specified pattern. For example say you specify a pattern “Path starts with /products”, then Piwik will list all URLs that were tracked in the past matching this pattern. This lets you validate whether your pattern actually matches the URLs you had in mind. It will also show you if the pattern doesn’t match any known URL which can indicate that your configuration may be wrong.

  

  2. Via the URL validator

  Below the steps configuration you find a form field that lets you enter any URL.

  

  We recommend to enter each URL that you have noted before in the planning phase. Once you enter a URL, the configurations will be validated immediately and the result will be shown to you in the step configuration. When a step matches your specified URL, the background will become green, when a step does not match the URL, the background will be red.

  

  If the URL does not match the expected step, simply change your step configuration and the steps will be re-validated as you change the configuration. This way you will see instantly as soon as you got the configuration right.

  What you don’t want is that either all of your steps don’t match (red background) or that several steps match a certain URL (green background). When several step match one URL, then one visitor might enter several funnel steps on just one page. This usually indicates a problem with the step configuration.

  3. Manual funnel validation

  After we have created or updated the goal (more about this soon), we always test a funnel configuration manually. This means we now open our website and click through the pages that we hand in mind and check afterwards whether the steps we took actually appear in the funnel report as expected. This is just another safety net to make sure your funnel configuration is right.

  It is really crucial to have a correct funnel configuration as otherwise the shown data in the funnel reports might not be as helpful. That’s why we focused so much on making the validation part real easy.

  Activating and saving the funnel

  Once you are happy with your configuration, it is time to activate your funnel. As soon as you activate your funnel, a report for this funnel will be generated and the links and reports for this funnel will be visible in the UI. If you are later no longer interested in the funnel, simply deactivate the funnel so it won’t appear in the reporting UI anymore.

  

  To save your funnel configuration simply click on either “Add goal” or “Update goal”. The funnel will be automatically saved whenever you update your goal.

  Goals Management

  The funnel plugin also enriches the list of goals in the Piwik goal management. At a glance you can see whether a funnel for a goal is configured and activated (green tick in the funnel column), whether a funnel is configured but not activated (grey tick in the funnel column) or whether no funnel is configured for a goal (no tick at all).

  

  How to get Funnels and related features

  You can get Funnels on the Piwik Marketplace. If you want to learn more about Funnels you might be also interested in the Funnel User Guide and the Funnel FAQ.

  Similar to Funnels we also offer Users Flow which lets you visualize the flow of your users and visitors across several interactions.

• bash script to install / update ffmpeg static builds

  1er mars 2017, par Joakim

  Hi I’m trying to make my first "real" bash script to do some real work than can be executed both manually and through cron jobs.

  The script should download and install the ffmpeg-static-build from https://johnvansickle.com/ffmpeg

  Here is what I’ve got so far :

  #!/bin/bash
  
  # Still to come, see if the script runs with root privileges else exit
  
  #Download FFMPEG static daily build and it's md5
  
  cd ~
  
  wget https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz | tar -xf
  
  #wget https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz.md5
  
  curl -L https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz.md5 | tar -xf | tee -a https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz | cut -d\  -f1 | md5sum > md5sum.txt
  
  
  
  
  
  #Chech the md5 is currect
  
  #md5sum -c MD5SUMS
  
  file1="md5sum.txt"
  
  file2="ffmpeg-git-64bit-static.tar.xz.md5"
  
  
  
  if ! cmp --silent "$file1" "$file2"; then
  
      echo "md5sum doesn't match...\n exit" >&2
  
      exit 1
  
  fi
  
  
  
  
  
  #tar -xf ffmpeg-*.tar.xz
  
  cp ffmpeg-*-static/ff* /usr/bin/
  
  cp ffmpeg-*-static/ff* /usr/local/bin/
  
  cp ffmpeg-*-static/qt-faststart /usr/bin/
  
  cp ffmpeg-*-static/qt-faststart /usr/local/bin/
  
  # Consider change second location to use ln -s
  
  # Remove downloads and do some clean up
  
  
  
  rm -fr ffmpeg-*
  
  
  
  #EOF

  As you can see in the script i would like to add the md5sum check but it fails (got the md5sum check part from Compare md5 sums in bash script)

  If i remove the md5sum part the script is working, but right now the script fails at the | tar -xf | part with this code

  2017-02-28 00:10:24 (617 KB/s) - ‘ffmpeg-git-64bit-static.tar.xz’ saved [17564756/17564756]
  
  
  
  tar: option requires an argument -- 'f'
  
  Try 'tar --help' or 'tar --usage' for more information.
  
  tee: 'https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz': No such file or directory
  
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
  
                                   Dload  Upload   Total   Spent    Left  Speed
  
  100    65  100    65    0     0     87      0 --:--:-- --:--:-- --:--:--    87
  
  (23) Failed writing body
  
  md5sum doesn't match...
  
   exit

  As this is my first, I would appreciate any "I’m 4 years old" advices and why

  update

  Have made some changes to the script based on the suggestions in this thread, but my problem is I have no output what so ever at this state :( So I think it’s time to ask for the next clue

  #!/bin/bash
  
  
  
  # version 0.3z
  
  
  
  ## Download FFMPEG static daily build and it's md5
  
  ## 
  
  ## To make this script working you might need to change the below values
  
  ## based on whether you are using a 32bit or 64 bit OS
  
  ## to obtain the right links you have to have a look @ https://johnvansickle.com/ffmpeg/
  
  ## and then change those below
  
  ## 
  
  ## If you are running on a shared server or dowsn't have root priviliges you might need to uncomment
  
  ## point 5.
  
  
  
  
  
  # a "~" means running users home folder :) and should be different from destination dir
  
  download_dir=~
  
  
  
  # as this can change if the ffmpeg is to be stored on ex. shared server
  
  dest_dir=/usr/bin/
  
  
  
  # The version it equal the filename from above link
  
  version=ffmpeg-git-64bit-static.tar.xz
  
  
  
  ## Do not change anything below here!!
  
  source_url=https://johnvansickle.com/ffmpeg/builds/${version}
  
  md5_url=https://johnvansickle.com/ffmpeg/builds/${version}.md5
  
  
  
  # Still to come, see if the script runs with write privileges else exit
  
  
  
  # 1. Can we enter download directory else exit
  
  cd ${download_dir} ||
  
  
  
          printf "%s\n" "You can't enter this folder.\nPlease chage download_dir in this script..." >&2
  
          exit 1
  
  
  
  # 2. Check the md5 is correct or have changed from last check
  
  ## instead of downloading ffmpeg-git-64bit-static.tar.xz every time,
  
  ## regardless if it is new or not, I recommend only downloading it
  
  ## if the md5 does not match. Would save John some bandwidth at least
  
  ## thx for the idea to @LordNeckbeard
  
  
  
  
  
  
  
  ## So somehow i'll guess some sed or grep only first part is nessesary :(
  
  ## This is getting more advance than expected for a first time script :/
  
  
  
  if ! diff <(md5sum ${version}) <(curl -s ${md5_url})
  
  
  
      then
  
          printf "%s\n" "md5sum doesn't match...\n
  
                          Downloading new version" >&2
  
          rm -f ${version} >&2
  
          curl ${source_url} -o ${download_dir}/${version} >&2
  
          #exit 2
  
  
  
      elif
  
          diff <(md5sum ${version}) <(curl -s ${md5_url})
  
          printf "%s\n" "Nothing new to download" >&2
  
        exit 3
  
  fi
  
  
  
  # 3. untar
  
  tar -xf ffmpeg-git-*-static.tar.xz
  
  
  
  # 4. Move builds to destination directories
  
  
  
  mv ${download_dir}/ffmpeg-*-static/ff* ${dest_dir}/
  
  mv ${download_dir}/ffmpeg-*-static/qt-faststart ${dest_dir}/
  
  
  
  # 5. Make soft links to static builds
  
  ln -sfn ${dest_dir}/qt-faststart /usr/local/bin/qt-faststart
  
  ln -sfn ${dest_dir}/ffmpeg /usr/local/bin/ffmpeg
  
  ln -sfn ${dest_dir}/ffmpeg-10bit /usr/local/bin/ffmpeg-10bit
  
  ln -sfn ${dest_dir}/ffprobe /usr/local/bin/ffprobe
  
  ln -sfn ${dest_dir}/ffserver /usr/local/bin/ffserver
  
  
  
  # Remove unzipped folder to do some clean up
  
  
  
  rm -fr ffmpeg-git-*-static/
  
  
  
  #EOF

  note : do to some more in depth answering of why not compile from source :
  1. This precompiled is usable on all Linux variations, despite distro and version
  2. It usable on shared hosting servers with ssh access

  UPDATE 2

      #!/bin/bash
  
  
  
  # version 0.4z
  
  
  
  ## Download FFMPEG static daily build and it's md5
  
  ## 
  
  ## To make this script working you might need to change the below values
  
  ## based on whether you are using a 32bit or 64 bit OS
  
  ## to obtain the right links you have to have a look @ https://johnvansickle.com/ffmpeg/
  
  ## and then change those below
  
  ## 
  
  ## Finished and working script should be distributed under GPLv3: free as in freedom
  
  ## 
  
  ## If you are running on a shared server or dowsn't have root priviliges you might need to uncomment
  
  ## point 5.
  
  
  
  
  
  # a "~" means running users home folder :) and should be different from destination dir
  
  download_dir=~
  
  
  
  # as this can change if the ffmpeg is to be stored on ex. shared server
  
  dest_dir=/usr/bin/
  
  
  
  # The version it equal the filename from above link
  
  version=ffmpeg-git-64bit-static.tar.xz
  
  
  
  ## Do not change anything below here!!
  
  source_url=https://johnvansickle.com/ffmpeg/builds/${version}
  
  md5="curl -s https://johnvansickle.com/ffmpeg/builds/${version}.md5"
  
  
  
  # Still to come, see if the script runs with write privileges else exit
  
  
  
  # 1. Can we enter download directory else exit
  
  cd ${download_dir} || 
  
          printf "%s\n" "You can't enter this folder.\nPlease chage download_dir in this script..." >&2
  
          exit 1
  
  
  
  # 2. Check the md5 is correct or have changed from last check
  
  ## instead of downloading ffmpeg-git-64bit-static.tar.xz every time,
  
  ## regardless if it is new or not, I recommend only downloading it
  
  ## if the md5 does not match. Would save John some bandwidth at least
  
  ## thx for the idea to @LordNeckbeard
  
  
  
  ## This is getting more advance than expected for a first time script :/
  
  
  
  if diff <(md5sum ${version}) <(${md5})
  
  
  
      then
  
          printf "%s\n" "No new version availeble" >&2
  
          exit 1
  
  
  
  elif ! diff <(md5sum ${version}) <(${md5})
  
      then
  
          rm -f ${version}
  
          curl ${source_url} > ${version}
  
          exit 0
  
  
  
          #only proceed if downloaded version match it's md5
  
          if ! diff <(md5sum ${version}) <(${md5})
  
              then
  
              rm -f ${version}
  
              printf "%s\n" "Downloaded version is damaged, try later\ndamaged version have been deleted" >&2
  
              exit 1
  
          fi
  
  
  
              # 3. untar
  
              tar -xf ffmpeg-git-*-static.tar.xz
  
  
  
              # 4. Move builds to destination directories
  
              mv ${download_dir}/ffmpeg-*-static/ff* ${dest_dir}/
  
              mv ${download_dir}/ffmpeg-*-static/qt-faststart ${dest_dir}/
  
  
  
              # 5. Make soft links to static builds
  
              ln -sfn ${dest_dir}/qt-faststart /usr/local/bin/qt-faststart
  
              ln -sfn ${dest_dir}/ffmpeg /usr/local/bin/ffmpeg
  
              ln -sfn ${dest_dir}/ffmpeg-10bit /usr/local/bin/ffmpeg-10bit
  
              ln -sfn ${dest_dir}/ffprobe /usr/local/bin/ffprobe
  
              ln -sfn ${dest_dir}/ffserver /usr/local/bin/ffserver
  
  
  
              # Remove unzipped folder to do some clean up
  
              rm -fr ffmpeg-git-*-static/
  
              printf "%s\n" "Going to install new version" >&2
  
              exit 1
  
  fi
  
  #EOF

  But still having some issues :(

  1. Running this script returns : a blanc shell, but I’ve expected one of the printf statements
  2. When I’m trying to narrow down the problem and going back to basic and trying to run the script with only the "if" part it fails with 44 : Syntax error : "(" unexpected

  3. running the very same "if" part typed directly into the shell/terminal itself it’s all happy !!
     if diff <(md5sum ffmpeg-git-64bit-static.tar.xz) <(curl -s "https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz.md5"); then printf "%s\n" "No new version availeble" >&2; elif ! diff <(md5sum ffmpeg-git-64bit-static.tar.xz) <(curl -s "https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz.md5"); then rm -f ffmpeg-git-64bit-static.tar.xz; curl https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-64bit-static.tar.xz > ffmpeg-git-64bit-static.tar.xz; printf "%s\n" "Going to install new version" >&2; fi

  4. I’m confused