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.

Sign up for GitHub

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

Jump to bottom

Modify go-releaser to create a second binary #1721

Open
jhiemstrawisc opened this issue Nov 11, 2024 · 0 comments · May be fixed by #1755
Open

Modify go-releaser to create a second binary #1721

jhiemstrawisc opened this issue Nov 11, 2024 · 0 comments · May be fixed by #1755
Assignees
@jhiemstrawisc
Labels
enhancement New feature or request lotman
Milestone
v7.12.0

Comments

@jhiemstrawisc
Copy link
Member

As we start working to split the server/client binaries, a good first step is creating a second binary in the first place. In the future we can work on splitting actual compiled code between these two, but for now identical binaries should suffice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhiemstrawisc jhiemstrawisc

Labels
enhancement New feature or request lotman
Projects
None yet
Milestone
v7.12.0
Development

Successfully merging a pull request may close this issue.

Restore lotman through splitting off a second server binary jhiemstrawisc/pelican
1 participant
@jhiemstrawisc