Recherche avancée

Médias (1)

Mot : - Tags -/Christian Nold

Autres articles (67)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • 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 (...)

Sur d’autres sites (4518)

  • Reason for write EPIPE error in my implementation ?

    25 mai 2019, par Chrisl446

    I currently have a small node.js express application for uploading images using sharp & thumbnails created from .mp4 videos using simple-thumbnail package/ffmpeg.

    The app works perfectly when uploading an image, the file is uploaded sharp processes it, then passes it along and it ends up in my amazon s3 bucket as expected. No errors what so ever.

    However, when I upload an mp4 video that I use to create and upload a thumbnail from by using simple-thumbnails genThumbnail() function, which uses ffmpeg child process, the thumbnail uploads successully to my s3 bucket, HOWEVER my app returns an EPIPE write error and NOT the url of the uploaded files url on S3.

    What is causing this and how can I fix it, considering it’s pretty much working aside from the EPIPE error that is being returned ? Thanks ahead !

    The packages of concern used are as follows :

    aws-sdk

    multer

    multer-s3 <- this one with the transform option, not the standard multer-s3 package

    simple-thumbnail

    const express = require('express');
    
const app = express();
    

    
const aws = require('aws-sdk');
    
const multer = require('multer');
    
const multerS3 = require('multer-s3'); //github:gmenih341/multer-s3 version of multer-s3 with transform option
    
const sharp = require('sharp');
    
const genThumbnail = require('simple-thumbnail');
    

    
app.use((req, res, next) => {
    
    res.header('Access-Control-Allow-Origin', '*');
    
    res.header('Access-Control-Allow-Headers', 'Orgin, X-Requested-With, Content-Type, Accept, Authorization');
    
    if (req.method === 'OPTIONS') {
    
        res.header('Access-Control-Allow-Methods', 'POST');
    
        return res.status(200).json({});
    
    }
    
    next();
    
});
    

    
let uniqueFileName;
    
let s3BucketName = 'bucketname';
    

    
let s3 = new aws.S3({
    
    accessKeyId: ACCESS_KEY,
    
    secretAccessKey: SECRET_KEY,
    
    Bucket: s3BucketName
    
});
    

    
let upload = multer({
    
    storage: multerS3({
    
        s3: s3,
    
        bucket: s3BucketName,
    
        acl: 'public-read',
    
        cacheControl: 'max-age=31536000',
    
        contentType: multerS3.AUTO_CONTENT_TYPE,
    
        shouldTransform: true,
    
        transforms: [{
    
            id: 'thumbnail',
    
            key: function (req, file, cb) {
    
                uniqueFileName = Date.now().toString();
    
                cb(null, uniqueFileName + '.jpg')
    
            },
    
            transform: function (req, file, cb) {
    
                if (file.mimetype == 'video/mp4') {
    
                    //When using simple-thumbnails' getThumbnail() on an mp4 video it uploads succesfully to S3 but node returns EPIPE write error
    
                    cb(null, genThumbnail(null, null, '250x?'))
    
                } else {
    
                    //When using sharp to resize an image this works perfectly and retuns the JSON below with the files S3 URL
    
                    cb(null, sharp().jpeg())
    
                }
    

    
            }
    
        }]
    
    })
    
});
    

    
app.post('/upload', upload.array('theFile'), (req, res) => {
    
    res.json({
    
        fileS3Url: 'https://s3.amazonaws.com/'+ s3BucketName +'/' + uniqueFileName
    
    });
    
});
    

    
app.use((req, res, next) => {
    
    const error = new Error('Not found');
    
    error.status = 404;
    
    next(error);
    
});
    

    
app.use((error, req, res, next) => {
    
    res.status(error.status || 500);
    
    res.json({
    
        error: {
    
            message: error.message
    
        }
    
    });
    
});
    

    
module.exports = app;

  • Reason for write EPIPE error in my implentation ?

    18 mai 2019, par Chrisl446

    So I currently have a small node.js express application for uploading images using sharp & thumbnails created from .mp4 videos using simple-thumbnail package/ffmpeg.

    The app works perfectly when uploading an image, the file is uploaded sharp processes it, then passes it along and it ends up in my amazon s3 bucket as expected. No errors what so ever.

    However, when I upload an mp4 video that I use to create and upload a thumbnail from by using simple-thumbnails genThumbnail() function, which uses ffmpeg child process, the thumbnail uploads successully to my s3 bucket, HOWEVER my app returns an EPIPE write error and NOT the url of the uploaded files url on S3.

    What is causing this and how can I fix it, considering it’s pretty much working aside from the EPIPE error that is being returned ? Thanks ahead !

    The packages of concern used are as follows :

    aws-sdk

    multer

    multer-s3 <- this one with the transform option, not the standard multer-s3 package

    simple-thumbnail

    const express = require('express');
    
const app = express();
    

    
const aws = require('aws-sdk');
    
const multer = require('multer');
    
const multerS3 = require('multer-s3'); //github:gmenih341/multer-s3 version of multer-s3 with transform option
    
const sharp = require('sharp');
    
const genThumbnail = require('simple-thumbnail');
    

    
app.use((req, res, next) => {
    
    res.header('Access-Control-Allow-Origin', '*');
    
    res.header('Access-Control-Allow-Headers', 'Orgin, X-Requested-With, Content-Type, Accept, Authorization');
    
    if (req.method === 'OPTIONS') {
    
        res.header('Access-Control-Allow-Methods', 'POST');
    
        return res.status(200).json({});
    
    }
    
    next();
    
});
    

    
let uniqueFileName;
    
let s3BucketName = 'bucketname';
    

    
let s3 = new aws.S3({
    
    accessKeyId: ACCESS_KEY,
    
    secretAccessKey: SECRET_KEY,
    
    Bucket: s3BucketName
    
});
    

    
let upload = multer({
    
    storage: multerS3({
    
        s3: s3,
    
        bucket: s3BucketName,
    
        acl: 'public-read',
    
        cacheControl: 'max-age=31536000',
    
        contentType: multerS3.AUTO_CONTENT_TYPE,
    
        shouldTransform: true,
    
        transforms: [{
    
            id: 'thumbnail',
    
            key: function (req, file, cb) {
    
                uniqueFileName = Date.now().toString();
    
                cb(null, uniqueFileName + '.jpg')
    
            },
    
            transform: function (req, file, cb) {
    
                if (file.mimetype == 'video/mp4') {
    
                    //When using simple-thumbnails' getThumbnail() on an mp4 video it uploads succesfully to S3 but node returns EPIPE write error
    
                    cb(null, genThumbnail(null, null, '250x?'))
    
                } else {
    
                    //When using sharp to resize an image this works perfectly and retuns the JSON below with the files S3 URL
    
                    cb(null, sharp().jpeg())
    
                }
    

    
            }
    
        }]
    
    })
    
});
    

    
app.post('/upload', upload.array('theFile'), (req, res) => {
    
    res.json({
    
        fileS3Url: 'https://s3.amazonaws.com/'+ s3BucketName +'/' + uniqueFileName
    
    });
    
});
    

    
app.use((req, res, next) => {
    
    const error = new Error('Not found');
    
    error.status = 404;
    
    next(error);
    
});
    

    
app.use((error, req, res, next) => {
    
    res.status(error.status || 500);
    
    res.json({
    
        error: {
    
            message: error.message
    
        }
    
    });
    
});
    

    
module.exports = app;

  • Evolution #4271 (Nouveau) : valider_url_distante => pouvoir déclarer des domaines distants et pas ...

    21 janvier 2019, par - Equipement

    Bonjour,

    La fonction valider_url_distante permet de déclarer des hosts distants :

    1. <span class="CodeRay"><span class="local-variable">$known_hosts</span> = pipeline(<span class="string"><span class="delimiter">'</span><span class="content">declarer_hosts_distants</span><span class="delimiter">'</span></span>, <span class="local-variable">$known_hosts</span>);
      2. 

    2. </span>
      3. 

    Télécharger

    C’est très bien, mais avec plusieurs centaines de hosts à déclarer (dont la liste varie dans le temps), cela devient compliqué à gérer.

    Serait-il possible d’avoir, en plus, la possibilité de déclarer des domaines distants ?

    Une première piste serait de pouvoir déclarer .example.com dans le pipeline pour inclure tous les *.example.com au lieu des les énumérer un par un.

    Une seconde piste consisterait à s’inspirer de la function need_proxy (via une constante avec la même syntaxe que pour le http_noproxy) :

    // Pour mémoire code actuel à conserver ...

    1. <span class="CodeRay">    <span class="local-variable">$is_known_host</span> = <span class="predefined-constant">false</span>;
      2. 

    2.     <span class="keyword">foreach</span> (<span class="local-variable">$known_hosts</span> <span class="keyword">as</span> <span class="local-variable">$known_host</span>) {
      3. 

    3.         <span class="local-variable">$parse_known</span> = <span class="predefined">parse_url</span>(<span class="local-variable">$known_host</span>);
      4. 

    4.         <span class="keyword">if</span> (<span class="local-variable">$parse_known</span>
      5. 

    5.           <span class="keyword">and</span> <span class="predefined">strtolower</span>(<span class="local-variable">$parse_known</span>[<span class="string"><span class="delimiter">'</span><span class="content">host</span><span class="delimiter">'</span></span>]) === <span class="predefined">strtolower</span>(<span class="local-variable">$parsed_url</span>[<span class="string"><span class="delimiter">'</span><span class="content">host</span><span class="delimiter">'</span></span>])) {
      6. 

    6.             <span class="local-variable">$is_known_host</span> = <span class="predefined-constant">true</span>;
      7. 

    7.             <span class="keyword">break</span>;
      8. 

    8.         }
      9. 

    9.     }
      10. 

    10. </span>
      11. 

    Télécharger

    // ... que l’on pourrait faire suivre de ce code (complètement inspiré de function need_proxy) :

    1. <span class="CodeRay">    <span class="keyword">if</span> (!<span class="local-variable">$is_known_host</span>) {
      2. 

    2.                 <span class="local-variable">$known_domaines</span> = _DECLARER_DOMAINES_DISTANTS;
      3. 

    3.  
      4. 

    4.                 <span class="local-variable">$known_domaines</span> = <span class="predefined">str_replace</span>(<span class="string"><span class="delimiter">"</span><span class="char">\n</span><span class="delimiter">"</span></span>, <span class="string"><span class="delimiter">"</span><span class="content"> </span><span class="delimiter">"</span></span>, <span class="local-variable">$known_domaines</span>);
      5. 

    5.                 <span class="local-variable">$known_domaines</span> = <span class="predefined">str_replace</span>(<span class="string"><span class="delimiter">"</span><span class="char">\r</span><span class="delimiter">"</span></span>, <span class="string"><span class="delimiter">"</span><span class="content"> </span><span class="delimiter">"</span></span>, <span class="local-variable">$known_domaines</span>);
      6. 

    6.                 <span class="local-variable">$known_domaines</span> = <span class="string"><span class="delimiter">"</span><span class="content"> </span><span class="local-variable">$known_domaines</span><span class="content"> </span><span class="delimiter">"</span></span>;
      7. 

    7.                 <span class="local-variable">$domain</span> = <span class="predefined">strtolower</span>(<span class="local-variable">$parsed_url</span>[<span class="string"><span class="delimiter">'</span><span class="content">host</span><span class="delimiter">'</span></span>]);
      8. 

    8.  
      9. 

    9.                 <span class="keyword">if</span> (<span class="predefined">strpos</span>(<span class="local-variable">$known_domaines</span>, <span class="string"><span class="delimiter">"</span><span class="content"> </span><span class="local-variable">$domain</span><span class="content"> </span><span class="delimiter">"</span></span>) !== <span class="predefined-constant">false</span>){
      10. 

    10.                     <span class="local-variable">$is_known_host</span> = <span class="predefined-constant">true</span>;
      11. 

    11.                 }
      12. 

    12.  
      13. 

    13.                 <span class="keyword">while</span> (<span class="predefined">strpos</span>(<span class="local-variable">$domain</span>, <span class="string"><span class="delimiter">'</span><span class="content">.</span><span class="delimiter">'</span></span>) !== <span class="predefined-constant">false</span>) {
      14. 

    14.                         <span class="local-variable">$domain</span> = <span class="predefined">explode</span>(<span class="string"><span class="delimiter">'</span><span class="content">.</span><span class="delimiter">'</span></span>, <span class="local-variable">$domain</span>);
      15. 

    15.                         <span class="predefined">array_shift</span>(<span class="local-variable">$domain</span>);
      16. 

    16.                         <span class="local-variable">$domain</span> = <span class="predefined">implode</span>(<span class="string"><span class="delimiter">'</span><span class="content">.</span><span class="delimiter">'</span></span>, <span class="local-variable">$domain</span>);
      17. 

    17.  
      18. 

    18.                         <span class="keyword">if</span> (<span class="predefined">strpos</span>(<span class="local-variable">$known_domaines</span>, <span class="string"><span class="delimiter">"</span><span class="content"> .</span><span class="local-variable">$domain</span><span class="content"> </span><span class="delimiter">"</span></span>) !== <span class="predefined-constant">false</span>) {
      19. 

    19.                             <span class="local-variable">$is_known_host</span> = <span class="predefined-constant">true</span>;
      20. 

    20.                         }
      21. 

    21.                 }
      22. 

    22.         } 
      23. 

    23. </span>
      24. 

    Télécharger

    Cordialement
    Equipement

Navigation