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

CN server: use local switches for installation instructions and in CI #132

Merged
merged 7 commits into from
Dec 17, 2024

Conversation

samcowger
Copy link
Contributor

Using switches makes the process a bit less fiddly and error-prone, and should obviate some of the stale dependency issues the previous process entailed.

@samcowger samcowger force-pushed the sc/opam-switch-instructions branch 5 times, most recently from 0540108 to 02ab1ff Compare November 12, 2024 19:58
@samcowger samcowger marked this pull request as ready for review November 12, 2024 20:01
@samcowger samcowger force-pushed the sc/opam-switch-instructions branch from 02ab1ff to a9b4f75 Compare November 12, 2024 20:07
@samcowger samcowger force-pushed the sc/opam-switch-instructions branch from a9b4f75 to febc36d Compare November 12, 2024 21:38
@samcowger samcowger changed the title CN server: use opam switches for installation instructions and in CI CN server: use local switches for installation instructions and in CI Nov 12, 2024
@samcowger
Copy link
Contributor Author

Aha - local switches also fall prey to the problem of Cerberus's runtime file dependency that I mentioned in #130 (comment). Although these instructions ought to work well for building a server in isolation, they'd also need to tell users how/where to install those runtime files and how to point the server at them - unless we end up taking one of the other paths I mentioned in that comment.

@samcowger
Copy link
Contributor Author

Aha - local switches also fall prey to the problem of Cerberus's runtime file dependency that I mentioned in #130 (comment). Although these instructions ought to work well for building a server in isolation, they'd also need to tell users how/where to install those runtime files and how to point the server at them - unless we end up taking one of the other paths I mentioned in that comment.

I've gotten around this for now by having a user point the client at the specific opam switch into which they've installed the server, since that switch will also contain the Cerberus runtime. Since this amounts to pointing the client at the right binary and runtime files, it should be possible to use a similar approach for binary distributions in the future.

@samcowger samcowger force-pushed the sc/opam-switch-instructions branch from c79f56a to 7846f8f Compare November 15, 2024 17:45
@samcowger samcowger force-pushed the sc/opam-switch-instructions branch from 51e2a1a to f14bfba Compare December 17, 2024 18:47
@samcowger samcowger merged commit 57e73d9 into main Dec 17, 2024
2 checks passed
@samcowger samcowger deleted the sc/opam-switch-instructions branch December 17, 2024 19:44
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