chore: migrate to AppImage and publish with electron-builder on Travis #1010
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#1010
Loading…
Reference in a new issue
No description provided.
Delete branch "issue/332"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This closes #332 and closes #966.
@JoshStrobl apologies if this is a redundant question (I have this feeling I've asked this), but for your purposes does this switch to AppImage: a) help, b) hurt, or c) doesn't matter?
@kauffj It doesn't affect packaging in my case. ("Doesn't matter.")
@IGassmann per our convo, let's make sure the daemon is signed: https://github.com/lbryio/lbry/issues/811
Now that this has been merged, where did the AppImage go?
@seanyesmunt do you know what happened to AppImage builds or what it would take to re-enable these?
We only temporarily tested with these and decided not to go with them at the time because it required setting the executable properties manually before installing.
With syncing enabled now, I think it will be a good time to check out appimage and snaps.
If you would like to test, here is an example AppImage I've made to be able tor run LBRY until an official AppImage becomes available:
https://github.com/probonopd/LBRY.AppImage/releases/tag/continuous
Before you can run an AppImage, you need to make it executable. This is a Linux security feature. There are three main ways to make an AppImage executable:
1. With the GUI
2. On the command line
3. Automatically with the optional appimaged daemon
If you would like to have all AppImages be executable automatically, you can install the optional
appimaged
daemon. It will automatically add downloaded AppImages to the menu and make them executable for you. It can be downloaded from https://github.com/AppImage/AppImageKit/releases or installed from your distribution.You can see the
.travis.yml
I used to make the AppImage here:https://github.com/probonopd/LBRY.AppImage/blob/master/.travis.yml
If you haven't seen it, also check out this: