lnav | Log File Navigator , lnav for short , is an advanced log

I finally found the one that suits my needs.

I'm sharing this in case anyone who wants to use the same solution.

Thanks to sourav19, I followed your advice, even though it took me 8-10 hours to install and configure everything, but it's really what I want.

I had to buy a Digital Ocean droplet, cost me $20 to get a 4 GB of RAM, but I think it's much cheaper than buying the other log monitoring applications which are way too expensive.

Before installing docker, we have to enable Virtual Private Cloud (VPC), we will use the provided IP Address for our docker containers, so they can communicate between each other, by following this article.

I used a dockerized ELK, link is here

All we need to do is to clone the dockerized ELK to our server, and then go inside the cloned folder, and build the Dockerfile

I manage to solve the problem by tracing the problem by using

You are never setting the input's values. I'd suggest you use rails' form helpers like form_for and the rest. https://guides.rubyonrails.org/form_helpers.html#binding-a-form-to-an-object

If you need to build different pieces for different execution hosts, then the cleanest way to go about it is to build the build tools separately. One of the answers you linked describes a way to do this. If you have a well-written Autotools build system, however, then you might be able to tackle this differently, by leveraging out-of-source builds. This can be scripted.

Create a directory within which to build the tools. In that directory, configure for the build system (path-to-source-dir/configure), and then build (just) the needed tools. Then in the source directory or a different out-of-source build directory, configure for the cross-compilation by specifying the appropriate --build and --host triplets to configure, copy or link the already-built tools into the build directory, and perform the rest of the build.

If the build system is especially carefully crafted, then you may need to overcome provisions for different executable extensions for the build tools on different hosts. If you need to do this and you're planning to script the two-stage cross-compilation anyway, then you can probably handle the issue when you copy/link the tools; that will avoid any need to write special support for it into the core build system.

To support cross-compilation in general, configure.ac should use the AC_CANONICAL_BUILD and AC_CANONICAL_HOST macros, and the build machine will need to have an appropriate cross-compilation toolchain installed.

As the c9 window says "...; make sure it's on port $PORT with $IP as the IP address", this is, don't replace $PORT or $IP with your own values, they're values already defined, you can check it using echo $IP && echo $PORT.

Try running ruby hi.rb -p $PORT -o $IP within your Sinatra project directory.

You can also define the port and ip as environment variables as the flags you noticed say running the export PORT= && export IP= command, and then access to them within any ruby file as ENV['PORT'] or ENV['IP'].

Note: For some reason when I use the route get '/hi' it didn't work running on c9.io, but it did it correctly in my local machine, if you have the same mistake try just get '/'.