<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Laravel on 知识铺的博客</title>
    <link>https://index.zshipu.com/geek/tags/Laravel/</link>
    <description>Recent content in Laravel on 知识铺的博客</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>zh-CN</language>
    <lastBuildDate>Wed, 19 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://index.zshipu.com/geek/tags/Laravel/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Laravel授权五大难题及2026年解法</title>
      <link>https://index.zshipu.com/geek/post/20260819/Laravel%E6%8E%88%E6%9D%83%E4%BA%94%E5%A4%A7%E9%9A%BE%E9%A2%98%E5%8F%8A2026%E5%B9%B4%E8%A7%A3%E6%B3%95/</link>
      <pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://index.zshipu.com/geek/post/20260819/Laravel%E6%8E%88%E6%9D%83%E4%BA%94%E5%A4%A7%E9%9A%BE%E9%A2%98%E5%8F%8A2026%E5%B9%B4%E8%A7%A3%E6%B3%95/</guid>
      <description>Laravel授权五大难题及2026年解法 随着应用规模扩大，Laravel开发者常会遇到授权相关的棘手问题。本文基于一篇技术文章，梳理了五个典型痛点及对应的解决思路，并介绍了一个集成方案。 角色爆炸：当角色数量失控 许多应用最初只定义几个角色，但随着业务复杂化，角色数量迅速膨胀，权限</description>
    </item>
  </channel>
</rss>
