
Recherche avancée
Autres articles (111)
-
Script d’installation automatique de MediaSPIP
25 avril 2011, parAfin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
La documentation de l’utilisation du script d’installation (...) -
Le plugin : Gestion de la mutualisation
2 mars 2010, parLe plugin de Gestion de mutualisation permet de gérer les différents canaux de mediaspip depuis un site maître. Il a pour but de fournir une solution pure SPIP afin de remplacer cette ancienne solution.
Installation basique
On installe les fichiers de SPIP sur le serveur.
On ajoute ensuite le plugin "mutualisation" à la racine du site comme décrit ici.
On customise le fichier mes_options.php central comme on le souhaite. Voilà pour l’exemple celui de la plateforme mediaspip.net :
< ?php (...) -
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 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 (...)
Sur d’autres sites (4278)
-
libopenjpeg encoding with ffmpeg
21 décembre 2012, par stibThe libopenjpeg codec for ffmpeg is deemed experimental. Does anyone know if it is useable for storage of archival video material, i.e. if I write a whole bunch of video files with it, am I likely top be able to open them in the future ?
Is there any other Free/OSS alternative to using ffmpeg for encoding motionJpeg2000, or for archiving video in general ?
-
installing yasm / nasm on heroku with vulcan
21 novembre 2013, par scientifficI'm trying to do a build of ffmpeg on Heroku, and I need to use libvpx. In order to install libvpx, I need to have nasm or yasm. I tried installing both using vulcan, but I keep getting the error Neither yasm not nasm has been found
Here is what I did
Installing Nasm
- get nasm source from http://www.linuxfromscratch.org/blfs/view/svn/general/NASM.html
- tar file using : tar -xJf nasm-2.10.09.tar.xz
- build using : vulcan build -v -s . -c "./configure -prefix=/app/vendor/nasm && make && make install"
- add the output of the tar file from vulcan to vendor/nasm
- push to heroku
Installing Yasm
- get yasm source from http://www.linuxfromscratch.org/blfs/view/svn/general/yasm.html
- extra tar file and build using : vulcan build -v -s . -c "./configure -prefix=/app/vendor/yasm && make && make install"
- add the output of the tar file from vulcan to vendor/yasm
- push to heroku
Installing Libvpx
- get libvpx source from http://www.linuxfromscratch.org/blfs/view/svn/multimedia/libvpx.html
- build libvpx using : vulcan build -v -s . -c "./configure —enable-shared —disable-static —prefix=/app/vendor/llibvpx && make && make install"
Attemping to build libvpx yields this error :
Packaging local directory... /.rvm/gems/ruby-1.9.2-p320/gems/vulcan-0.8.2/lib/vulcan/cli.rb:49: warning: Insecure world writable dir /usr/local in PATH, mode 040777
done
Uploading source package... done
Building with: ./configure --enable-shared --disable-static --prefix=/app/vendor/llibvpx && make && make install
Configuring selected codecs
enabling vp8_encoder
enabling vp8_decoder
Configuring for target 'x86_64-linux-gcc'
enabling x86_64
enabling pic
enabling runtime_cpu_detect
enabling mmx
enabling sse
enabling sse2
enabling sse3
enabling ssse3
enabling sse4_1
**Neither yasm nor nasm have been found**
Configuration failed. This could reflect a misconfiguration of your
toolchains, improper options selected, or another problem. If you
don't see any useful error messages above, the next step is to look
at the configure error log file (config.err) to determine what
configure was trying to do when it died.How can I successfully build libvpx on heroku using vulcan ?
The instructions I've been (loosely) following are from here :
https://gist.github.com/czivko/4392472
And the reason I need to use libvpx is that I'm using the carrierwave-video gem in my Rails app to convert videos, and it needs libvpx to convert to webm to support video playback in Firefox.
-
Anomalie #3315 (Fermé) : Champs obligatoires non renseignés : afficher un message en haut de page
28 octobre 2014, par cedric -Appliqué par commit r21729.