From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] support/misc/Vagrantfile: Enable website
Date: Sat, 4 Feb 2017 23:50:43 +0100 [thread overview]
Message-ID: <20170204235043.2d80212c@free-electrons.com> (raw)
In-Reply-To: <1486247634-5995-1-git-send-email-angelo.compagnucci@gmail.com>
Hello,
On Sat, 4 Feb 2017 23:33:54 +0100, Angelo Compagnucci wrote:
> This patch enables buildroot website inside Vagrant
> and makes it accessible on localhost:8888 outside. It could be
> usefull for website development or simply navigating it
> without internet access.
>
> * Removed apt-get update to speedup first boot
> * Moved archive download at first to accomodate Apache
> * Added Apache configuration via here document
> * Added 80 to 8888 port redirection
>
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Why would we want to include this in the Vagrantfile? The point of
the Vagrantfile is to create a system that is known to work to use
Buildroot, not something for the few people who happen to work on
Buildroot's web site. So I really don't see why would we add all this
complexity to the Vagrantfile.
Could you explain the rationale ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-02-04 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 22:33 [Buildroot] [PATCH 1/1] support/misc/Vagrantfile: Enable website Angelo Compagnucci
2017-02-04 22:50 ` Thomas Petazzoni [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=20170204235043.2d80212c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox