Skip to main content

Redis Installation Steps




Redis is an in-memory key-value store known for its flexibility, performance, and wide language support” Inorder to install redis on your machine you need ubuntu 16.4 and a non-root user with sudo privileges to perform the administrative functions required for this process.
Download and Extract the Source Code
  • Create a tmp directory
    cd /tmp
  • Download the latest stable version of Redis
    curl -O http://download.redis.io/redis-stable.tar.gz
  • untar
    tar xzvf redis-stable.tar.gz
  • Move into the Redis source directory structure that was just extracted
    cd redis-stable

Build and Install Redis

  • Now, we can compile the Redis binaries by typing
    make
  • After the binaries are compiled, run the test suite to make sure everything was built correctly. You can do this by typing:
    make test
  • This will typically take a few minutes to run. Once it is complete, you can install the binaries onto the system by typing:
    sudo make install

Configure Redis

Now that Redis is installed, we can begin to configure it.
  • To start off, we need to create a configuration directory. We will use the conventional ‘/etc/redisdirectory’ which can be created by typing
         sudo mkdir /etc/redis
  • Now, copy over the sample Redis configuration file included in the Redis source archive:
    sudo cp /tmp/redis-stable/redis.conf /etc/redis
  • Next, we can open the file to adjust a few items in the configuration
         sudo nano /etc/redis/redis.conf
  • In the file, find the supervised directive. Currently, this is set to no. Since we are running an operating system that uses the systemd init system, we can change this to systemd
    /etc/redis/redis.conf
. . .



# If you run Redis from upstart or systemd, Redis can interact with your
# supervision tree. Options:
# supervised no - no supervision interaction
# supervised upstart - signal upstart by putting Redis into SIGSTOP mode
# supervised systemd - signal systemd by writing READY=1 to $NOTIFY_SOCKET
# supervised auto - detect upstart or systemd method based on
# UPSTART_JOB or NOTIFY_SOCKET environment variables
# Note: these supervision methods only signal "process is ready."
# They do not enable continuous liveness pings back to your supervisor.
supervised systemd



. . .
  • Next, find the dir directory. This option specifies the directory that Redis will use to dump persistent data. We need to pick a location that Redis will have write permission and that isn't viewable by normal users.
  • We will use the /var/lib/redis directory for this, which we will create in a moment:
/etc/redis/redis.conf
. . .



# The working directory.
#
# The DB will be written inside this directory, with the filename specified
# above using the 'dbfilename' configuration directive.
#
# The Append Only File will also be created inside this directory.
#
# Note that you must specify a directory here, not a file name.
dir /var/lib/redis


. . .
  • Save and close the file when you are finished.

Create a Redis systemd Unit File
  • Next, we can create a systemd unit file so that the init system can manage the Redis process. Create and open the /etc/systemd/system/redis.service file to get started:
    sudo nano /etc/systemd/system/redis.service
  • Inside, we can begin the [Unit] section by adding a description and defining a requirement that networking be available before starting this service
  • In the [Service] section, we need to specify the service's behavior. For security purposes, we should not run our service as root. We should use a dedicated user and group, which we will call redis for simplicity. We will create these momentarily.
  • To start the service, we just need to call the redis-server binary, pointed at our configuration. To stop it, we can use the Redis shutdown command, which can be executed with the redis-cli binary. Also, since we want Redis to recover from failures when possible, we will set the Restart directive to "always"
  • Finally, in the [Install] section, we can define the systemd target that the service should attach to if enabled (configured to start at boot):
    /etc/systemd/system/redis.service
[Unit]
Description=Redis In-Memory Data Store
After=network.target


[Service]
User=redis
Group=redis
ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf
ExecStop=/usr/local/bin/redis-cli shutdown
Restart=always


[Install]
WantedBy=multi-user.target
  • Save and close the file when you are finished.



Create the Redis User, Group and Directories
  • Now, we just have to create the user, group, and directory that we referenced in the previous two files.Begin by creating the redis user and group. This can be done in a single command by typing:
         sudo adduser --system --group --no-create-home redis
  • Now, we can create the /var/lib/redis directory by typing:
         sudo mkdir /var/lib/redis
  • We should give the redis user and group ownership over this directory:
         sudo chown redis:redis /var/lib/redis
  • Adjust the permissions so that regular users cannot access this location:
         sudo chmod 770 /var/lib/redis


Start the Redis Service
  • Start up the systemd service by typing:
    sudo systemctl start redis

  • Check that the service had no errors by running:
    sudo systemctl status redis


Test the Redis Instance Functionality
  • To test that your service is functioning correctly, connect to the Redis server with the command-line client:
    redis-cli

  • In the prompt that follows, test connectivity by typing:
    ping
    You should see:
    Output
    PONG

Comments

Popular posts from this blog

Redis Basic CRUD

We have seen how to setup on your linux machine here , now we will see how to perform basic CRUD operations using Spring Data & Redis server
We will be creating a simple application that would persist an employee information into redis database. You will be needing certain JARs like jedis.jar, spring-data-redis.jar etc details of which you can download and view at https://github.com/meta-magic/RedisCRUDexample.git 
First of all we will be creating the Employee entity, plz note that we are using the Serializable interface which automatically mapps the objects against the key.


Employee.java



importjava.io.Serializable;publicclassEmployeeimplementsSerializable{privatestaticfinallong serialVersionUID =-8243145429438016231L;

Progressive Web Apps

Deliver amazing user experience for WEB
Introduction
Progressive Web Apps (PWA) are user experience that reach for web. Its useful to users from the very first visit with no installation required. As the user spends more time with the web app it becomes more and more powerful, It loads quickly even on slower networks. Can have offline support, push notification, icon on home screen, full screen support. PWA are:
Reliable - load instantly even on slower/uncertain network.Fast - Respond quickly to user interactionsEngaging - Feel like natural app on device with amazing user experience.Reliable When launched from the user’s home screen, service workers enable a Progressive Web App to load instantly, regardless of the network state. A service worker, written in JavaScript, is like a client-side proxy and puts you in control of the cache and how to respond to resource requests. By pre-caching key resources you can eliminate the dependence on the network, ensuring an instant and reliable ex…

Zuul Edge Server

Zuul to Proxy your Microservices A common challenge when building microservices is providing a unified interface to the consumers of your system. The fact that your services are split into small composableappsshouldn’t be visible to users or result in substantial development effort. To solve this problem, Netflix created and open-sourced its Zuulproxy server. Zuul is an edge service that proxies requests to multiple backing services. It is “front door” to your system, which allows a browser, mobile app, or other user interface to consume services from multiple hosts without managing cross-origin resource sharing (CORS) and authentication for each one. Spring Cloud has created an embedded Zuul proxy to ease the development of a very common use case where a UI application wants to proxy calls to one or more back end services. This feature is useful for a user interface to proxy to the backend services it requires, avoiding the need to manage CORS and authentication concerns independentl…