Recherche avancée

Médias (0)

Mot : - Tags -/organisation

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (53)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP 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" (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP 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.

Sur d’autres sites (8682)

  • mpegaudioenc : Move some static tables to MpegAudioContext

    4 novembre 2013, par Diego Biurrun
    mpegaudioenc : Move some static tables to MpegAudioContext

    This reduces global state and the amount of globally visible tables.
    • [DBH] libavcodec/mpegaudioenc.c
    • [DBH] libavcodec/mpegaudiotab.h

  • Getting ffmpeg to work with Heroku

    23 octobre 2016, par scientiffic

    I attempted to install ffmpeg for my Heroku Rails app and now my app is crashing.

    I added a buildpack using the following command :

    heroku config:add BUILDPACK_URL=https://github.com/shunjikonishi/heroku-buildpack-ffmpeg

    After pushing to Heroku, I get the following error according to my logs :

    2013-11-17T17:50:44.022351+00:00 heroku[web.1]: Starting process with command `bundle exec rails server -p 47171`
    
2013-11-17T17:50:46.295602+00:00 app[web.1]: bash: bundle: command not found
    
2013-11-17T17:50:47.589491+00:00 heroku[web.1]: Process exited with status 127
    
2013-11-17T17:50:47.597968+00:00 heroku[web.1]: State changed from starting to crashed
    
2013-11-17T17:50:48.620853+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ (...) fwd="76.118.180.235" dyno= connect= service= status=503 bytes=
    
2013-11-17T17:50:48.847288+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=(...) fwd="76.118.180.235" dyno= connect= service= status=503 bytes=

    When I run heroku run rake db:migrate, I get the error :

    Running `rake db:migrate` attached to terminal... up, run.9791
    
(in /app)
    
rake aborted!
    
no such file to load -- bundler/setup
    
rubygems/custom_require>:29:in `require'
    
rubygems/custom_require>:29:in `require'
    
/app/config/boot.rb:6:in `<top>'
    
rubygems/custom_require>:29:in `require'
    
rubygems/custom_require>:29:in `require'
    
/app/config/application.rb:1:in `<top>'
    
rubygems/custom_require>:29:in `require'
    
rubygems/custom_require>:29:in `require'
    
/app/Rakefile:5:in `<top>'
    
/usr/local/lib/ruby/1.9.1/rake.rb:2373:in `load'
    
/usr/local/lib/ruby/1.9.1/rake.rb:2373:in `raw_load_rakefile'
    
/usr/local/lib/ruby/1.9.1/rake.rb:2007:in `block in load_rakefile'
    
/usr/local/lib/ruby/1.9.1/rake.rb:2058:in `standard_exception_handling'
    
/usr/local/lib/ruby/1.9.1/rake.rb:2006:in `load_rakefile'
    
/usr/local/lib/ruby/1.9.1/rake.rb:1991:in `run'
    
/usr/local/bin/rake:31:in `<main>'
    
</main></top></top></top>

    When I check the version of bundler I’m using (bundle show bundler), I get :

    /Users/(...).rvm/gems/ruby-1.9.3-p448/gems/bundler-1.3.5/lib/bundler.rb:284: warning: Insecure world writable dir /usr/local in PATH, mode 040777
    
/Users/(...)/.rvm/gems/ruby-1.9.3-p448/gems/bundler-1.3.5

    How can I solve this problem ?

  • lavc : remove the locking code in avcodec_close()

    5 avril 2014, par Anton Khirnov
    lavc : remove the locking code in avcodec_close()

    This function should not modify any global state, so there should be no
    
reason for any locking.
    • [DH] libavcodec/utils.c

Navigation