-
Notifications
You must be signed in to change notification settings - Fork 247
User manual: installing MediacenterJS
- FFmpeg installed (included for Windows)
- NodeJS installed
- A modern browser like Chrome(ium)
- An internet connection
- Install MediacenterJS
https://github.com/jansmolders86/mediacenterjs-windows/raw/master/setup.exe
Starting MediacenterJS:
After running this installer and restarting you computer, run "mediacenterjs.exe" located in the root of the directory you've installed MediacenterJS to start the project. If you close this window, MCJS will stop working. You can also see useful information about what the server is doing, including error messages and other useful information.
Open a browser, preferably Chrome, and type in the address bar: http://localhost:3000 The program will boot in setup mode.
If this is the first time you are running MCJS, the application will try to automatically open a browser with the correct webpage for you.
please paste the following commands in your terminal:
Install latest version of Nodejs
curl -sL https://deb.nodesource.com/setup | sudo bash -
apt-get install nodejs
You can also install Nodejs on Ubuntu using:
sudo apt-get install npm
cd /usr/local/src
wget https://nodejs.org/dist/v4.2.2/node-v4.2.2-linux-x86.tar.gz
tar -xvzf node-v4.2.2.tar.gz
cd node-v4.2.2
sudo ./configure --without-snapshot
sudo make
sudo make install
which node
Once NodeJS is built, install sqlite3:
sudo apt-get install sqlite3
If you do not have a recent version of FFMPEG installed on your system you need to compile a new build:
# FFMPEG Dependencies
sudo apt-get update
sudo apt-get -y install autoconf automake build-essential git libass-dev libgpac-dev \
libsdl1.2-dev libtheora-dev libtool libva-dev libvdpau-dev libvorbis-dev libx11-dev \
libxext-dev libxfixes-dev pkg-config texi2html zlib1g-dev libmp3lame-dev yasm libopus-dev
mkdir ~/ffmpeg_sources
# Install xh264
cd ~/ffmpeg_sources
git clone --depth 1 git://git.videolan.org/x264.git
cd x264
./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin" --enable-static --disable-asm
make
make install
make distclean
# Install FFMPEG
cd ~/ffmpeg_sources
git clone --depth 1 git://source.ffmpeg.org/ffmpeg
cd ffmpeg
PKG_CONFIG_PATH="$HOME/ffmpeg_build/lib/pkgconfig"
export PKG_CONFIG_PATH
./configure --prefix="$HOME/ffmpeg_build" \
--extra-cflags="-I$HOME/ffmpeg_build/include" --extra-ldflags="-L$HOME/ffmpeg_build/lib" \
--bindir="$HOME/bin" --extra-libs="-ldl" --enable-gpl --enable-libass \
--enable-libmp3lame --enable-libtheora --enable-libvorbis \
--enable-libx264 --enable-nonfree --enable-libxcb
make
make install
make distclean
hash -r
. ~/.profile
For more information and troubleshooting: https://trac.ffmpeg.org/wiki/UbuntuCompilationGuide
Use Homebrew to install ffmpeg. Install Homebrew from here (http://brew.sh/)
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"
sudo chown -R $USER:admin /usr/local (Homebrew can create syslinks)
brew options ffmpeg ( shows additional options)
brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype --with-frei0r --with-libass
--with-libvo-aacenc --with-libvorbis --with-libvpx --with-opencore-amr --with-openjpeg
--with-opus --with-rtmpdump --with-schroedinger --with-speex --with-theora --with-tools
If you use a Git clone of MediacenterJS please use:
sudo apt-get install git # If you do not have git installed yet
git clone https://github.com/jansmolders86/mediacenterjs.git
cd mediacenterjs
npm install
npm start or node server
If you want to use NPM to install MediacenterJS use: (Please note that NPM does not necessary give you the latest version of the repo.)
npm install mediacenterjs
cd mediacenterjs
npm start or node server
Use 'sudo node server' if you use a port below 1000
The program will boot in setup mode, being accessible in your browser on http://localhost:3000 or http://'IP of the server':3000.
After the initial setup has been completed MediacenterJS will be available on the port you have specified and the language you have chosen. the server.js will make sure you do not have to restart the actual application (index.js) every time the configuration file changes.
Of course, if you change the port, you need to use that port after the initial setup.