-
Notifications
You must be signed in to change notification settings - Fork 490
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instructions for creating a flatpack #1760
base: v2
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for tauri-v2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
First of all, big thanks!
No idea what that section would entail tbh
i thought that's what we were talking about, mb. But yeah, that's what most flatpak consumers will actually use so we for sure need it. It also doesn't really build on top of the standalone flatpak approach though so that will be a bit harder. That said, no need to add it in this PR, we can work on that in another one.
Remove the distribute.mdx file, create a new distribute folder and move the flatpak guide into that. It'll also need an index file like this one https://github.com/robertosw/tauri-docs/blob/flatpak-docs/src/content/docs/guides/debug/index.mdx - at least i assume that's the approach we wanna take for now, maybe Lorenzo will
Try changing |
This did the trick 👍🏼 The "distribute" page is now in its own folder as a |
I found this guide on how to submit your flatpak to the Flathub repo. I linked this at the end of this flatpak page, because I think this already explains everything. |
The guide isn't really clear imo. The first part kinda sounds like you could upload the generated .flatpak bundle (which your docs here create) which is not the case. This is only the testing phase. For uploading the app to flathub you only upload the manifest and build at least the flatpak bundle but preferebly the app itself too in their CI. Especially with Rust apps this is not exactly straight forward (also closed source vs open source apps) which this guide doesn't touch at all.
True true, but as said above we need an explicit flathub guide anyway. But yeah, we could move this part into the building sections to .deb and .appimage and only have the seperate flathub guide in distribute. |
Okay, fair enough 👍 |
What kind of changes does this PR include?
Description
Open Questions
How do I add this page to the navbar?Why is the "On this page" not showing the headers?