
Recherche avancée
Autres articles (67)
-
Gestion générale des documents
13 mai 2011, parMédiaSPIP ne modifie jamais le document original mis en ligne.
Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (9514)
-
Send rtmp from nginx into another VM
12 janvier 2018, par Akim BenchihaI’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. -
Piwik 2 reaches end of life soon (December 2017), update now !
7 décembre 2017, par Piwik Core Team — CommunityIn 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 !
-
FFmpeg doesnt read any file
19 mars 2020, par Excalibur SwordI can see files with ftp connection even more with terminal but ffmpeg command doesnt do it.I show the error on youtube link.
root@cixme:/var/www/html# ls
deneme.php index.html PHP-FFMpeg-master
drop.avi info.php php-html5-video-converter-master
root@cixme:/var/www/html#the link shows the error how disapers.
I use ubuntu vps server.the program is remmina
root@cixme:/# sudo ffmpeg -i drop.mp4
sudo: unable to resolve host cixme
Error: unable to open display
ffmpeg version n4.1.4 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
configuration: --prefix= --prefix=/usr --disable-debug --disable-doc --disable-static --enable-avisynth --enable-cuda --enable-cuvid --enable-libdrm --enable-ffplay --enable-gnutls --enable-gpl --enable-libass --enable-libfdk-aac --enable-libfontconfig --enable-libfreetype --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb --enable-libopus --enable-libpulse --enable-sdl2 --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxvid --enable-nonfree --enable-nvenc --enable-omx --enable-openal --enable-opencl --enable-runtime-cpudetect --enable-shared --enable-vaapi --enable-vdpau --enable-version3 --enable-xlib
libavutil 56. 22.100 / 56. 22.100
libavcodec 58. 35.100 / 58. 35.100
libavformat 58. 20.100 / 58. 20.100
libavdevice 58. 5.100 / 58. 5.100
libavfilter 7. 40.101 / 7. 40.101
libswscale 5. 3.100 / 5. 3.100
libswresample 3. 3.100 / 3. 3.100
libpostproc 55. 3.100 / 55. 3.100
drop.mp4: No such file or directory