<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>404x.io</title>
    <link>https://www.404x.io/</link>
    <description>404x.io</description>
    <language>zh-CN</language>
    <lastBuildDate>Tue, 10 Nov 2026 22:21:27 GMT</lastBuildDate>
    <atom:link href="https://www.404x.io/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TradingAgents 实操指南：从零搭建一个多智能体金融分析框架</title>
      <link>https://www.404x.io/2026/11/05/TradingAgents/</link>
      <guid isPermaLink="true">https://www.404x.io/2026/11/05/TradingAgents/</guid>
      <pubDate>Thu, 05 Nov 2026 11:57:53 GMT</pubDate>
      <description>TradingAgents 实操指南：从零搭建一个多智能体金融分析框架 本文基于 TauricResearch/TradingAgents 开源项目撰写，聚焦于安装、配置与运行的完整流程。需要提前说明的是，该框架官方定位为研究工具，其交易表现受模型选择、温度参数、数据质量等多重因素影响，不构成任何投资建议。请以学习多智能体协作逻辑的心态来使用它。 一、这个项目是什么？ TradingAgents 用 LLM 驱动的多个智能体，模拟真实交易公司的组织分工： 注：上图为项目官方架构图，展示了从分析师团队到组合经理的完整决策链路。* 用一张简化的流程图来理解它的协作逻辑： 关键设计*：四位分析师并行工作，各自使用独立工具；等全部报告完成后</description>
      <category>ai</category>
      <category>multi-agent</category>
      <category>trading</category>
      <category>llm</category>
    </item>
    <item>
      <title>Enabling Google Authenticator for SSH Logon on Linux Server</title>
      <link>https://www.404x.io/2025/02/25/Linux-Server-enable-Google-Authenticator/</link>
      <guid isPermaLink="true">https://www.404x.io/2025/02/25/Linux-Server-enable-Google-Authenticator/</guid>
      <pubDate>Tue, 25 Feb 2025 01:17:25 GMT</pubDate>
      <description>This guide explains how to set up Google Authenticator for Two-Factor Authentication (2FA) on a Linux server for SSH logon. Prerequisites A Linux server (Ubuntu/Debian/CentOS, etc.) SSH access to the server A smartphone with the Google Authenticator app installed Steps 1. Install Google Authenticator PAM Module For Ubu</description>
      <category>linux</category>
      <category>ssh</category>
      <category>2fa</category>
      <category>pam</category>
    </item>
    <item>
      <title>SQL Server High Availability (HA) Solutions</title>
      <link>https://www.404x.io/2025/01/28/SQL-Server-High-Availability-HA-Solutions/</link>
      <guid isPermaLink="true">https://www.404x.io/2025/01/28/SQL-Server-High-Availability-HA-Solutions/</guid>
      <pubDate>Tue, 28 Jan 2025 09:28:43 GMT</pubDate>
      <description>1. 数据库镜像（Database Mirroring） 原理： 数据库镜像技术通过维护两个数据库副本（一个主副本和一个镜像副本）来提供高可用性。在数据库镜像中，主数据库会将其事务日志发送到镜像数据库，并实时应用。镜像模式可以是同步模式（保证数据一致性）或异步模式（提高性能但可能导致数据丢失）。 使用场景： 小型企业或简单的应用：适用于对高可用性要求较低，且只需提供灾难恢复的场景。 低预算项目：成本较低，部署和管理相对简单。 灾难恢复：在灾难发生时，可以迅速将主数据库切换到镜像数据库。 优缺点： 优点：简单，低成本，支持自动故障转移。 缺点：不支持扩展，性能可能受影响，不能用于读写分离。 最佳实践：</description>
      <category>high-availability</category>
      <category>sql-server</category>
      <category>database-mirroring</category>
      <category>always-on</category>
      <category>failover-cluster</category>
    </item>
    <item>
      <title>Enable Nvidia Runtime on Docker</title>
      <link>https://www.404x.io/2024/10/19/Enable-Nvidia-Runtime-on-Docker/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/10/19/Enable-Nvidia-Runtime-on-Docker/</guid>
      <pubDate>Sat, 19 Oct 2024 16:49:10 GMT</pubDate>
      <description>Make Sure nvidia succeed installed on your machine : Installing the NVIDIA Container Toolkit on host https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html#installing-with-yum-or-dnf Configure on Docker https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install</description>
      <category>docker</category>
      <category>nvidia</category>
      <category>gpu</category>
      <category>container-toolkit</category>
    </item>
    <item>
      <title>LoadBalancer for Bare Metal Kubernetes Cluster-MetalLB</title>
      <link>https://www.404x.io/2024/10/13/LoadBalancer-for-bare-metal-Kubernetes-cluster-MetalLB/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/10/13/LoadBalancer-for-bare-metal-Kubernetes-cluster-MetalLB/</guid>
      <pubDate>Sun, 13 Oct 2024 06:29:42 GMT</pubDate>
      <description>在 Kubernetes 中，对于 LoadBalancer 类型的 Service，k8s 并没有为裸机集群实现负载均衡器，因此我们只有在以下 IaaS 平台（GCP, AWS, Azure）上才能使用 LoadBalancer 类型的 service。 因此裸机集群只能使用 NodePort 或者 externalIPs service 来对面暴露服务，然而这两种方式和 LoadBalancer service 相比都有很大的缺点,而 MetalLB 的出现就是为了解决这个问题。 也就是说在裸机的 K8s 集群无法使用 LoadBancer 类型的 Service。否则，您会发现 LoadBancer 的 Service 一直处</description>
      <category>kubernetes</category>
      <category>metallb</category>
      <category>load-balancer</category>
      <category>bare-metal</category>
    </item>
    <item>
      <title>Kubernetes-Docker-Network</title>
      <link>https://www.404x.io/2024/10/12/Kubernetes-docker-network/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/10/12/Kubernetes-docker-network/</guid>
      <pubDate>Sat, 12 Oct 2024 13:59:41 GMT</pubDate>
      <description>1、Kubernetes网络模型和CNI插件 在Kubernetes中设计了一种网络模型，要求无论容器运行在集群中的哪个节点，所有容器都能通过一个扁平的网络平面进行通信，即在同一IP网络中。需要注意的是：在K8S集群中，IP地址分配是以Pod对象为单位，而非容器，同一Pod内的所有容器共享同一网络名称空间。 1.1、Docker网络模型 了解Docker的友友们都应该清楚，Docker容器的原生网络模型主要有3种：Bridge（桥接）、Host（主机）、none。 Bridge：借助虚拟网桥设备为容器建立网络连接。 Host：设置容器直接共享当前节点主机的网络名称空间。 none：多个容器共享同一个网络名称空间。 从上可以看到容器内</description>
      <category>kubernetes</category>
      <category>docker</category>
      <category>cni</category>
      <category>networking</category>
    </item>
    <item>
      <title>Kubernetes-Install-Kubeapps</title>
      <link>https://www.404x.io/2024/08/09/Kubernetes-install-kubeapps/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/09/Kubernetes-install-kubeapps/</guid>
      <pubDate>Fri, 09 Aug 2024 07:49:17 GMT</pubDate>
      <description>Helm install Kubeapps install</description>
      <category>kubernetes</category>
      <category>kubeapps</category>
      <category>helm</category>
    </item>
    <item>
      <title>Kubernetes-Argo-CD</title>
      <link>https://www.404x.io/2024/08/08/Kubernetes-Argo-CD/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/08/Kubernetes-Argo-CD/</guid>
      <pubDate>Thu, 08 Aug 2024 19:39:29 GMT</pubDate>
      <description>Kubernetes高级工具Argo CD https://argo-cd.readthedocs.io/en/stable/ Argo CD 是针对 Kubernetes 的声明式 GitOps 持续交付工具。 Argo CD 是一个为 Kubernetes 而生的，遵循声明式 GitOps 理念的持续部署（CD）工具。 Argo CD 可在 Git 存储库更改时自动同步和部署应用程序。 安装argo cd</description>
      <category>kubernetes</category>
      <category>argo-cd</category>
      <category>gitops</category>
    </item>
    <item>
      <title>Frps Server for LAN</title>
      <link>https://www.404x.io/2024/08/07/frps-server-for-LAN/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/07/frps-server-for-LAN/</guid>
      <pubDate>Wed, 07 Aug 2024 17:12:33 GMT</pubDate>
      <description>局域网穿透：顾名思义，就是在没有公网IP的情况下，实现从公网访问局域网络的一种技术统称。 局域网内网穿透的很多方式： Cloudflare Tunnel 实现： nps： frps： 我们今天要展示的就是frps实现局域网内网穿透，以上所有的方式都是CS模式，分为服务器端和本地端展开: 服务器端： 本地客户端 验证：在服务端检查，确认客户端和服务端已经建立通信。</description>
      <category>reverse-proxy</category>
      <category>frp</category>
      <category>nat-traversal</category>
    </item>
    <item>
      <title>Kubernetes-Storage-PV-PVC</title>
      <link>https://www.404x.io/2024/08/07/Kubernetes-storage/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/07/Kubernetes-storage/</guid>
      <pubDate>Wed, 07 Aug 2024 11:44:22 GMT</pubDate>
      <description>Kubernetes 存储实战指南：从 PV/PVC 到分布式存储服务器搭建 容器天生是&amp;quot;短命&amp;quot;的，Pod 重启或重新调度后，写在容器内部的数据会消失。Kubernetes 存储要解决的核心问题就是：让数据活得比 Pod 久。这篇指南从零开始，带你理解 PV、PVC、StorageClass 的关系，并给出可直接执行的代码实例，最后扩展到常见的分布式存储选型与存储服务器的快速搭建。 目录 一、核心概念：三分钟搞懂 PV、PVC、StorageClass 二、动手实战：从静态 PV 到动态供给 三、生产级实战：WordPress + MySQL 持久化部署 四、常见分布式存储选型对比 五、避坑清单与最佳实践 六、快</description>
      <category>kubernetes</category>
      <category>persistent-volume</category>
      <category>storage-class</category>
      <category>storage</category>
    </item>
    <item>
      <title>Kubernetes-Argo-Rollout</title>
      <link>https://www.404x.io/2024/08/06/Kubernetes-Argo-Rollout/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/06/Kubernetes-Argo-Rollout/</guid>
      <pubDate>Tue, 06 Aug 2024 18:18:11 GMT</pubDate>
      <description>Argo 介绍 https://argoproj.github.io/ Argo 是一个开源项目，旨在提供一套用于在 Kubernetes 上运行和管理容器化工作负载的工具。 Argo 项目最早在2017年由Applatix公司创立开源,在2018年被美国加利福尼的 Intuit 公司收购并持续维护，并得到了广泛的社区支持。 Argo 项目主要包括以下几个子项目，每个子项目都有其特定的用途: Argo Workflows: 简介: Argo Workflows 是一个 Kubernetes 原生的工作流引擎，用于在 Kubernetes 集群上创 建、管理和协调容器化任务。 用途: 支持DAG(有向无环图 Directed Acyc</description>
      <category>kubernetes</category>
      <category>argo-rollouts</category>
      <category>progressive-delivery</category>
    </item>
    <item>
      <title>DevOps Practice</title>
      <link>https://www.404x.io/2024/08/04/Devops-Practice/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/04/Devops-Practice/</guid>
      <pubDate>Sun, 04 Aug 2024 09:08:17 GMT</pubDate>
      <description>一、DevOps介绍 软件开发最开始是由两个团队组成： 开发计划由开发团队从头开始设计和整体系统的构建。需要系统不停的迭代更新。 运维团队将开发团队的Code进行测试后部署上线。希望系统稳定安全运行。 这看似两个目标不同的团队需要协同完成一个软件的开发。 在开发团队指定好计划并完成coding后，需要提供到运维团队。 运维团队向开发团队反馈需要修复的BUG以及一些需要返工的任务。 这时开发团队需要经常等待运维团队的反馈。这无疑延长了事件并推迟了整个软件开发的周期。 会有一种方式，在开发团队等待的时候，让开发团队转移到下一个项目中。等待运维团队为之前的代码提供反馈。 可是这样就意味着一个完整的项目需要一个更长的周期才可以开发出最终代码</description>
      <category>devops</category>
      <category>git</category>
      <category>gitlab</category>
      <category>jenkins</category>
      <category>ci-cd</category>
    </item>
    <item>
      <title>K8s Ingress-Nginx Tutorial</title>
      <link>https://www.404x.io/2024/08/02/k8s-ingress-nginx-Tutorial/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/08/02/k8s-ingress-nginx-Tutorial/</guid>
      <pubDate>Fri, 02 Aug 2024 13:36:32 GMT</pubDate>
      <description>Ingress-Nginx deploy https://github.com/kubernetes/ingress-nginx/blob/main/docs/deploy/index.md Create kubernetes Ingress-Nginx resource 单域名匹配</description>
      <category>kubernetes</category>
      <category>nginx</category>
      <category>ingress-nginx</category>
    </item>
    <item>
      <title>Velero Backup and Restore K8s Cluster</title>
      <link>https://www.404x.io/2024/06/28/Velero-backup-and-restore-k8s-cluster/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/06/28/Velero-backup-and-restore-k8s-cluster/</guid>
      <pubDate>Fri, 28 Jun 2024 11:19:11 GMT</pubDate>
      <description>Velero部署及使用示例 Velero是用于备份和恢复 Kubernetes 集群资源和PV的开源项目。 基于Velero CRD创建备份（Backup）和恢复作业（Restore） 可以备份或恢复集群中的几乎所有对象，也可以按类型、名称空间或标签过滤对象 支持基于文件系统备份（File System Backup，简称FSB）备份Pod卷中的数据，并借助于restic或kopia上传到对象存储系统上 支持基于快照备份PV，这种方式较之FSB能确保文件的一致性；它支持两种操作 仅创建PV快照 创建PV快照，并借助于restic或kopia上传到对象存储系统上 使用对象存储作为备份数据的存储目标，并基于对象存储上的备份对象完成数据恢</description>
      <category>kubernetes</category>
      <category>velero</category>
      <category>backup</category>
      <category>restore</category>
    </item>
    <item>
      <title>OpenWRT ROOT Relocation</title>
      <link>https://www.404x.io/2024/05/29/OpenWRT-ROOT-Relocation/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/05/29/OpenWRT-ROOT-Relocation/</guid>
      <pubDate>Wed, 29 May 2024 05:45:50 GMT</pubDate>
      <description>Why are we doing this? Sometime customized openwrt OS root partion(/) is too small, we need extend or Relocate the root path. Let&apos;s get started Update in fstab before next boot</description>
      <category>homelab</category>
      <category>openwrt</category>
      <category>partitions</category>
    </item>
    <item>
      <title>Homelab PXE Server iVentoy</title>
      <link>https://www.404x.io/2024/05/24/Homelab-PXE-Server-iVentoy/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/05/24/Homelab-PXE-Server-iVentoy/</guid>
      <pubDate>Fri, 24 May 2024 02:33:19 GMT</pubDate>
      <description>What is iVentoy https://www.iventoy.com/en/index.html iVentoy is an enhanced version of the PXE server. With iVentoy you can boot and install OS on multiple machines at the same time through the network. iVentoy is extremely easy to use, without complicated configuration, just put the ISO file in the specified location</description>
      <category>pxe</category>
      <category>iventoy</category>
      <category>homelab</category>
    </item>
    <item>
      <title>Static Web Resources Hosted on Cloudflare and Azure</title>
      <link>https://www.404x.io/2024/05/10/Static-web-resources-hosted-on-Cloudflare-and-Azure/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/05/10/Static-web-resources-hosted-on-Cloudflare-and-Azure/</guid>
      <pubDate>Fri, 10 May 2024 04:36:44 GMT</pubDate>
      <description>Deploy to Cloudflare Deploy to Azure 91PRGfEWssk</description>
      <category>deployment</category>
      <category>static-site</category>
      <category>cloudflare-pages</category>
      <category>azure-static-web-apps</category>
    </item>
    <item>
      <title>Cloudflare Tunnel 实现内网穿透</title>
      <link>https://www.404x.io/2024/05/09/Cloudflare-Tunnel-实现内网穿透/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/05/09/Cloudflare-Tunnel-实现内网穿透/</guid>
      <pubDate>Thu, 09 May 2024 08:33:10 GMT</pubDate>
      <description>Prepare work Cloudflare Account A Domain name which register under Cloudflare Setup steps Cloudflare Dashboard –&amp;gt; Zero Trust –&amp;gt; Networks –&amp;gt;Tunnels-&amp;gt; Create new Tunnels –&amp;gt; Connector(Cloudflared) Tips If you have multiple applications on one server, recommend use docker to create multiple connectors for ea</description>
      <category>cloudflare-tunnel</category>
      <category>reverse-proxy</category>
      <category>zero-trust</category>
    </item>
    <item>
      <title>Sqlcmd Client Connection Error to Sqlserver on Windows Server</title>
      <link>https://www.404x.io/2024/04/09/sqlcmd-client-Connection-error-to-sqlserver-on-windows-server/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/04/09/sqlcmd-client-Connection-error-to-sqlserver-on-windows-server/</guid>
      <pubDate>Tue, 09 Apr 2024 02:27:40 GMT</pubDate>
      <description>Case scenario I installed SQL Server 2019 on Windows Server 2022, When I successful installed SQL Server, local connection with sql server management studio all good. Well, when I tried to using sqlcmd to connect the SQL Server on another Linux machine. I encountered an issue like this: Troubleshooting Check SQL server</description>
      <category>sql-server</category>
      <category>troubleshooting</category>
      <category>connectivity</category>
      <category>sqlcmd</category>
    </item>
    <item>
      <title>Customize windowsPE Image for PXE Server</title>
      <link>https://www.404x.io/2024/04/08/Customize-windowsPE-image-for-PXE-server/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/04/08/Customize-windowsPE-image-for-PXE-server/</guid>
      <pubDate>Mon, 08 Apr 2024 09:11:34 GMT</pubDate>
      <description>Work Env Windows ADK (September 2023) Windows PE add-on for the Windows ADK (September 2023) Download Intel LAN Drivers for My PC Why need this step: Sometimes we need using WinPE OS network to communicate with Internet or access internal CIFS share like below: Intel LAN Drivers v29.0: https://www.intel.com/content/www</description>
      <category>windows-pe</category>
      <category>pxe</category>
      <category>drivers</category>
      <category>deployment</category>
    </item>
    <item>
      <title>Azure Arc-Enbaled SQL Server Instance With AKS</title>
      <link>https://www.404x.io/2024/03/30/Azure-Arc-Enbaled-SQL-Server-instance-with-AKS/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/03/30/Azure-Arc-Enbaled-SQL-Server-instance-with-AKS/</guid>
      <pubDate>Sat, 30 Mar 2024 15:35:59 GMT</pubDate>
      <description>Azure data controller Setup https://docs.microsoft.com/en-us/azure/azure-arc/data/create-data-controller-direct-cli?tabs=windows create resources group create aks Get azure aks kubectl admin access check k8s context for current environment</description>
      <category>azure-arc</category>
      <category>sql-server</category>
      <category>azure-kubernetes-service</category>
      <category>azure-data-controller</category>
    </item>
    <item>
      <title>Sql Server Best Practice</title>
      <link>https://www.404x.io/2024/03/30/sql-server-best-practice/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/03/30/sql-server-best-practice/</guid>
      <pubDate>Sat, 30 Mar 2024 15:24:55 GMT</pubDate>
      <description>CPU最佳实践。 根据CPU架构和核数配置MaxDop. https://learn.microsoft.com/zh-CN/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option?view=sql-server-ver16 内存最佳实践。 Sqlserver的内存尽量占用至主机的85%~80%之间。 日常管理相关建议。 日志文件和数据文件尽量分别放置在不同的磁盘上有利于磁盘带宽的分配。 对于数据库文件较大的数据库，如果空间使用率很高。对于这方面的优化建议定期检查文件大小及空间使</description>
      <category>sql-server</category>
      <category>performance</category>
      <category>best-practices</category>
      <category>configuration</category>
    </item>
    <item>
      <title>Arc SQL MI With Multi-Cloud </title>
      <link>https://www.404x.io/2024/03/30/Arc-SQL-MI-Multi-cloud-Database-failover-with-Distributed-AG/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/03/30/Arc-SQL-MI-Multi-cloud-Database-failover-with-Distributed-AG/</guid>
      <pubDate>Sat, 30 Mar 2024 15:16:39 GMT</pubDate>
      <description>Arc SQL MI: Multi-cloud Database failover with Distributed AG https://techcommunity.microsoft.com/t5/azure-architecture-blog/arc-sql-mi-demonstrating-multi-cloud-database-failover-using/ba-p/2936589 Azure Arc-enabled SQL Managed Instance - disaster recovery https://learn.microsoft.com/en-us/azure/azure-arc/data/managed</description>
      <category>azure-arc</category>
      <category>sql-managed-instance</category>
      <category>distributed-availability-group</category>
      <category>high-availability</category>
      <category>multi-cloud</category>
    </item>
    <item>
      <title>Setup AD Controller on Linux</title>
      <link>https://www.404x.io/2024/03/30/setup-AD-controller-on-linux/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/03/30/setup-AD-controller-on-linux/</guid>
      <pubDate>Sat, 30 Mar 2024 15:11:02 GMT</pubDate>
      <description>Setup AD controller with Samba on linux Server: client</description>
      <category>linux</category>
      <category>active-directory</category>
      <category>ldap</category>
      <category>samba</category>
    </item>
    <item>
      <title>SQL Server AG With Docker Without Pacemaker</title>
      <link>https://www.404x.io/2024/03/30/SQL-Server-AG-with-Docker-without-Pacemaker/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/03/30/SQL-Server-AG-with-Docker-without-Pacemaker/</guid>
      <pubDate>Sat, 30 Mar 2024 14:53:02 GMT</pubDate>
      <description>概览 Prepare the Dockerfile with HA feather Build image with Dockerfile just created Create the SQL server nodes with the image which with HA feather Create the certs ,master key and logins on each nodes Sync all certs to each other Create AG group and Endpoint on Primary Node Two Secondary nodes join AG group Create Tes</description>
      <category>high-availability</category>
      <category>sql-server</category>
      <category>docker</category>
      <category>availability-group</category>
    </item>
    <item>
      <title>Linux-System-Performance-Optimization</title>
      <link>https://www.404x.io/2024/03/27/Linux-system-performance-optimization/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/03/27/Linux-system-performance-optimization/</guid>
      <pubDate>Wed, 27 Mar 2024 06:18:09 GMT</pubDate>
      <description>一、影响 Linux 性能的各种因素 1、系统硬件资源 （1）CPU 如何判断多核 CPU 与超线程 消耗 CPU 的业务：动态 web 服务、mail 服务 （2）内存 物理内存与 swap 的取舍 选择 64 位 Linux 操作系统 消耗内存的业务：内存数据库（redis/hbase/mongodb） （3）磁盘 IO</description>
      <category>performance</category>
      <category>troubleshooting</category>
      <category>linux</category>
    </item>
    <item>
      <title>How to Customize Iconfont Icon in Hexo Fluid Theme</title>
      <link>https://www.404x.io/2024/02/07/How-to-customize-iconfont-icon-in-Hexo-fluid-theme/</link>
      <guid isPermaLink="true">https://www.404x.io/2024/02/07/How-to-customize-iconfont-icon-in-Hexo-fluid-theme/</guid>
      <pubDate>Wed, 07 Feb 2024 09:48:51 GMT</pubDate>
      <description>What we do in this article? if you want to change the menu button ( Marked as red below the Picture ) as I did. This article is gonna help you to do that. Use default icon Please check fluid docs https://hexo.fluid-dev.com/docs/icon/ Customize icon Search the icon from https://www.iconfont.cn/ and add to your own Inven</description>
      <category>hexo</category>
      <category>iconfont</category>
      <category>theme</category>
    </item>
    <item>
      <title>CSS-Sql Server Troubleshooting Tools</title>
      <link>https://www.404x.io/2023/12/15/CSS-sql-server-Performance-Troubleshooting/</link>
      <guid isPermaLink="true">https://www.404x.io/2023/12/15/CSS-sql-server-Performance-Troubleshooting/</guid>
      <pubDate>Fri, 15 Dec 2023 08:19:58 GMT</pubDate>
      <description>Connection https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/resolve-connectivity-errors-overview https://github.com/microsoft/CSS_SQL_Networking_Tools/wiki/0000-Troubleshooting-Workflows Performance Pssdiag &amp;amp; Sqldiag manager This is data collection tool for performance issues. It collects </description>
      <category>sql-server</category>
      <category>performance</category>
      <category>troubleshooting</category>
      <category>connectivity</category>
    </item>
    <item>
      <title>Public Network Access LAN Network Setup Tutorial</title>
      <link>https://www.404x.io/2023/11/11/Public-network-access-LAN-network-setup-Tutorial/</link>
      <guid isPermaLink="true">https://www.404x.io/2023/11/11/Public-network-access-LAN-network-setup-Tutorial/</guid>
      <pubDate>Sat, 11 Nov 2023 11:52:05 GMT</pubDate>
      <description>Why I write this article ? Because I have some test environment or Applications running on my Home server, the problem is when I leave the LAN net work, everything become unaccessible. That&apos;s a very big problem and here&apos;s a solution to solve this problem. Network topology home.msft.vip------&amp;gt;192.168.3.200 ???? DDNS </description>
      <category>networking</category>
      <category>openwrt</category>
      <category>ddns</category>
      <category>port-forwarding</category>
    </item>
    <item>
      <title>Setup K8s Ha Cluster With Kubeasz</title>
      <link>https://www.404x.io/2023/10/18/setup-k8s-ha-cluster-with-kubeasz/</link>
      <guid isPermaLink="true">https://www.404x.io/2023/10/18/setup-k8s-ha-cluster-with-kubeasz/</guid>
      <pubDate>Wed, 18 Oct 2023 17:18:37 GMT</pubDate>
      <description>Architecture Environment Cluster Role IP Address Component Hostname Master-01 192.168.3.11 kube-apiserver kube-controller-manager kube-scheduler ansible K8snode1 Master-02 192.168.3.12 kube-apiserver kube-controller-manager kube-scheduler K8snode2 Worker-01 192.168.3.13 Kubelet kube-proxy etcd K8snode3 Worker-02 192.16</description>
      <category>high-availability</category>
      <category>kubernetes</category>
      <category>kubeasz</category>
      <category>cluster</category>
    </item>
  </channel>
</rss>
