
Recherche avancée
Autres articles (54)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Installation en mode ferme
4 février 2011, parLe mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
C’est la méthode que nous utilisons sur cette même plateforme.
L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)
Sur d’autres sites (8718)
-
ffmpeg running in cloudfunction silently fails/never finishes
19 juin 2020, par VojtěchI am trying to implement a Cloudfunction which would run
ffmpeg
on a Google bucket upload. I have been playing with a script based on https://kpetrovi.ch/2017/11/02/transcoding-videos-with-ffmpeg-in-google-cloud-functions.html


The original script needs little tuning as the library evolved a bit. My current version is here :



const {Storage} = require('@google-cloud/storage');
const storage = new Storage();
const ffmpeg = require('fluent-ffmpeg');
const ffmpeg_static = require('ffmpeg-static');

console.log("Linking ffmpeg path to:", ffmpeg_static)
ffmpeg.setFfmpegPath(ffmpeg_static);

exports.transcodeVideo = (event, callback) => {
 const bucket = storage.bucket(event.bucket);
 console.log(event);
 if (event.name.indexOf('uploads/') === -1) {
 console.log("File " + event.name + " is not to be processed.")
 return;
 }

 // ensure that you only proceed if the file is newly createdxxs
 if (event.metageneration !== '1') {
 callback();
 return;
 }

 // Open write stream to new bucket, modify the filename as needed.
 const targetName = event.name.replace("uploads/", "").replace(/[.][a-z0-9]+$/, "");
 console.log("Target name will be: " + targetName);

 const remoteWriteStream = bucket.file("processed/" + targetName + ".mp4")
 .createWriteStream({
 metadata: {
 //metadata: event.metadata, // You may not need this, my uploads have associated metadata
 contentType: 'video/mp4', // This could be whatever else you are transcoding to
 },
 });

 // Open read stream to our uploaded file
 const remoteReadStream = bucket.file(event.name).createReadStream();

 // Transcode
 ffmpeg()
 .input(remoteReadStream)
 .outputOptions('-c:v copy') // Change these options to whatever suits your needs
 .outputOptions('-c:a aac')
 .outputOptions('-b:a 160k')
 .outputOptions('-f mp4')
 .outputOptions('-preset fast')
 .outputOptions('-movflags frag_keyframe+empty_moov')
 // https://github.com/fluent-ffmpeg/node-fluent-ffmpeg/issues/346#issuecomment-67299526
 .on('start', (cmdLine) => {
 console.log('Started ffmpeg with command:', cmdLine);
 })
 .on('end', () => {
 console.log('Successfully re-encoded video.');
 callback();
 })
 .on('error', (err, stdout, stderr) => {
 console.error('An error occured during encoding', err.message);
 console.error('stdout:', stdout);
 console.error('stderr:', stderr);
 callback(err);
 })
 .pipe(remoteWriteStream, { end: true }); // end: true, emit end event when readable stream ends
};





This version correctly runs and I can see this in logs :



2020-06-16 21:24:22.606 Function execution took 912 ms, finished with status: 'ok'
2020-06-16 21:24:52.902 Started ffmpeg with command: ffmpeg -i pipe:0 -c:v copy -c:a aac -b:a 160k -f mp4 -preset fast -movflags frag_keyframe+empty_moov pipe:1




It seems the function execution ends before the actual ffmpeg command, which then never finishes.



Is there a way to make the ffmpeg "synchronous" or "blocking" so that it finishes before the function execution ?


-
Secure and track every change to your Matomo installation with the Activity Log plugin
14 novembre 2017, par InnoCraft — PluginsAre you wondering how your colleagues are using Matomo (Piwik) ? Would you like to know if an unauthorized user got an access to your installation ? Would you like to remember the last actions you performed in Matomo some weeks ago ? At InnoCraft, we developed a plugin called “Activity Log”. With this feature you can easily track and check all major changes to your Matomo websites, for example : user permissions, goals, and funnels. In this article we will show you the different ways you can use it and explain why it is an invaluable plugin.
Activity log for better security
The activity log feature has been designed for security. Also referred to as “audit logging” or “audit trail”, with this plugin you will be able to :
- detect any suspicious actions
- detect hacker attacks
- help identify performance problems
- see clearly who did what, and when
- find out how people are using Matomo (Piwik) within your company
1 – detect any suspicious actions
With audit trail you can easily identify if a former employee still has access to your Matomo (Piwik) installation. You will then be able to know when he accessed it for the last time, and what changes she or he performed. If you got hacked, you will be able to find out if the user created, changed, or deleted any website, goals, or did anything else suspicious.
2 – detect hacker attacks
When an unregistered user is trying to access your Matomo (Piwik), each failed login attempt is registered within the Activity Log report.
3 – help identify performance problems
Activity Log can help you identify performance problems by registering the sequence of each major action a user performed. For example, if a user updated or installed a third party plugin, and suddenly Matomo (Piwik) is getting performance problems, then it is likely that the plugin update caused it.
4 – see clearly who did what, and when
It is always challenging in an organization to know who did what and when. With Activity Log, you will know who were the employee(s) that accessed Matomo (Piwik), created, updated, or deleted a goal, a funnel, a scheduled report, and much more.
5- find out how people are using Matomo within your company
By having a look at how people are using Matomo (Piwik) you will have an overview of how your colleagues use Matomo. For example, you can see who is creating Custom segments to analyse the audience in more details, who is creating funnels to learn where your users drop off. You will then be able to identify who has the knowledge and who needs training.
Did you know ?
You can help the Matomo (Piwik) core team make Matomo even better by sharing anonymously how you use Matomo on a day to day basis. You just need to install the following plugin : http://plugins.matomo.org/AnonymousPiwikUsageMeasurement
What’s in it ?
Once downloaded and installed from the marketplace, you will be able to access the activity log from the admin panel within the diagnostic section :
If you are logged as a super user administrator, you will get an overview and a detailed report about who accessed Matomo (Piwik) and which actions they performed.
Those reports are critical as they allow the super user to :
- ensure users are following all documented procedures within your organization such as naming conventions for reports, using the right settings when adding measurables…
- identify suspicious behavior. As those reports are gathering all major Matomo (Piwik) users activities it is easy to identify non conventional behavior.
- replay the sequence some users went through in order to fix any potential issues.
Activity log view report you can access through the admin panel
So you will see in a second if an unusual user got access to Matomo (Piwik) and the different actions the user performed.
It is also a good way to see the features that your users are using and identify potential misuse.As a regular user or admin, activity log is providing only the historical actions that this user performed :
Actions listed in the log include any changes (add, edit, delete) to the following features (this is a non exhaustive list) :
- Annotation
- Custom Alert
- Custom Dimension
- Goal
- Privacy settings
- Scheduled report
- Segment
- User
- Website
- …
This is a ideal to remember the actions they previously performed some weeks/months ago.
Where can I start from here ?
Activity log is a premium feature you can acquire through the Matomo (Piwik) marketplace. If you want to experience it before purchasing it, you can try it for free on our cloud infrastructure.
Activity log is just one out of the many great premium features developed by InnoCraft, the company founded by the creators of Matomo. Discover all their special plugins through the premium marketplace.
-
ffmpeg : StreamNotFound error
27 janvier 2017, par KMGI’m using Adobe Media server and push streams to this server using FMLE.
My stream name : appvideo
When I tried to pull the video from the server using ffmpeg/ffplay, I’m not getting "stream not found error". Whereas rtmpdump can stream the video.
After I see the logs, all the ffmpeg request logs have a stream name with extension .flv like [appvideo.flv]. But rtmpdump not append this extension [ like appvideo].
FFMpeg/ffplay log in Media server :
play stream 2017-01-27 02:26:17 GMT appvideo 10.11.12.202 32715 11 17 _defaultRoot_ _defaultVHost_ live _definst_ 0 404 183.82.250.50 rtmp - rtmp://10.11.12.202:443/live rtmp://10.11.12.202:443/live - -- 4702122229742256497 3135 3631 normal appvideo - - rtmp://10.11.12.202:443/live/appvideo.flv rtmp://10.11.12.202:443/live/appvideo.flv - flv 0 0.000000 0 - 0 0 - - - - 1 - -- - - - - - - -1 -1.000000 -
Not sure why request append .flv extension at last like this : rtmp ://10.11.12.202:443/live/appvideo.flv