Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/website: Improving website speed
Date: Thu, 23 Feb 2017 22:15:56 +0100	[thread overview]
Message-ID: <20170223221556.5e152293@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VkW5hdUHCU26w0bswKspdN-geT5me_2_pPOF=a=jzTKXw@mail.gmail.com>

Hello,

On Thu, 23 Feb 2017 22:08:05 +0100, Angelo Compagnucci wrote:

> My patch doesn't necessary requires a server side configuration
> change, usually the module I used in htaccess are enabled in common
> apache configuration. BTW the use of the modules by a virtualhost is
> not enabled by default and .htaccess simply enables it.
> On a shared webserver with hundres of websites for example, changing
> the cache control setting doesn't require the server sysadmin
> intervention, cause the htaccess is used to accomodate user
> preferences on a per site base.
> Buildroot is probably served by a shared webserver with the required
> modules enabled, but they are not correctly configured for the
> buildroot.org virtualhost.
> So simply dropping the .htaccess in the buildroot virtualhost root
> directory should do the trick and enable that configuraion.

Right. I want to see what the admins of the webserver have to say
though.

> Pngcrush is a software for reducing the size of png images without
> affecting quality. That means that we have to use less bandwidth to
> serve the same content as before.

I'm OK with what pngcrush does, but in your commit log, you said "The
images resized to ~60% of the original size.". To me it means that you
have reduced the size (in pixel) of the images to make them smaller in
size (in bytes).

Or is the 60% number just the saving (in bytes) thanks to using
pngcrush?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-02-23 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22 22:52 [Buildroot] [PATCH] docs/website: Improving website speed Angelo Compagnucci
2017-02-23 20:54 ` Thomas Petazzoni
2017-02-23 21:08   ` Angelo Compagnucci
2017-02-23 21:15     ` Thomas Petazzoni [this message]
2017-02-23 21:20       ` Angelo Compagnucci
2017-02-23 21:26         ` Thomas Petazzoni
2017-02-24  9:12       ` Arnout Vandecappelle
2017-02-24 17:15 ` Arnout Vandecappelle
2017-02-24 18:24   ` Angelo Compagnucci
2017-02-24 23:02     ` Arnout Vandecappelle
2017-03-01 21:18 ` Thomas Petazzoni

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=20170223221556.5e152293@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