felixse / felixse/FluentTerminal

Deployment enhancements

未關閉
#118 6 則留言 24 個 reaction 已指派 0 人 在 GitHub 檢視
enhancement
主要語言
C#
星號
9.6k
分支
448
PR 合併指標
30 天內沒有已合併 PR

描述

Hi,

I was looking to see if you'd be interested in ways to improve the deployment experience? I have a lot of experience in building/deploying appx's.

A few thoughts:

- You can use AppInstaller and publish built appx/appxbundles to a storage location. That will enable auto-updating without needing to go through the store. Even with a store version, you can have a separate "nightly"/"CI" channel.
- Tools like NerdBank.GitVersioning enable updating the version per-build. This enables continuous deployment to different channels since package version numbers are set.
- A code signing cert will enable use without any manual install or certificate prompts. They are available for about $80/year from some vendors.
- Code signing can be automated in a service, so it's easy to ensure the appxmanifest matches the cert
- The local cert (pfx) that you have for the store is not secret; it's a self-signed cert where the subject happens to match the store id. It is safe to check-in. The store signs the package with a different cert where it has the private key. It would be easier to check that in.
- A tool like Bugsnag, which has an OSS plan, can help catch exceptions you don't see locally.
- Releases, to blob storage/the store, can be all automated using Azure Pipelines release management (for free for OSS projects). It has 10 concurrent builds for free for OSS projects.

I'm happy to discuss any/all of this if you're interested. Here's one example of this all put together:
https://github.com/NuGetPackageExplorer/NuGetPackageExplorer

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。