GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: GNU/Weeb Mailing List <[email protected]>
Cc: Ammar Faizi <[email protected]>,
	Irvan Malik <[email protected]>,
	Memet Zx <[email protected]>
Subject: [PATCH website v1 0/2] nginx integration
Date: Thu, 20 Oct 2022 06:59:24 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi,

This is the starting point of the web server integration (nginx).
There are two patches in this series.

# Patch 1: Lock file update after "npm install".

After invoking "npm install" command, these two lock files are changed.
Sycn them with this commit.

# Patch 2: Create logs directory for nginx log.

Create "logs" directory inside the project directory, ignore all files
inside this directory except the ".gitignore" file. We will use this
directory to save access.log and error.log from the nginx web server.

Signed-off-by: Ammar Faizi <[email protected]>
---

Ammar Faizi (2):
  Lock file update after "npm install"
  Create logs directory for nginx log

 logs/.gitignore   |     2 +
 package-lock.json | 13357 ++++++++++++++++++++++++++++++++++++++++++++
 yarn.lock         |  8446 ++++++++++++++--------------
 3 files changed, 17568 insertions(+), 4237 deletions(-)
 create mode 100644 logs/.gitignore
 create mode 100644 package-lock.json

-- 
Ammar Faizi


             reply	other threads:[~2022-10-19 23:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 23:59 Ammar Faizi [this message]
2022-10-19 23:59 ` [PATCH website v1 2/2] Create logs directory for nginx log Ammar Faizi
2022-10-20  0:03 ` [PATCH website v1 0/2] nginx integration Ammar Faizi

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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