
Recherche avancée
Médias (1)
-
The pirate bay depuis la Belgique
1er avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (32)
-
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community. -
ANNEXE : Les plugins utilisés spécifiquement pour la ferme
5 mars 2010, parLe site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)
-
Contribute to translation
13 avril 2011You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
MediaSPIP is currently available in French and English (...)
Sur d’autres sites (5368)
-
Revision 276a1106e6 : Merge changes I54acef34,I72d42971 into experimental * changes : Make some sb_t
24 avril 2013, par Ronald S. BultjeChanged Paths : Modify /vp9/decoder/vp9_decodemv.c Modify /vp9/decoder/vp9_decodframe.c Merge changes I54acef34,I72d42971 into experimental * changes : Make some sb_type comparisons independent of literal enum values. Make loopfilter aware of rectangular (...)
-
Deploying on google App Engine : An error occurred : ffmpeg was killed with signal SIGABRT Error : ffmpeg was killed with signal SIGABRT
27 août 2020, par Jérémy GachonI wrote a node-js api, with node-js and fluent-ffmpeg :


'use strict';
require('babel-register');
const path = require('path'); 
const ffmpeg = require('fluent-ffmpeg');



[...]


var infs = new ffmpeg

infs.addInput(doc.data().url).outputOptions([
 '-preset slow', '-g 48', '-sc_threshold 0',
 '-map 0:0', '-map 0:1', '-map 0:0', '-map 0:1',
 '-s:v:0 1280x720', '-c:v:0 libx264', '-b:v:0 2000k',
 // "-var_stream_map", "'v:0,a:0 v:1,a:1'",
 '-master_pl_name ./' + req.params.id + '/master' + req.params.id + '.m3u8',
 '-f hls', '-hls_time 6', '-hls_list_size 0',
 '-hls_segment_filename ./' + req.params.id + '/fileSequence|' + req.params.id + '|%d|v%v.ts',
 '-max_muxing_queue_size 1024',
 ]).output('./' + req.params.id + '/video' + req.params.id + '.m3u8')
 .on('start', function (commandLine) {
 console.log('Spawned Ffmpeg with command: ' + commandLine);
 })
 .on('error', function (err, stdout, stderr) {
 console.log('An error occurred: ' + err.message, err, stderr);
 })
 .on('progress', function (progress) {
 console.log('Processing: ' + progress.percent + '% done')
 })
 .on('end', function (err, stdout, stderr) {

 console.log('Finished processing!' /*, err, stdout, stderr*/)
 })
 .run()
 res.status(200).send('GG').end();
 } 
 });



[...]


That work with




node app.js




on my macbook pro, but when i do




gcloud app deploy




and I call the public url, I have this logs :


Processing: undefined% done
An error occurred: ffmpeg was killed with signal SIGABRT Error: ffmpeg was killed with signal SIGABRT 



Here is my app.yaml :


# Copyright 2017, Google, Inc.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

# [START gae_flex_quickstart_yaml]
runtime: nodejs
env: flex

# This sample incurs costs to run on the App Engine flexible environment.
# The settings below are to reduce costs during testing and are not appropriate
# for production use. For more information, see:
# https://cloud.google.com/appengine/docs/flexible/nodejs/configuring-your-app-with-app-yaml
manual_scaling:
 instances: 1
resources:
 cpu: 1
 memory_gb: 6
 disk_size_gb: 30

# [END gae_flex_quickstart_yaml]





How can I do to deploy correctly my node-js api on google app engine ?


Thank's in advance.


Jérémy.


-
Core : make sure remote is executed last
14 janvier 2014, par bpintoCore : make sure remote is executed last
Fixes gh-711
Closes gh-807