Skip to content
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

feat: Add linux support, github publisher and release workflow #9

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

sogladev
Copy link

Changes

Windows:

  • No changes

Linux:

  • feat: add support for Linux platform
    • Removed the need for workarounds for epoch-installer.exe; now installable via native .deb or .rpm.
    • AppImage and Flatpak are currently not supported. See note below
    • Launch button uses wine prefix in the game client directory by default, with a configurable WINEPREFIX.

Developer-Focused Changes:

  • feat: Add GitHub publisher, release workflow, and updated devDependencies.
    • New workflow builds and uploads assets as a draft release.
    • Introduce GitHub publisher per Electron Forge docs.
    • Small compatibility for new devDependencies to plugin format and asset paths.

Flatpak & AppImage:

Tests

I used the workflow to create binaries and tested those:
GitHub Actions Page
Release Page

* use builtin `path` for cross platform paths, launch client with wine

* set startup command to use env WINEPREFIX

* setup maker RPM and DEB configuration

* 1.1.0

npm version 1.1.0

* add support for custom linux startup commands

example: env LUTRIS_SKIP_INIT=1 lutris lutris:rungameid/1
* Add a workflow that builds and uploads assets as draft

* update "plugins" to new format

* update devDependencies

* add appimage maker

* fix image paths

* drop appimage maker

settings aren't persisted; not usable as a launcher if user needs to set
the game directory on every launch

* fix: use npm ci

uses existing package-lock.json rather than install's latest compatible

* drop custom startup command

too many problems trying to use a custom command, existing functionality
is sufficient
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant