Command Flags
| Flag | Options | Description |
|---|---|---|
-codec:a |
libfaac, libfdk_aac, libvorbis | Audio Codec |
-quality |
best, good, realtime | Video Quality |
-b:a |
128k, 192k, 256k, 320k | Audio Bitrate |
-codec:v |
mpeg4, libx264, libvpx-vp9 | Video Codec |
Command Flags
| Flag | Options | Description |
|---|---|---|
-codec:a |
libfaac, libfdk_aac, libvorbis | Audio Codec |
-quality |
best, good, realtime | Video Quality |
-b:a |
128k, 192k, 256k, 320k | Audio Bitrate |
-codec:v |
mpeg4, libx264, libvpx-vp9 | Video Codec |
Brought to you by Headjack
FFmpeg is one of the most powerful tools for video transcoding and manipulation, but it's fairly complex and confusing to use. That's why I decided to create this cheat sheet which shows some of the most often used commands.
Let's start with some basics:
ffmpeg calls the FFmpeg application in the command line window, could also be the full path to the FFmpeg binary or .exe fileFor this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| /etc/supervisor/conf.d/sidekiq.conf | |
| [program:sidekiq] | |
| command=/usr/local/bin/sidekiq.sh | |
| directory=/usr/local/bin/ | |
| user=ubuntu | |
| startsecs=10 | |
| autostart=true | |
| autorestart=true | |
| stdout_logfile=/var/log/supervisor/sidekiq.log |
You can check here for getting the latest version. Change the wget url to download newer versions.
When a lot of people are working on the same Rails application, than Vagrant could help to set up environment quick and easy. Even Vagrant is not recommended for production, it is very usefull for testing deployment script. For production we can simply copy deployment script and run manually.
We can deploy Ruby on Rails app using a quick way to deploy ruby on rails on vagrant.
| # Download and Install the Latest Updates for the OS | |
| apt-get update && apt-get upgrade -y | |
| # Set the Server Timezone to CST | |
| echo "America/Chicago" > /etc/timezone | |
| dpkg-reconfigure -f noninteractive tzdata | |
| # Enable Ubuntu Firewall and allow SSH & MySQL Ports | |
| ufw enable | |
| ufw allow 22 |
| /** | |
| * Sample React Native App | |
| * https://github.com/facebook/react-native | |
| */ | |
| 'use strict'; | |
| var React = require('react-native'); | |
| var { | |
| AppRegistry, | |
| StyleSheet, |
| $( document ).ready( function() { | |
| $( "input.date" ).datepicker({ | |
| minDate: moment().subtract( "months", 1 ).toDate(), | |
| maxDate: moment().add( "months", 1 ).toDate(), | |
| dateFormat: "d M, y", | |
| constrainInput: true, | |
| beforeShowDay: $.datepicker.noWeekends | |
| }); |
| When starting a project that includes refinerycms-blog: | |
| $ rake refinery:override view=refinery/pages/* | |
| $ rake refinery:override view=layouts/* | |
| $ rake refinery:override view=refinery/blog/shared/* | |
| $ rake refinery:override view=refinery/blog/posts/* | |
| $ rake refinery:override view=refinery/* | |
| $ rake refinery:override controller=refinery/blog/* | |
| $ rake refinery:override controller=refinery/* |