用爬蟲作為Dify的知識庫：Firecrawl / Using a Web Crawler as Dify's Knowledge Base: Firecrawl

Dify的知識庫能夠取自網路資料，再搭配我們自架的Coolcrawl來取代公開服務Firecrawl，就能夠抓取內部區域網路裡面的網路資料。接下來就讓我們來看看這要怎麼實作吧。

Dify's knowledge base can draw from online data, and by combining it with our self-hosted Coolcrawl (instead of the public service Firecrawl), it can also crawl data within the intranet. Let's take a look at how to implement this.

離開抱抱臉: 讓Dify擁抱Ollama / Leaving Hugging Face: Embracing Ollama with Dify

在「自行架設大型語言模式應用程式：Dify」這篇我講到我在Dify裡面使用Hugging Face API作文字嵌入(embedding)，但啟動等待跟限速的限制降低了使用效率。這次我們把文字嵌入的工作交給自行架設的Ollama，讓我們來看看自行架設到底可以帶來什麼效益吧。

In the article "Self-Hosting a Large Language Model Application: Dify," I discussed using the Hugging Face API for text embedding within Dify. However, startup latency and rate limiting reduced efficiency. This time, we'll offload the text embedding task to a self-hosted Ollama instance. Let's explore the benefits of self-hosting.

雜談：來自架Dify v0.12.1吧！ / TALK: Let's Self-Host Dify v0.12.1!

自從上次講到想要從Dify v0.6.14升級之後，這次就來試著安裝看看吧。

雜談：是時候該來處理一下Dify的問題了 / TALK: It's Time to Address the Issues with Dify

在「自行架設大型語言模式應用程式：Dify」這篇裡面，我用Dify在筆電架設了可客製化、具備RAG的大型語言模型應用程式。但這段期間用下來還是遭遇了很多問題。以下就稍微列舉一下我遭遇的狀況。

自行架設大型語言模式應用程式：Dify / Self-Hosting a Large Language Model Application: Dify

Coze開始收費之後，Dify會是更好的替代方案嗎？事情原來沒有我自己想象中的這麼簡單！

When Coze began to charge fees, what is the next solution for Large Language Model (LLM) application? Will Dify be a better alternative? The actual situation is not as simple as I had imagined!