-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathatom.xml
More file actions
379 lines (379 loc) · 26.9 KB
/
Copy pathatom.xml
File metadata and controls
379 lines (379 loc) · 26.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<generator uri="https://hexo.io/">Hexo</generator>
<icon>https://forgetfulengineer.github.io/img/favicon.svg</icon>
<id>https://forgetfulengineer.github.io/</id>
<link href="https://forgetfulengineer.github.io/" rel="alternate"/>
<link href="https://forgetfulengineer.github.io/atom.xml" rel="self"/>
<rights>All rights reserved 2026, 健忘工程師</rights>
<subtitle>forgetful engineer</subtitle>
<title>健忘工程師</title>
<updated>2026-09-18T05:28:01.000Z</updated>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Backend" scheme="https://forgetfulengineer.github.io/categories/Backend/"/>
<category term="Linux" scheme="https://forgetfulengineer.github.io/categories/Backend/Linux/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="terminal" scheme="https://forgetfulengineer.github.io/tags/terminal/"/>
<category term="linux" scheme="https://forgetfulengineer.github.io/tags/linux/"/>
<category term="system" scheme="https://forgetfulengineer.github.io/tags/system/"/>
<category term="security" scheme="https://forgetfulengineer.github.io/tags/security/"/>
<id>https://forgetfulengineer.github.io/Backend/Linux/file-permissions-owner-management/</id>
<link href="https://forgetfulengineer.github.io/Backend/Linux/file-permissions-owner-management/"/>
<published>2026-09-18T05:28:01.000Z</published>
<summary>1.Owner 決定檔案擁有者的 Permission 2.Group 提供一組 User 共用的 Permission 3.rwx 分別代表 Read、Write、Execute 4.chmod 負責 Permission，chown 負責 Owner／Group，chgrp 專門修改 Group【Linux】</summary>
<title>【Linux】檔案權限與擁有者管理：rwx、chmod、chown</title>
<updated>2026-09-18T05:28:01.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Frontend" scheme="https://forgetfulengineer.github.io/categories/Frontend/"/>
<category term="JavaScript" scheme="https://forgetfulengineer.github.io/categories/Frontend/JavaScript/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="javascript" scheme="https://forgetfulengineer.github.io/tags/javascript/"/>
<category term="js" scheme="https://forgetfulengineer.github.io/tags/js/"/>
<id>https://forgetfulengineer.github.io/Frontend/JavaScript/variable-declarations-const-let-var/</id>
<link href="https://forgetfulengineer.github.io/Frontend/JavaScript/variable-declarations-const-let-var/"/>
<published>2026-09-03T03:18:58.000Z</published>
<summary>1.const、let 採用 Block Scope，var 採用 Function Scope 2.let、const 具有 Temporal Dead Zone (TDZ)；var 則會在 Scope 建立時初始化為 undefined 3.let、const 在同一 Scope 不允許 Redeclaration；var 可以【JavaScript】</summary>
<title>【JavaScript】變數宣告 const、let、var 的差異</title>
<updated>2026-09-03T03:18:58.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="Git" scheme="https://forgetfulengineer.github.io/categories/Other/Git/"/>
<category term="git" scheme="https://forgetfulengineer.github.io/tags/git/"/>
<category term="github" scheme="https://forgetfulengineer.github.io/tags/github/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<category term="ci/cd" scheme="https://forgetfulengineer.github.io/tags/ci-cd/"/>
<id>https://forgetfulengineer.github.io/Other/Git/conventional-commits-commit-message-guide/</id>
<link href="https://forgetfulengineer.github.io/Other/Git/conventional-commits-commit-message-guide/"/>
<published>2026-08-19T02:09:00.000Z</published>
<summary>1.Conventional Commits 讓 Commit 同時具有人類與機器可讀的結構 2.彙整主要 commit type 類型及其適用情境 3.Conventional Commits 能提供 Changelog、Semantic Versioning、Release 與 CI/CD 自動化所需的結構化資訊【Git】</summary>
<title>【Git】使用 Conventional Commits 規範優化 commit message</title>
<updated>2026-08-19T02:09:00.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="GitHub" scheme="https://forgetfulengineer.github.io/categories/Other/GitHub/"/>
<category term="github" scheme="https://forgetfulengineer.github.io/tags/github/"/>
<category term="security" scheme="https://forgetfulengineer.github.io/tags/security/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Other/GitHub/github-branch-ruleset-guide/</id>
<link href="https://forgetfulengineer.github.io/Other/GitHub/github-branch-ruleset-guide/"/>
<published>2026-08-05T01:30:23.000Z</published>
<summary>1.解析 github branch ruleset 設定 2.目標分支與例外權限設定 3.Branch 保護規則 4.Pull Request 審核機制 5.狀態檢查與強推限制 6.程式碼審核與 AI 審核機制【GitHub】</summary>
<title>【GitHub】解析 branch ruleset 設定</title>
<updated>2026-08-05T01:30:23.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Backend" scheme="https://forgetfulengineer.github.io/categories/Backend/"/>
<category term="Nodejs" scheme="https://forgetfulengineer.github.io/categories/Backend/Nodejs/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="javascript" scheme="https://forgetfulengineer.github.io/tags/javascript/"/>
<category term="js" scheme="https://forgetfulengineer.github.io/tags/js/"/>
<category term="nodejs" scheme="https://forgetfulengineer.github.io/tags/nodejs/"/>
<category term="nvm" scheme="https://forgetfulengineer.github.io/tags/nvm/"/>
<id>https://forgetfulengineer.github.io/Backend/Nodejs/use-nvm-to-manage-nodejs-version/</id>
<link href="https://forgetfulengineer.github.io/Backend/Nodejs/use-nvm-to-manage-nodejs-version/"/>
<published>2026-07-20T02:15:14.000Z</published>
<summary>1.透過 nvm 可在系統中切換多種 Node.js 版本，解決全域套件衝突 2.了解 Windows 和 Linux / macOS 安裝 nvm 的流程 3.相比直接安裝，nvm 提供更彈性的環境隔離與版本降級、升級能力 4.建議安裝 nvm 前先移除既有 Node.js，避免檔案或路徑衝突【Node.js】</summary>
<title>【Node.js】使用 nvm 管理 Node.js 版本重點整理</title>
<updated>2026-07-20T02:15:14.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="GitHub" scheme="https://forgetfulengineer.github.io/categories/Other/GitHub/"/>
<category term="git" scheme="https://forgetfulengineer.github.io/tags/git/"/>
<category term="github" scheme="https://forgetfulengineer.github.io/tags/github/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Other/GitHub/github-reference-system/</id>
<link href="https://forgetfulengineer.github.io/Other/GitHub/github-reference-system/"/>
<published>2026-07-02T03:06:59.000Z</published>
<summary>1.Reference System 透過簡單的語法讓內容建立關聯 2.同一個 Repository 內的所有 Issue 和 PR 共用同一組遞增的流水號 3.如何跨儲存庫參照 4.雙向追蹤機制自動建立雙向提交紀錄和通知 5.利用 Closing Keywords 關閉 issue【GitHub】</summary>
<title>【GitHub】解析 Reference System：Issue、Pull Request、Commit 如何建立關聯</title>
<updated>2026-07-02T03:06:59.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Backend" scheme="https://forgetfulengineer.github.io/categories/Backend/"/>
<category term="Develop" scheme="https://forgetfulengineer.github.io/categories/Backend/Develop/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="database" scheme="https://forgetfulengineer.github.io/tags/database/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<category term="search engine" scheme="https://forgetfulengineer.github.io/tags/search-engine/"/>
<category term="ai rag" scheme="https://forgetfulengineer.github.io/tags/ai-rag/"/>
<id>https://forgetfulengineer.github.io/Backend/Develop/search-engine-integration-for-better-performance/</id>
<link href="https://forgetfulengineer.github.io/Backend/Develop/search-engine-integration-for-better-performance/"/>
<published>2026-06-23T07:49:47.000Z</published>
<summary>1.搜尋引擎透過建立倒排索引（Inverted Index）來提升查詢效率 2.一般資料庫擅長資料儲存與交易處理，搜尋引擎則專注於資料檢索 3.搜尋引擎的優勢是全文檢索、模糊搜尋與相關性排序 4.適合導入搜尋引擎的場景有哪些 5.搜尋引擎可作為系統架構中的檢索層，降低資料庫查詢壓力【Develop】</summary>
<title>【Develop】介接搜尋引擎來提升查詢效率！</title>
<updated>2026-06-23T07:49:47.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Backend" scheme="https://forgetfulengineer.github.io/categories/Backend/"/>
<category term="Nodejs" scheme="https://forgetfulengineer.github.io/categories/Backend/Nodejs/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="javascript" scheme="https://forgetfulengineer.github.io/tags/javascript/"/>
<category term="js" scheme="https://forgetfulengineer.github.io/tags/js/"/>
<category term="nodejs" scheme="https://forgetfulengineer.github.io/tags/nodejs/"/>
<category term="cjs" scheme="https://forgetfulengineer.github.io/tags/cjs/"/>
<category term="esm" scheme="https://forgetfulengineer.github.io/tags/esm/"/>
<id>https://forgetfulengineer.github.io/Backend/Nodejs/-cjs-vs-esm-migration-guide/</id>
<link href="https://forgetfulengineer.github.io/Backend/Nodejs/-cjs-vs-esm-migration-guide/"/>
<published>2026-06-02T03:50:24.000Z</published>
<summary>1.解析 CommonJS、ES Modules 模組語法差異 2.CJS 使用 require() 與 module.exports，ESM 使用 import 與 export 3.CJS 採同步載入，ESM 採靜態分析與非同步初始化 4.ESM 天生支援 Tree Shaking，利於效能優化【Node.js】</summary>
<title>【Node.js】解析 CJS 與 ESM 核心差異和專案轉換</title>
<updated>2026-06-02T03:50:24.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="google" scheme="https://forgetfulengineer.github.io/tags/google/"/>
<category term="ai" scheme="https://forgetfulengineer.github.io/tags/ai/"/>
<category term="gemini" scheme="https://forgetfulengineer.github.io/tags/gemini/"/>
<category term="antigravity" scheme="https://forgetfulengineer.github.io/tags/antigravity/"/>
<category term="ide" scheme="https://forgetfulengineer.github.io/tags/ide/"/>
<id>https://forgetfulengineer.github.io/Other/ide-disappeared-after-recovery/</id>
<link href="https://forgetfulengineer.github.io/Other/ide-disappeared-after-recovery/"/>
<published>2026-05-20T06:52:57.000Z</published>
<summary>1.Antigravity 2.0 不再以「AI IDE」為核心，而是改為 autonomous AI agent 平台 2.如何找回原本的 Antigravity IDE 3.如何恢復原本 IDE 設定與 AI 對話紀錄【Antigravity】</summary>
<title>【Antigravity】自動更新後編輯器因此消失，如何恢復原本的編輯器與設定</title>
<updated>2026-05-20T06:52:57.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="GitHub" scheme="https://forgetfulengineer.github.io/categories/Other/GitHub/"/>
<category term="github" scheme="https://forgetfulengineer.github.io/tags/github/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Other/GitHub/github-pages-user-project-page-priority/</id>
<link href="https://forgetfulengineer.github.io/Other/GitHub/github-pages-user-project-page-priority/"/>
<published>2026-05-04T05:46:59.000Z</published>
<summary>1.GitHub Pages 分為 User Page 與 Project Page 兩種類型 2.User Page 與 Project Page 路徑重疊時，優先解析 Project Page 的內容【GitHub】</summary>
<title>【GitHub】User Page 與 Project Page 路徑解析優先級</title>
<updated>2026-05-04T05:46:59.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="Hexo" scheme="https://forgetfulengineer.github.io/categories/Other/Hexo/"/>
<category term="hexo" scheme="https://forgetfulengineer.github.io/tags/hexo/"/>
<category term="seo" scheme="https://forgetfulengineer.github.io/tags/seo/"/>
<category term="icarus" scheme="https://forgetfulengineer.github.io/tags/icarus/"/>
<category term="json-ld" scheme="https://forgetfulengineer.github.io/tags/json-ld/"/>
<category term="structured data" scheme="https://forgetfulengineer.github.io/tags/structured-data/"/>
<id>https://forgetfulengineer.github.io/Other/Hexo/icarus-json-ld-custom-structured-data-seo/</id>
<link href="https://forgetfulengineer.github.io/Other/Hexo/icarus-json-ld-custom-structured-data-seo/"/>
<published>2026-04-20T02:26:55.000Z</published>
<summary>1.覆寫 Icarus 預設 Structured Data，改為自訂元件控制 2.建立 structured_data.jsx，依頁面類型動態產生不同的 JSON-LD，提升 SEO 表現【Hexo】</summary>
<title>【Hexo】自訂 Icarus 主題的 JSON-LD 優化 SEO</title>
<updated>2026-04-20T02:26:55.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="system" scheme="https://forgetfulengineer.github.io/tags/system/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<category term="devops" scheme="https://forgetfulengineer.github.io/tags/devops/"/>
<category term="ci/cd" scheme="https://forgetfulengineer.github.io/tags/ci-cd/"/>
<id>https://forgetfulengineer.github.io/Other/devops-ci-cd-pipeline/</id>
<link href="https://forgetfulengineer.github.io/Other/devops-ci-cd-pipeline/"/>
<published>2026-04-08T03:19:21.000Z</published>
<summary>1.定義 DevOps、CI 與 CD 核心概念 2.解析 CI 與 CD 的差異 3.解析 CI/CD 流水線標準流程及應用場景 4.說明 CI 與 CD 的異常處理 5.說明 DevOps 與 CI/CD 的關係【Develop】</summary>
<title>【Develop】解析 DevOps 與 CI/CD 自動化流程</title>
<updated>2026-04-08T03:19:21.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="system" scheme="https://forgetfulengineer.github.io/tags/system/"/>
<category term="tool" scheme="https://forgetfulengineer.github.io/tags/tool/"/>
<category term="google" scheme="https://forgetfulengineer.github.io/tags/google/"/>
<category term="netlify" scheme="https://forgetfulengineer.github.io/tags/netlify/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Other/analyzing-five-cloud-service-models/</id>
<link href="https://forgetfulengineer.github.io/Other/analyzing-five-cloud-service-models/"/>
<published>2026-03-23T08:21:57.000Z</published>
<summary>1.定義五大雲端服務模型（IaaS、CaaS、PaaS、FaaS、SaaS）的核心架構 2.區分各服務硬體、虛擬化、作業系統、應用程式等層級的管理歸屬 3.各服務模型的代表性產品、管理複雜度及適用場景【Develop】</summary>
<title>【Develop】解析五大雲端服務模型</title>
<updated>2026-03-23T08:21:57.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="Tool" scheme="https://forgetfulengineer.github.io/categories/Other/Tool/"/>
<category term="tool" scheme="https://forgetfulengineer.github.io/tags/tool/"/>
<category term="google" scheme="https://forgetfulengineer.github.io/tags/google/"/>
<category term="ai" scheme="https://forgetfulengineer.github.io/tags/ai/"/>
<category term="gemini" scheme="https://forgetfulengineer.github.io/tags/gemini/"/>
<id>https://forgetfulengineer.github.io/Other/Tool/build-running-pace-app-with-gemini-canvas/</id>
<link href="https://forgetfulengineer.github.io/Other/Tool/build-running-pace-app-with-gemini-canvas/"/>
<published>2026-03-05T02:46:47.000Z</published>
<summary>1.簡潔、無需付費的跑步配速工具 2.自訂配速目標與語音回報 3.即時配速與時間儀表板 4.訓練總結，平均配速分、每公里分段數據表格 5.跑步配速助手使用教學 6.web app 的背景執行限制【Tool】</summary>
<title>【Tool】使用 Gemini Canvas 製作跑步配速 APP</title>
<updated>2026-03-05T02:46:47.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Other/analyzing-url-text-fragments/</id>
<link href="https://forgetfulengineer.github.io/Other/analyzing-url-text-fragments/"/>
<published>2026-02-24T05:31:53.000Z</published>
<summary>1.Text Fragments 允許透過 URL 直接定位並 highlight 網頁中的特定文字，無需依賴 HTML ID 屬性 2.語法結構支援單詞、範圍及上下文定位 3.要求導航必須由使用者觸發（例如點擊連結或在網址列輸入） 4.可透過 ::target-text 客製化反白樣式，不影響 DOM 結構【Html】</summary>
<title>【Develop】解析 URL Text Fragments #:~:text=</title>
<updated>2026-02-24T05:31:53.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="VSCode" scheme="https://forgetfulengineer.github.io/categories/Other/VSCode/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="vscode" scheme="https://forgetfulengineer.github.io/tags/vscode/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Other/VSCode/trim-trailing-whitespace/</id>
<link href="https://forgetfulengineer.github.io/Other/VSCode/trim-trailing-whitespace/"/>
<published>2026-02-03T04:56:37.000Z</published>
<summary>1.VSCode 可以在存檔時自動移除行尾空白（Trim Trailing Whitespace） 2.基礎設定為全域生效 3.settings.json 可進行語言層級的進階控制 4.Render Whitespace 設定可以輔助檢視空白位置【VSCode】</summary>
<title>【VSCode】自動移除行尾空白</title>
<updated>2026-02-03T04:56:37.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="NPM" scheme="https://forgetfulengineer.github.io/categories/Other/NPM/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="terminal" scheme="https://forgetfulengineer.github.io/tags/terminal/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="npm" scheme="https://forgetfulengineer.github.io/tags/npm/"/>
<id>https://forgetfulengineer.github.io/Other/NPM/analyzing-npm-install-update-mechanism/</id>
<link href="https://forgetfulengineer.github.io/Other/NPM/analyzing-npm-install-update-mechanism/"/>
<published>2026-01-21T10:14:15.000Z</published>
<summary>1.npm install 行為機制 2.npm 設定檔的分工設計 3.npm 相依套件的分類 4.語意化版本（SemVer）、符號（^、~）的實際安裝範圍 5.npm update 是一個依版本規則自動前進的更新工具 6.npm 降版本需求使用 npm install，不能使用 npm update【NPM】</summary>
<title>【NPM】解析 npm 安裝和更新的行為</title>
<updated>2026-01-21T10:14:15.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="NPM" scheme="https://forgetfulengineer.github.io/categories/Other/NPM/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="terminal" scheme="https://forgetfulengineer.github.io/tags/terminal/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="npm" scheme="https://forgetfulengineer.github.io/tags/npm/"/>
<id>https://forgetfulengineer.github.io/Other/NPM/common-commands-cheat-sheet/</id>
<link href="https://forgetfulengineer.github.io/Other/NPM/common-commands-cheat-sheet/"/>
<published>2026-01-05T07:16:09.000Z</published>
<summary>1.npm 常用指令速查表及各指令的詳細說明 2.說明 npm 從初始化到安裝到更新到移除等等實用指令 3.npm install 和 npm ci 的差異【NPM】</summary>
<title>【NPM】常用指令速查表</title>
<updated>2026-01-05T07:16:09.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Other" scheme="https://forgetfulengineer.github.io/categories/Other/"/>
<category term="Hexo" scheme="https://forgetfulengineer.github.io/categories/Other/Hexo/"/>
<category term="GitHub" scheme="https://forgetfulengineer.github.io/categories/Other/GitHub/"/>
<category term="frontend" scheme="https://forgetfulengineer.github.io/tags/frontend/"/>
<category term="github" scheme="https://forgetfulengineer.github.io/tags/github/"/>
<category term="hexo" scheme="https://forgetfulengineer.github.io/tags/hexo/"/>
<category term="seo" scheme="https://forgetfulengineer.github.io/tags/seo/"/>
<category term="tool" scheme="https://forgetfulengineer.github.io/tags/tool/"/>
<category term="jsDelivr" scheme="https://forgetfulengineer.github.io/tags/jsDelivr/"/>
<id>https://forgetfulengineer.github.io/Other/GitHub/jsdelivr-cdn-github-pages-hexo-acceleration-tutorial/</id>
<link href="https://forgetfulengineer.github.io/Other/GitHub/jsdelivr-cdn-github-pages-hexo-acceleration-tutorial/"/>
<published>2025-12-21T05:38:55.000Z</published>
<summary>1.jsDelivr 串接 GitHub Pages，延長快取時長、加速載入 2.GitHub Pages 與 jsDelivr 在快取、全球節點、資源更新速度上的差異 3.jsDelivr 串接原理與版本控制 4.Hexo 過濾器實現本地資源重寫 5.自動化佈署腳本與 CDN Tag 機制強制更新快取【GitHub、Hexo】</summary>
<title>【GitHub、Hexo】jsDelivr CDN 加速 GitHub Pages 資源及 Hexo 實作</title>
<updated>2026-03-31T06:38:50.000Z</updated>
</entry>
<entry>
<author>
<name>健忘工程師</name>
<email>thatforgetfulengineer@gmail.com</email>
</author>
<category term="Backend" scheme="https://forgetfulengineer.github.io/categories/Backend/"/>
<category term="backend" scheme="https://forgetfulengineer.github.io/tags/backend/"/>
<category term="system" scheme="https://forgetfulengineer.github.io/tags/system/"/>
<category term="seo" scheme="https://forgetfulengineer.github.io/tags/seo/"/>
<category term="security" scheme="https://forgetfulengineer.github.io/tags/security/"/>
<category term="develop" scheme="https://forgetfulengineer.github.io/tags/develop/"/>
<id>https://forgetfulengineer.github.io/Backend/reverse-proxy-forward-proxy/</id>
<link href="https://forgetfulengineer.github.io/Backend/reverse-proxy-forward-proxy/"/>
<published>2025-12-03T06:30:37.000Z</published>
<summary>1.Reverse Proxy 反向代理是在保護與加速後端伺服器，扮演對外單一入口 2.Forward Proxy 正向代理是用於存取控制與匿名化，扮演用戶端請求的單一出口 3.Reverse Proxy 和 Load Balancer 的關係 4.Forward Proxy 和 VPN 的相似之處【Develop】</summary>
<title>【Develop】解析 Reverse Proxy 與 Forward Proxy</title>
<updated>2025-12-03T06:30:37.000Z</updated>
</entry>
</feed>