More actions
No edit summary |
No edit summary |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
== Purpose == | == Purpose == | ||
Sysadminafterdark docs serves as an internal source of truth for myself and the staff part of my organization. With this documentation, what you see is what you get. What's documented here is how it is deployed in my environment. I try to do things as publicly as possible, with some exceptions such as IP addresses, passwords, signing keys, and other sensitive documents that are dangerous to publicly release. From the public's perspective, it serves as an educational tool to peak into a live production environment while providing a window into how servers are staged, updated, secured, and interact through their lifecycle. This may seem like “boring”, somewhat mundane systems administration work, however unless you are actively a systems administrator or an IT professional, many are unaware of the daily goings on of the profession. | Sysadminafterdark docs serves as an internal source of truth for myself and the staff part of my organization. With this documentation, what you see is what you get. What's documented here is how it is deployed in my environment. I try to do things as publicly as possible, with some exceptions such as IP addresses, passwords, signing keys, and other sensitive documents that are dangerous to publicly release. From the public's perspective, it serves as an educational tool to peak into a live production environment while providing a window into how servers are staged, updated, secured, and interact through their lifecycle. This may seem like “boring”, somewhat mundane systems administration work, however unless you are actively a systems administrator or an IT professional, many are unaware of the daily goings on of the profession. | ||
== Internal Site Map == | |||
This website is broken down into multiple top level categories then broken down further by service or application in attempt to make finding things a bit easier. If you are looking for something specific, please use the search bar above. | |||
== External Site Map == | == External Site Map == | ||
[sysadminafterdark.com Blog] – Long form written content of various systems administration, homelab, and personal journeys. | [https://sysadminafterdark.com Blog] – Long form written content of various systems administration, homelab, and personal journeys. | ||
[docs.sysadminafterdark.com Docs] – You are here. This system was designed to hold all of my personal homelab public documentation, standards, and procedures. My goal is to have as much of my network publicly documented as possible. Unlike the blog, this is a living system. Information will change, links will break, and content will change over time as my homelab changes and grows. | |||
[forum.sysadminafterdark.com Forum] – The forum is a place to ask questions and engage with the community. It is split into multiple different categories based on various topics and technologies. | [https://docs.sysadminafterdark.com Docs] – You are here. This system was designed to hold all of my personal homelab public documentation, standards, and procedures. My goal is to have as much of my network publicly documented as possible. Unlike the blog, this is a living system. Information will change, links will break, and content will change over time as my homelab changes and grows. | ||
[gitlab.sysadminafterdark.com Git] – My GitLab server serves various scripts, configurations, and other code based things I have developed over the years. You can freely view all in-house developed code by searching and selecting various repositories. | |||
[status.sysadminafterdark.com Status] – Uptime is a publicly accessible Uptime Kuma dashboard that serves to inform the public the status of all public servers that hold this project together. If you can’t access something, chances are it is down due to error or I have a scheduled maintenance window in place. You can also follow my twitter for the latest status updates. | [https://forum.sysadminafterdark.com Forum] – The forum is a place to ask questions and engage with the community. It is split into multiple different categories based on various topics and technologies. | ||
[links.sysadminafterdark.com Follow Me] – A list of links to my various social media profiles. I utilize LinkStack to aggregate as much of my content as possible in one place. In addition to my various social media posts, this website also offers an RSS feed | |||
[https://gitlab.sysadminafterdark.com Git] – My GitLab server serves various scripts, configurations, and other code based things I have developed over the years. You can freely view all in-house developed code by searching and selecting various repositories. | |||
[https://status.sysadminafterdark.com Status] – Uptime is a publicly accessible Uptime Kuma dashboard that serves to inform the public the status of all public servers that hold this project together. If you can’t access something, chances are it is down due to error or I have a scheduled maintenance window in place. You can also follow my twitter for the latest status updates. | |||
[https://links.sysadminafterdark.com Follow Me] – A list of links to my various social media profiles. I utilize LinkStack to aggregate as much of my content as possible in one place. In addition to my various social media posts, this website also offers an RSS feed. | |||
== Contact Me == | == Contact Me == | ||
The best way to contact me is via the forum or X.com. I'd love to read your post if you have something to add, but should probably be done publicly so others can join in. Sometimes that's not good enough - for example if you find a security issue or bug in my code. If you need to contact me directly, please shoot me an email. | The best way to contact me is via the [https://forum.sysadminafterdark.com forum] or [https://twitter.com/sysadafterdark X.com]. I'd love to read your post if you have something to add, but should probably be done publicly so others can join in. Sometimes that's not good enough - for example if you find a security issue or bug in my code. If you need to contact me directly, please shoot me an [mailto:[email protected] email]. | ||
Latest revision as of 03:43, 13 November 2024
Getting Started
Welcome to sysadminafterdark docs! On the left sidebar you will find various technical topics with accompanying documentation.
In my documentation, we will deep dive into how my personal home production servers are setup, secured and the purpose behind them.
Whether you're interested in setting up a homelab for personal use or to enhance your professional skills, this wiki will provide you with baseline knowledge on how a real production environment works.
Purpose
Sysadminafterdark docs serves as an internal source of truth for myself and the staff part of my organization. With this documentation, what you see is what you get. What's documented here is how it is deployed in my environment. I try to do things as publicly as possible, with some exceptions such as IP addresses, passwords, signing keys, and other sensitive documents that are dangerous to publicly release. From the public's perspective, it serves as an educational tool to peak into a live production environment while providing a window into how servers are staged, updated, secured, and interact through their lifecycle. This may seem like “boring”, somewhat mundane systems administration work, however unless you are actively a systems administrator or an IT professional, many are unaware of the daily goings on of the profession.
Internal Site Map
This website is broken down into multiple top level categories then broken down further by service or application in attempt to make finding things a bit easier. If you are looking for something specific, please use the search bar above.
External Site Map
Blog – Long form written content of various systems administration, homelab, and personal journeys.
Docs – You are here. This system was designed to hold all of my personal homelab public documentation, standards, and procedures. My goal is to have as much of my network publicly documented as possible. Unlike the blog, this is a living system. Information will change, links will break, and content will change over time as my homelab changes and grows.
Forum – The forum is a place to ask questions and engage with the community. It is split into multiple different categories based on various topics and technologies.
Git – My GitLab server serves various scripts, configurations, and other code based things I have developed over the years. You can freely view all in-house developed code by searching and selecting various repositories.
Status – Uptime is a publicly accessible Uptime Kuma dashboard that serves to inform the public the status of all public servers that hold this project together. If you can’t access something, chances are it is down due to error or I have a scheduled maintenance window in place. You can also follow my twitter for the latest status updates.
Follow Me – A list of links to my various social media profiles. I utilize LinkStack to aggregate as much of my content as possible in one place. In addition to my various social media posts, this website also offers an RSS feed.
Contact Me
The best way to contact me is via the forum or X.com. I'd love to read your post if you have something to add, but should probably be done publicly so others can join in. Sometimes that's not good enough - for example if you find a security issue or bug in my code. If you need to contact me directly, please shoot me an email.