ffmpeg -i "Apache Sqoop Tutorial Part 1.mp4" -c copy -bsf:v h264_mp4toannexb -f mpegts intermediate1.ts
ffmpeg -i "Apache Sqoop Tutorial Part 2.mp4" -c copy -bsf:v h264_mp4toannexb -f mpegts intermediate2.ts
ffmpeg -i "Apache Sqoop Tutorial Part 3.mp4" -c copy -bsf:v h264_mp4toannexb -f mpegts intermediate3.ts
ffmpeg -i "Apache Sqoop Tutorial Part 4.mp4" -c copy -bsf:v h264_mp4toannexb -f mpegts intermediate4.ts
ffmpeg -i "concat:intermediate1.ts|intermediate2.ts|intermediate3.ts|intermediate4.ts" -c copy -bsf:a aac_adtstoasc "Apache Sqoop Tutorial.mp4"
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/bin/bash | |
| # It is probably redundant if you set settings mentioned in https://gist.github.com/zekefast/42273658939724ba7c7a . | |
| # But anyway it will not hurt anybody (sure if you are not putting your production database to RAM :)). | |
| # | |
| # Look for more detailed description in follow articles: | |
| # - http://blog.vergiss-blackjack.de/2011/02/run-postgresql-in-a-ram-disk/ | |
| # | |
| # ATTENTION: | |
| # DO NOT apply this approach if you store important data in postgresql cluster, because that could cause |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #!/usr/bin/python | |
| #-*-coding:utf8-*- | |
| import pyinotify,os,subprocess | |
| sourcePath = '/home/yjiang/foo/' | |
| targetPath = 'yjiang@test:/home/yjiang/sync_test/' | |
| wm = pyinotify.WatchManager() | |
| class rsync(): |
This is a collection of information on PostgreSQL and PostGIS for what I tend to use most often.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| from sqlalchemy.ext.declarative import declarative_base | |
| from sqlalchemy import Column, ForeignKey, Integer, String, ForeignKeyConstraint | |
| from sqlalchemy import create_engine | |
| from sqlalchemy.orm import sessionmaker, relationship | |
| Model = declarative_base() | |
| class Parent(Model): | |
| __tablename__ = 'parent' | |
| id = Column(Integer, primary_key=True) |
This is a short overview on how to completely remove any old mysql server installs in OSX and upgrade to MariaDB without conflicts. Things can get a bit weird when you have various old installs of MySQL server floating around, and utilizing homebrew to install and upgrade MariaDB as a drop in replacement for MySQL has worked well, especially if you're used to managing MySQL installs via yum in linux.
Backup all of your current databases with mysqldump
This isn't a tutorial on backups, and there are many ways to do it. You should know how to backup your data anyway. For this example, we'll do a full backup of our InnoDB databases.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| https://www.gnu.org/licenses/gpl-3.0.en.html | |
| GNU GENERAL PUBLIC LICENSE v3 |