diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/404.html b/404.html new file mode 100644 index 0000000..7265da6 --- /dev/null +++ b/404.html @@ -0,0 +1,619 @@ + + + +
+ + + + + + + + + + + + + + + + + +++All notable changes to this project will be documented in this file. The format is based on +Keep a Changelog and this project adheres to +Semantic Versioning.
+
fmt
example output (5018825) - (Jimmy Briggs)Changelog generated by git-cliff.
+or individually:
+ +Date: 2024-04-04
+Status: Accepted
+Need to choose between Porkbun Email Hosting vs. Google Email Hosting.
+Migrated from Porkbun Email Hosting to Google Workspaces (Business Starter Subscription).
+Email forwarding aliases allow you to forward emails sent to one email address to another email address. This is useful if you have multiple email addresses and want to consolidate them into one inbox.
+From a business standpoint, email forwarding aliases can be used to create various email addresses for different departments or teams. For example, you could have an email address for sales, support, and billing, and have emails sent to those addresses forwarded to the appropriate team members.
+++Note: The process for creating email forwarding aliases will vary depending on your email provider / domain registrar.
+
Since we use Porkbub for our domain registration, we will use their email forwarding service to create email forwarding aliases.
+ +At No Clocks, we have configured email forwarding aliases to forward email sent to various aliases to always forward emails to a shared, "root" email address contact@noclocks.dev which, in turn, forwards the emails to both members of our team.
+This allows us to both receive and respond to emails sent to any of the aliases.
+Additionally, we have set up some short-hand versions of our full, personal email addresses for convenience. For example, emails sent to pat@noclocks.dev will be forwarded to patrick.howars@noclocks.dev and emails sent to jimmy@noclocks.dev will be forwarded to jimmy.briggs@noclocks.dev.
+Here is a graphical representation of our email forwarding strategy flow:
+graph LR
+ subgraph "Email Aliases"
+ admin["admin@noclocks.dev"]
+ contact["contact@noclocks.dev"]
+ dev["dev@noclocks.dev"]
+ feedback["feedback@noclocks.dev"]
+ hello["hello@noclocks.dev"]
+ help["help@noclocks.dev"]
+ legal["legal@noclocks.dev"]
+ news["news@noclocks.dev"]
+ privacy["privacy@noclocks.dev"]
+ sales["sales@noclocks.dev"]
+ schedule["schedule@noclocks.dev"]
+ store["store@noclocks.dev"]
+ support["support@noclocks.dev"]
+ team["team@noclocks.dev"]
+ test["test@noclocks.dev"]
+ end
+
+ subgraph ra["Root Alias"]
+ root["contact@noclocks.dev"]
+ end
+
+ subgraph "Team Members"
+
+ jimmybriggs["jimmy.briggs@noclocks.dev"]
+ patrickhoward["patrick.howard@noclocks.dev"]
+
+ end
+
+ admin --> root
+ contact --> root
+ dev --> root
+ feedback --> root
+ hello --> root
+ help --> root
+ legal --> root
+ news --> root
+ privacy --> root
+ sales --> root
+ schedule --> root
+ store --> root
+ support --> root
+ team --> root
+ test --> root
+
+ root --> jimmybriggs
+ root --> patrickhoward
+As you can see, emails sent to any of the email forwarding aliases will be forwarded to the shared root email address, which will then forward the emails to both team members.
+Here are the current email forwarding aliases we have set up for our domain:
+Forward | +To | +
---|---|
admin@noclocks.dev | +contact@noclocks.dev | +
contact@noclocks.dev | +jimmy.briggs@noclocks.dev | +
contact@noclocks.dev | +patrick.howard@noclocks.dev | +
dev@noclocks.dev | +contact@noclocks.dev | +
feedback@noclocks.dev | +contact@noclocks.dev | +
hello@noclocks.dev | +contact@noclocks.dev | +
help@noclocks.dev | +contact@noclocks.dev | +
jimmy@noclocks.dev | +jimmy.briggs@noclocks.dev | +
legal@noclocks.dev | +contact@noclocks.dev | +
news@noclocks.dev | +contact@noclocks.dev | +
pat@noclocks.dev | +patrick.howard@noclocks.dev | +
privacy@noclocks.dev | +contact@noclocks.dev | +
sales@noclocks.dev | +contact@noclocks.dev | +
schedule@noclocks.dev | +contact@noclocks.dev | +
store@noclocks.dev | +contact@noclocks.dev | +
support@noclocks.dev | +contact@noclocks.dev | +
team@noclocks.dev | +contact@noclocks.dev | +
test@noclocks.dev | +contact@noclocks.dev | +
And here is a screenshot of the email forwarding aliases we have set up in Porkbun:
+ +Email forwarding aliases are a powerful tool that can help you manage multiple email addresses and consolidate them into one inbox. By setting up email forwarding aliases, you can create different email addresses for different purposes and have all emails sent to those addresses forwarded to a central inbox.
+No Clocks, LLC | 2024
+ + + + + + + + + + +++This documentation outlines the system in place at No Clocks, LLC for setting up, maintaining, managing, provisioning, and tracking the various DNS records we have set up for our domain: noclocks.dev.
+
This documentation outlines the system in place at No Clocks, LLC for setting up, maintaining, managing, provisioning, and tracking the various DNS records we have set up for our domain: noclocks.dev.
"},{"location":"#contents","title":"Contents","text":""},{"location":"#navigation","title":"Navigation","text":"Tech Stack
DNS Records
Email Aliases
About
Contact
Changelog
All notable changes to this project will be documented in this file. The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
"},{"location":"changelog/#unreleased","title":"[Unreleased]","text":""},{"location":"changelog/#bug-fixes","title":"Bug Fixes","text":"fmt
example output (5018825) - (Jimmy Briggs)Changelog generated by git-cliff.
"},{"location":"contact/","title":"Contact","text":""},{"location":"contact/#email","title":"Email","text":"or individually:
Email forwarding aliases allow you to forward emails sent to one email address to another email address. This is useful if you have multiple email addresses and want to consolidate them into one inbox.
From a business standpoint, email forwarding aliases can be used to create various email addresses for different departments or teams. For example, you could have an email address for sales, support, and billing, and have emails sent to those addresses forwarded to the appropriate team members.
"},{"location":"email-aliases/#creating-email-forwarding-aliases","title":"Creating Email Forwarding Aliases","text":"Note: The process for creating email forwarding aliases will vary depending on your email provider / domain registrar.
Since we use Porkbub for our domain registration, we will use their email forwarding service to create email forwarding aliases.
At No Clocks, we have configured email forwarding aliases to forward email sent to various aliases to always forward emails to a shared, \"root\" email address contact@noclocks.dev which, in turn, forwards the emails to both members of our team.
This allows us to both receive and respond to emails sent to any of the aliases.
Additionally, we have set up some short-hand versions of our full, personal email addresses for convenience. For example, emails sent to pat@noclocks.dev will be forwarded to patrick.howars@noclocks.dev and emails sent to jimmy@noclocks.dev will be forwarded to jimmy.briggs@noclocks.dev.
"},{"location":"email-aliases/#graphical-representation","title":"Graphical Representation","text":"Here is a graphical representation of our email forwarding strategy flow:
graph LR\n subgraph \"Email Aliases\"\n admin[\"admin@noclocks.dev\"]\n contact[\"contact@noclocks.dev\"]\n dev[\"dev@noclocks.dev\"]\n feedback[\"feedback@noclocks.dev\"]\n hello[\"hello@noclocks.dev\"]\n help[\"help@noclocks.dev\"]\n legal[\"legal@noclocks.dev\"]\n news[\"news@noclocks.dev\"]\n privacy[\"privacy@noclocks.dev\"]\n sales[\"sales@noclocks.dev\"]\n schedule[\"schedule@noclocks.dev\"]\n store[\"store@noclocks.dev\"]\n support[\"support@noclocks.dev\"]\n team[\"team@noclocks.dev\"]\n test[\"test@noclocks.dev\"]\n end\n\n subgraph ra[\"Root Alias\"]\n root[\"contact@noclocks.dev\"]\n end\n\n subgraph \"Team Members\"\n\n jimmybriggs[\"jimmy.briggs@noclocks.dev\"]\n patrickhoward[\"patrick.howard@noclocks.dev\"]\n\n end\n\n admin --> root\n contact --> root\n dev --> root\n feedback --> root\n hello --> root\n help --> root\n legal --> root\n news --> root\n privacy --> root\n sales --> root\n schedule --> root\n store --> root\n support --> root\n team --> root\n test --> root\n\n root --> jimmybriggs\n root --> patrickhoward
As you can see, emails sent to any of the email forwarding aliases will be forwarded to the shared root email address, which will then forward the emails to both team members.
"},{"location":"email-aliases/#current-email-forwarding-aliases","title":"Current Email Forwarding Aliases","text":"Here are the current email forwarding aliases we have set up for our domain:
Forward To admin@noclocks.dev contact@noclocks.dev contact@noclocks.dev jimmy.briggs@noclocks.dev contact@noclocks.dev patrick.howard@noclocks.dev dev@noclocks.dev contact@noclocks.dev feedback@noclocks.dev contact@noclocks.dev hello@noclocks.dev contact@noclocks.dev help@noclocks.dev contact@noclocks.dev jimmy@noclocks.dev jimmy.briggs@noclocks.dev legal@noclocks.dev contact@noclocks.dev news@noclocks.dev contact@noclocks.dev pat@noclocks.dev patrick.howard@noclocks.dev privacy@noclocks.dev contact@noclocks.dev sales@noclocks.dev contact@noclocks.dev schedule@noclocks.dev contact@noclocks.dev store@noclocks.dev contact@noclocks.dev support@noclocks.dev contact@noclocks.dev team@noclocks.dev contact@noclocks.dev test@noclocks.dev contact@noclocks.devAnd here is a screenshot of the email forwarding aliases we have set up in Porkbun:
"},{"location":"email-aliases/#conclusion","title":"Conclusion","text":"Email forwarding aliases are a powerful tool that can help you manage multiple email addresses and consolidate them into one inbox. By setting up email forwarding aliases, you can create different email addresses for different purposes and have all emails sent to those addresses forwarded to a central inbox.
No Clocks, LLC | 2024
"},{"location":"overview/","title":"Overview","text":""},{"location":"techstack/","title":"Techstack","text":"# Tech Stack File ![](https://img.stackshare.io/repo.svg \"repo\") [noclocks/dns](https://github.com/noclocks/dns)![](https://img.stackshare.io/public_badge.svg \"public\") |4Tools used|03/08/24 Report generated| |------|------|"},{"location":"techstack/#languages-1","title":"Languages (1)","text":"JavaScript"},{"location":"techstack/#devops-3","title":"DevOps (3)","text":"Docker Git GitHub Actions Generated via [Stack File](https://github.com/marketplace/stack-file)"},{"location":"decisions/001-porkbun/","title":"Porkbun DNS","text":""},{"location":"decisions/002-dnscontrol/","title":"DNSControl IaC","text":""},{"location":"decisions/003-docker/","title":"Docker","text":""},{"location":"decisions/004-google-workspace/","title":"Google Workspace Email Migration","text":"Date: 2024-04-04
Status: Accepted
"},{"location":"decisions/004-google-workspace/#context","title":"Context","text":"Need to choose between Porkbun Email Hosting vs. Google Email Hosting.
"},{"location":"decisions/004-google-workspace/#decision","title":"Decision","text":"Migrated from Porkbun Email Hosting to Google Workspaces (Business Starter Subscription).
"},{"location":"decisions/004-google-workspace/#consequences","title":"Consequences","text":"
+
+ + JavaScript + + + |
+
+
+
+ + Docker + + + |
+
+
+
+ + Git + + + |
+
+
+
+ + GitHub Actions + + + |
+
+