RabbitLabs/random-bunny

Fork 0

AS a developer, I want to be able to create a binary from the package #101

New issue

Closed

opened 2023-10-20 14:57:37 +01:00 by Vylpes · 2 comments

Vylpes commented

2023-10-20 14:57:37 +01:00

Owner

Epic: #70
Story Points: 8

AS a developer, I want to be able to create a binary from the package
SO THAT a user can run the binary and interact with it as any other program

Acceptance Criteria

AS a developer
GIVEN I want to package the project into a binary
WHEN I run yarn package
THEN the program will package the project into a binary file

AS a user
GIVEN I want to use a pre-built package binary
WHEN I run the binary file in the command line
THEN the output of the package should run

Subtasks

Install pkg
Create package script
Update deployment process to package the project up for me
#153

Notes

This will use Pkg
Need it to also build it into a binary file on building master/develop and rsync it to the server

Epic: #70 Story Points: 8 --- AS a developer, I want to be able to create a binary from the package SO THAT a user can run the binary and interact with it as any other program ## Acceptance Criteria AS a developer GIVEN I want to package the project into a binary WHEN I run `yarn package` THEN the program will package the project into a binary file AS a user GIVEN I want to use a pre-built package binary WHEN I run the binary file in the command line THEN the output of the package should run ## Subtasks - [x] Install pkg - [x] Create package script - [x] Update deployment process to package the project up for me - [x] #153 ## Notes - This will use [Pkg](https://www.npmjs.com/package/pkg) - Need it to also build it into a binary file on building master/develop and rsync it to the server

Vylpes added the

labels 2023-10-20 14:57:44 +01:00

Vylpes added this to the 2.2 milestone 2023-10-20 14:57:57 +01:00

Vylpes referenced this issue

2023-10-20 14:58:07 +01:00

Command Line Interface #70

Vylpes changed title from ~~Generate binary file~~ to AS a developer, I want to be able to create a binary from the package

2023-11-19 14:32:23 +00:00

Vylpes removed the

needs criteria

label 2023-11-19 14:34:58 +00:00

Vylpes removed the

needs estimate

label 2023-12-31 14:19:36 +00:00

Vylpes added this to the 2.2 Sprint 4 project 2024-01-07 15:04:40 +00:00

Vylpes modified the project from 2.2 Sprint 4 to 2.2 Sprint 5

2024-02-18 14:08:54 +00:00

Vylpes self-assigned this 2024-02-19 14:52:56 +00:00

Vylpes added the

blocked

label 2024-02-20 17:45:33 +00:00

Vylpes commented

2024-02-20 17:45:48 +00:00

Author

Owner

Blocked until woodpecker ci change is merged

Vylpes removed the

blocked

label 2024-02-24 14:17:32 +00:00

Vylpes started working 2024-02-26 18:04:01 +00:00

Vylpes referenced this issue

2024-02-26 18:32:56 +00:00

Add binary building #151

Vylpes stopped working 2024-02-26 18:34:13 +00:00

30 minutes 12 seconds

Vylpes referenced this issue from a commit

2024-03-01 19:51:12 +00:00

Add binary building (#151)

VylpesTester commented

2024-03-01 19:59:42 +00:00

Member

> Warning Unable to sign the macOS executable
  Due to the mandatory code signing requirement, before the
  executable is distributed to end users, it must be signed.
  Otherwise, it will be immediately killed by kernel on launch.
  An ad-hoc signature is sufficient.
  To do that, run pkg on a Mac, or transfer the executable to a Mac
  and run "codesign --sign - <executable>", or (if you use Linux)
  install "ldid" utility to PATH and then run pkg again

Maybe see if there's a way around this?

``` > Warning Unable to sign the macOS executable Due to the mandatory code signing requirement, before the executable is distributed to end users, it must be signed. Otherwise, it will be immediately killed by kernel on launch. An ad-hoc signature is sufficient. To do that, run pkg on a Mac, or transfer the executable to a Mac and run "codesign --sign - <executable>", or (if you use Linux) install "ldid" utility to PATH and then run pkg again ``` Maybe see if there's a way around this?