DokuWiki

First, update your package list

sudo apt update

Next, install the dependencies required to install Ruby:

sudo apt install autoconf bison build-essential libssl-dev libyaml-dev libreadline6-dev zlib1g-dev libncurses5-dev libffi-dev libmysqlclient-dev libgdbm-dev

if anything breaks the installation, remove the particular dependency and install the other packages Once the dependencies download, you can install rbenv itself. Clone the rbenv repository from GitHub into the directory ~/.rbenv

git clone https://github.com/rbenv/rbenv.git ~/.rbenv

Next, add ~/.rbenv/bin to your $PATH so that you can use the rbenv command line utility. Do this by altering your ~/.bashrc file so that it affects future login sessions:

echo 'export PATH=“$HOME/.rbenv/bin:$PATH”' » ~/.bashrc

Then add the command eval “$(rbenv init -)” to your ~/.bashrc file so rbenv loads automatically:

echo 'eval “$(rbenv init -)”' » ~/.bashrc

Next, apply the changes you made to your ~/.bashrc file to your current shell session:

source ~/.bashrc

Verify that rbenv is set up properly by using the type command, which will display more information about the rbenv command:

type rbenv

Your terminal window will display something starts with rbenv is a function

Next, install the ruby-build, plugin. This plugin adds therbenv install command, which simplifies the installation process for new versions of Ruby:

git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build

With the ruby-build plugin now installed, you can install versions of Ruby y may need through a simple command. First, let’s list all the available versions of Ruby:

rbenv install -l

if the above command throws error, you need to close the terminal and open the terminal again to load bashrc file, setting up rbenv

Let’s install Ruby 2.6.3

rbenv install 2.6.3

Once it’s done installing, set it as our default version of Ruby with the global sub-command

rbenv global 2.6.3

Verify that Ruby was properly installed by checking its version number:

ruby -v

Gems are the way Ruby libraries are distributed. You use the gem command to manage these gems

When you install a gem, the installation process generates local documentation. This can add a significant amount of time to each gem’s installation process, so turn off local documentation generation by creating a file called ~/.gemrc which contains a configuration setting to turn off this feature

echo “gem: –no-document” > ~/.gemrc

Bundler is a tool that manages gem dependencies for projects. Install the Bundler gem, particularly the version 2.1.4

gem install bundler -v 2.1.4

To install it, update the package index on your server with apt

sudo apt update

Then install the default package

sudo apt install mysql-server

This will install MySQL latest version. below will install mysql 5.7, As part of installation you provide necessary input to set password for the root user

To deploy the meeting application, first we need to clone the meeting application repository. Every time deploy the application, go inside /home/expdev01/meeting/trunk

cd /home/expdev01/

create a directory meeting

mkir meeting

clone expertus meeting application inside meeting directory

cd meeting svn checkout https://repos.exphosted.com/svnrepos/meeting/server/trunk

install the required gems, with bundle command

cd trunk bundle install

Now, the capistrano gem is installed and ready for the deployment

cap production deploy

Above command will start deploy the meeting application to the actual directory, for that we need to create apps folder inside the home directory

cd /home/expdev01/ mkdir apps cd apps mkdir meeting

Copy shared files

As part of the deployment, script will stop due to shared files does not exit, we need to copy all the shared files under config folder in the working application or the existing servers

active_directory.yml bigbluebutton.yml database.yml storage.yml

all the above 4 files need to be copied and paste inside

/home/expdev01/apps/meeting/shared/config/

then redo the same deployment command

cap production deploy

once the deployment is success, can start/stop puma server with below 2 commands

cap production puma:stop cap production puma:start

If you face, any problem while start puma server, run the below command to start puma

RBENV_ROOT=~/.rbenv RBENV_VERSION=2.6.3 ~/.rbenv/bin/rbenv exec bundle exec puma -C /home/expdev01/apps/meeting/shared/puma.rb –daemon

configure nginx add below code to nginx configuration file and the restart the nginx service file - /etc/nginx/sites-enabled/bigbluebutton