From 9f9087ab498b190da41152ca8e67acdcf1274b44 Mon Sep 17 00:00:00 2001
From: Kirill Zhuravlev <kazhuravlev@fastmail.com>
Date: Mon, 20 Feb 2023 19:39:45 +0100
Subject: [PATCH] netlify config

---
 netlify.toml | 47 +++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 netlify.toml

diff --git a/netlify.toml b/netlify.toml
new file mode 100644
index 00000000..8a87f954
--- /dev/null
+++ b/netlify.toml
@@ -0,0 +1,47 @@
+# Settings in the [build] context are global and are applied to
+# all contexts unless otherwise overridden by more specific contexts.
+[build]
+# Directory to change to before starting a build.
+# This is where we will look for package.json/.nvmrc/etc.
+# If not set, defaults to the root directory.
+base = "./"
+
+# Directory that contains the deploy-ready HTML files and
+# assets generated by the build. This is relative to the base
+# directory if one has been set, or the root directory if
+# a base has not been set. This sample publishes the directory
+# located at the absolute path "root/project/build-output"
+
+publish = "out/"
+
+# Default build command.
+command = "echo 'default context'"
+
+[[plugins]]
+# Installs the Lighthouse Build Plugin for all deploy contexts
+package = "@netlify/plugin-lighthouse"
+
+# Production context: all deploys from the Production branch
+# set in your site’s Branches settings in the UI will inherit
+# these settings. You can define environment variables
+# here but we recommend using the Netlify UI for sensitive
+# values to keep them out of your source repository.
+[context.production]
+publish = "out/"
+
+# Redirects and headers are GLOBAL for all builds – they do not
+# get scoped to contexts no matter where you define them in the file.
+# For context-specific rules, use _headers or _redirects files,
+# which are PER-DEPLOY.
+
+[[redirects]]
+from = "/awesome-cloud-native"
+to = "/"
+status = 302
+force = true
+
+[[redirects]]
+from = "/awesome-go-fork"
+to = "/"
+status = 302
+force = true