mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Alexander Dahl <ada@thorsis.com>
Subject: Re: [ptxdist] [APPLIED] rootfs: Add option to create /var/www
Date: Fri, 12 Dec 2025 15:52:18 +0100	[thread overview]
Message-ID: <20251212145218.3034173-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251211100718.1261055-2-ada@thorsis.com>

Thanks, applied as 8e87fca5ae8b36dc5430d16576ae2fb68ac93a32.

Michael

[sent from post-receive hook]

On Fri, 12 Dec 2025 15:52:18 +0100, Alexander Dahl <ada@thorsis.com> wrote:
> Multiple packages like nginx, lighttpd, and jvisu are installing things
> to /var/www already, and create that path implicitly.  Make it explicit.
> 
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
> Message-Id: <20251211100718.1261055-2-ada@thorsis.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/rootfs.in b/rules/rootfs.in
> index 2b7c50363df0..93b53481d121 100644
> --- a/rules/rootfs.in
> +++ b/rules/rootfs.in
> @@ -256,6 +256,15 @@ config ROOTFS_VAR_TMP
>  	  system reboots. Say 'y' here to ensure a '/var/tmp' directory is
>  	  available at run-time.
>  
> +config ROOTFS_VAR_WWW
> +	bool
> +	prompt "/var/www"
> +	help
> +	  This directory is intended for webserver application data.
> +	  Usually things like html or javascript files go here.
> +	  Say 'y' here to ensure a '/var/www' directory is available at
> +	  run-time.
> +
>  endmenu
>  endif # ROOTFS
>  
> diff --git a/rules/rootfs.make b/rules/rootfs.make
> index 1c1e5501cf83..656fbe4ba5a7 100644
> --- a/rules/rootfs.make
> +++ b/rules/rootfs.make
> @@ -145,6 +145,9 @@ ifdef PTXCONF_ROOTFS_VAR_OVERLAYFS
>  	@$(call install_link, rootfs, ../var.mount, \
>  		/usr/lib/systemd/system/local-fs.target.requires/var.mount)
>  endif
> +ifdef PTXCONF_ROOTFS_VAR_WWW
> +	@$(call install_copy, rootfs, 0, 0, 0755, /var/www)
> +endif
>  
>  #	#
>  #	# install files in rootfs



  reply	other threads:[~2025-12-12 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 10:07 [ptxdist] [PATCH 0/3] rootfs: Create /var/www and allow webservers to depend on it Alexander Dahl via ptxdist
2025-12-11 10:07 ` [ptxdist] [PATCH 1/3] rootfs: Add option to create /var/www Alexander Dahl via ptxdist
2025-12-12 14:52   ` Michael Olbrich [this message]
2025-12-11 10:07 ` [ptxdist] [PATCH 2/3] nginx: Select rootfs /var/www dependency Alexander Dahl via ptxdist
2025-12-12 14:52   ` [ptxdist] [APPLIED] " Michael Olbrich
2025-12-11 10:07 ` [ptxdist] [PATCH 3/3] lighttpd: " Alexander Dahl via ptxdist
2025-12-12 14:52   ` [ptxdist] [APPLIED] " Michael Olbrich

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=20251212145218.3034173-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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