Recherche avancée

Médias (91)

Autres articles (66)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Menus personnalisés

    14 novembre 2010, par

    MediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
    Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
    Menus créés à l’initialisation du site
    Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...)

Sur d’autres sites (5306)

  • Piwik 2 reaches end of life soon (December 2017), update now !

    7 décembre 2017, par Piwik Core Team — Community

    In less than three weeks, Piwik 2 will be no longer supported. This means that no further (security) updates will be released for this version. As per our Long Term Support announcement, Piwik 2.X is supported for 12 months after the initial release of Piwik 3.0.0 which was on December 18th 2016. Therefore, Piwik 2 will no longer receive any updates after December 18th 2017.

    It has been almost a year since we released Piwik 3 and we highly recommend updating to Piwik 3 ASAP. The major new release came with a new UI, performance and security improvements. If you are still on Piwik 2, the security improvements alone should be worth updating your Piwik to Piwik 3 now. We cannot recommend this enough.

    The update to Piwik 3 should be smooth, but may take a while depending on the amount of data you have.

    • If you have any problem with the update, feel free to get in touch with us, or ask in the forums.
    • If you are currently using Piwik self-hosted and would like to be upgraded, plus your Piwik managed in the official Cloud-hosted service, contact InnoCraft Cloud and they will migrate your database.

    At Piwik and InnoCraft, the company of the makers of Piwik, we have seen many thousands of Piwik installations upgraded over the past year and look forward to an exciting future for Piwik 3 and beyond !

  • Send rtmp from nginx into another VM

    12 janvier 2018, par Akim Benchiha

    I’ve set up my nginx server in a VM for the rtmp connection.
    I want to use exec_push for running a script in another VM.

    NGINX 1st VM

    rtmp {
     server {
        listen 1935;
        ping 30s;
        notify_method get;
           application ingest {
                live on;
                exec_kill_signal term;
                idle_streams off;
                #exec_push /usr/local/bin/ffmpeg_push.sh $name ;
                exec_options on;
                exec_push sshpass -p PASSWORD ssh root@192.168.1.139 sh /usr/local/bin/ffmpeg_push.sh $name;
        }
     }
    }

    I have also tried with node server that execute the script but every time, the script reset

    NGINX 1st VM

      rtmp {
         server {
            listen 1935;
            ping 30s;
            notify_method get;
               application ingest {
                    live on;
                    exec_kill_signal term;
                    idle_streams off;
                    #exec_push /usr/local/bin/ffmpeg_push.sh $name ;
                    exec_options on;
                    exec_push curl -X POST -H "Content-Type: application/json" -d "" 192.168.1.139:3000/$name;
            }
         }
       }

    NodeJS into second VM

    #!/usr/bin/env node

    const express = require('express');
    var app = express();
    app.use(function (req, res, next) {
           res.setHeader('Access-Control-Allow-Origin', '*');
           res.setHeader('Access-Control-Allow-Methods', 'GET, POST, OPTIONS, PUT, PATCH, DELETE');
           res.setHeader('Access-Control-Allow-Headers', 'X-Requested-With,content-type');
           res.setHeader('Access-Control-Allow-Credentials', true);
           next();
    });
    app.post('/:name', function(req, res) {
           console.log('start performed');
           console.log(req.params.name);
           require('child_process').spawn('sh', ['ffmpeg_push.sh', req.params.name], {stdio: 'inherit'});
    });

    But when the script is running in the first VM, everything is fine. I have disabled the firewall.
    Thank you.

  • avcodec/exr : use the correct step value for plane pointers

    5 mars, par James Almer
    avcodec/exr : use the correct step value for plane pointers
    

    Fixes a regression since 0e917389fe73c932049635d947bba076f1709589.

    Signed-off-by : James Almer <jamrial@gmail.com>

    • [DH] libavcodec/exr.c
    • [DH] tests/ref/fate/exr-rgb-tile-half-piz-dw-large
    • [DH] tests/ref/fate/exr-rgb-tile-half-zip