-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
- Loading branch information
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
|
||
##### 操作步骤 | ||
1.创建并进入一个新目录 | ||
mkdir vuepress-starter && cd vuepress-starter | ||
2.初始化项目 | ||
yarn init # npm init | ||
3.安装[vuepress2.x](https://www.vuepress.cn) 依赖包 | ||
yarn add -D vuepress # npm install vuepress@next -D | ||
4.新建一个READ.ME | ||
mkdir docs && echo '# Hello VuePress' > docs/README.md | ||
5.在 package.json 中添加一些 scripts | ||
{ | ||
scripts: { | ||
docs:dev: vuepress dev docs, //开发环境使用 | ||
docs:build: vuepress build docs // 正式环境使用 | ||
} | ||
} | ||
6.开发环境运行 | ||
yarn docs:dev # npm run docs:dev | ||
|
||
VuePress 会在 http://localhost:8080 (opens new window) 启动一个热重载的开发服务器 | ||
7.正式环境 | ||
yarn docs:build # npm run docs:build | ||
|
||
这会在docs/.vuepress/dist生成 dist打包文件,这个dist文件我部署在:pages.github | ||
|
||
这个是最终的效果:[指尖上的记忆](https://gspgsp.github.io/) |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
import{_ as s,c as a,h as e,o as i}from"./app-BkdxZrhi.js";const l={};function p(d,n){return i(),a("div",null,n[0]||(n[0]=[e(`<p>AppImage和Deb包的区别:</p><div class="language-text line-numbers-mode" data-highlighter="prismjs" data-ext="text" data-title="text"><pre><code><span class="line">AppImage 是一种通用的软件打包格式,它可以在大多数 Linux 发行版上直接运行而无需安装。这种格式允许开发者将整个应用程序及其所有依赖项打包到单个文件中,使应用程序更易于分发和使用。</span> | ||
<span class="line"> </span> | ||
<span class="line">使用 AppImage 具有以下一些优点:</span> | ||
<span class="line"> </span> | ||
<span class="line">无需安装 - 只需下载 AppImage 文件,标记为可执行,然后直接运行它。</span> | ||
<span class="line">无依赖地狱 - AppImage 中已经包含了应用程序所需的所有依赖库,避免了传统软件包之间相互依赖的问题。</span> | ||
<span class="line">与发行版无关 - 理论上,AppImage 可以在所有 Linux 发行版上运行,而无需针对特定版本进行打包或编译。</span> | ||
<span class="line">沙箱化 - AppImage 在沙箱环境中运行,避免与系统其他部分产生冲突。</span> | ||
<span class="line">易于删除 - 只需删除 AppImage 文件即可完全卸载应用程序。</span> | ||
<span class="line">在 Ubuntu 上使用 AppImage 非常简单,请按照以下步骤操作:</span> | ||
<span class="line"> </span> | ||
<span class="line">下载所需的 AppImage 文件。</span> | ||
<span class="line">在终端中导航到下载目录。</span> | ||
<span class="line">使用 chmod a+x 命令赋予 AppImage 文件可执行权限。例如: chmod a+x ApplicationName.AppImage</span> | ||
<span class="line">运行该文件,例如: ./ApplicationName.AppImage</span> | ||
<span class="line">就是这样,应用程序就会启动了!很多开源软件和一些商业软件现在都提供了 AppImage 格式的下载。它为 Linux 用户提供了一种额外的灵活安装选择。</span> | ||
<span class="line"></span> | ||
<span class="line">Debian软件包(deb格式)是Ubuntu等基于Debian的Linux发行版使用的传统软件包格式。deb格式和AppImage有一些显著区别:</span> | ||
<span class="line"> </span> | ||
<span class="line">deb软件包:</span> | ||
<span class="line">需要通过包管理器(如apt)安装,会将文件解包并部署到系统相应的位置。</span> | ||
<span class="line">会自动处理依赖关系,从软件仓库下载所需的依赖库。</span> | ||
<span class="line">与系统的软件包管理深度集成,可以方便地升级、卸载。</span> | ||
<span class="line">被安装到系统后,多个程序可共享同一个库文件。</span> | ||
<span class="line">安装时可能会修改系统配置(如修改环境变量等)。</span> | ||
<span class="line">特定于不同的Linux发行版和架构。</span> | ||
<span class="line">相比之下,AppImage:</span> | ||
<span class="line"> </span> | ||
<span class="line">是单个可执行文件,不需安装过程。</span> | ||
<span class="line">所有依赖已打包在内,不依赖系统库。</span> | ||
<span class="line">与系统基本隔离,不会影响其它程序,更新时完全覆盖。</span> | ||
<span class="line">可以在不同Linux发行版和架构间移植使用。</span> | ||
<span class="line">方便分发和备份,只需复制AppImage文件。</span> | ||
<span class="line">总的来说,deb更适合常规需要深度系统集成的应用程序,而AppImage则更加灵活、无缝,尤其适合在不同环境间使用、测试或临时运行某些程序。两者在使用场景和设计理念上有所不同,兼有利弊,开发者或用户可根据实际需求选择使用。</span> | ||
<span class="line"></span></code></pre><div class="line-numbers" aria-hidden="true" style="counter-reset:line-number 0;"><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div><div class="line-number"></div></div></div>`,2)]))}const m=s(l,[["render",p],["__file","AppImage和Deb包的区别.html.vue"]]),v=JSON.parse('{"path":"/content/other/spread/AppImage%E5%92%8CDeb%E5%8C%85%E7%9A%84%E5%8C%BA%E5%88%AB.html","title":"AppImage和Deb包的区别","lang":"en-US","frontmatter":{"sidebar":false,"title":"AppImage和Deb包的区别","description":"AppImage和Deb包的区别"},"headers":[],"git":{},"filePathRelative":"content/other/spread/AppImage和Deb包的区别.md"}');export{m as comp,v as data}; |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.