All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Galbusera <gizero@gmail.com>
To: Pello Heriz <pello.heriz@alumni.mondragon.edu>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	meta-virtualization@yoctoproject.org,
	meta-xilinx@yoctoproject.org
Subject: Re: Redis on Yocto
Date: Wed, 3 May 2017 15:55:24 +0200	[thread overview]
Message-ID: <CAC+thW0o9Emp=53XNkWRLVwnmq6efEt3oR6thgJZGiqPt7PSeQ@mail.gmail.com> (raw)
In-Reply-To: <CAFL6qn7SykziH4rvKmcw2Gd0z5SEafiimTYkkhOAGe13vm+-TA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Hi,

On Wed, May 3, 2017 at 9:21 AM, Pello Heriz <
pello.heriz@alumni.mondragon.edu> wrote:

> Hi,
>
> I want to implement Redis in an image that I have created with Yocto
> master branch. What I have understood is that there are some recipes into
> meta-oe layer that support to have Redis in the created image. Anyway, what
> steps do I need to do in order to install/start-up/execute Redis in the
> created image on MPSoC QEMU?
>

As soon as meta-oe is in your conf/bblayers.conf, adding the following line
to your conf/local.conf should be enough to get the server enabled at boot
(at least with systemd as the chosen init system) with default
configuration
from meta-openembedded/meta-oe/recipes-extended/redis/redis/redis.conf in
whatever image you are building.

IMAGE_INSTALL_append = " redis"

You might want to override the default configuration with an appropriate
bbappend in one of your custom layers..

[-- Attachment #2: Type: text/html, Size: 1361 bytes --]

      reply	other threads:[~2017-05-03 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03  7:21 Redis on Yocto Pello Heriz
2017-05-03 13:55 ` Andrea Galbusera [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC+thW0o9Emp=53XNkWRLVwnmq6efEt3oR6thgJZGiqPt7PSeQ@mail.gmail.com' \
    --to=gizero@gmail.com \
    --cc=meta-virtualization@yoctoproject.org \
    --cc=meta-xilinx@yoctoproject.org \
    --cc=pello.heriz@alumni.mondragon.edu \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.