You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been building a (private) deployer and have ended up re-using a lot of components from ocurrent-deployer. I was wondering if there was any interest (or perhaps even some preliminary work :)) on extracting some of the reusable components into a publishable current_deployer library. In particular, things like https://github.com/ocurrent/ocurrent-deployer/blob/master/src/build.ml ?
@patricoferris did you make any progress on this? Having re-usable components for deployer is a great idea.
Mark has written AWS ones and I'm working on equivalent Azure ones for a personal project.
Unfortunately not far beyond re-implementing most of the build.ml file (I used records instead of first-class modules) and then providing some docker helper functions (including a docker-compose-based CI). But not much beyond what could be extracted here.
One really great feature would be private GitHub repository support, which I think such a deployer library would need. I'll add my voice to that issue if I can find (and if it exists, I think it does)
Yes such an issue exists on both OCaml-CI and now on ocurrent. I had a
rough POC working using tokens last year but I’ve not had time to look at
it since.
On Tue, 7 Feb 2023 at 9:48 am, Patrick Ferris ***@***.***> wrote:
Unfortunately not far beyond re-implementing most of the build.ml file (I
used records instead of first-class modules) and then providing some docker
helper functions (including a docker-compose-based CI). But not much beyond
what could be extracted here.
One really great feature would be private GitHub repository support, which
I think such a deployer library would need. I'll add my voice to that issue
if I can find (and if it exists, I think it does)
—
Reply to this email directly, view it on GitHub
<#141 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJXOITQKGOICY2KVQZIWTWWF5UJANCNFSM6AAAAAAQGWQGXY>
.
You are receiving this because you commented.Message ID:
***@***.***>
Activity
talex5 commentedon Sep 9, 2022
Yes please!
avsm commentedon Sep 15, 2022
Yes please!
tmcgilchrist commentedon Feb 2, 2023
@patricoferris did you make any progress on this? Having re-usable components for deployer is a great idea.
Mark has written AWS ones and I'm working on equivalent Azure ones for a personal project.
patricoferris commentedon Feb 6, 2023
Unfortunately not far beyond re-implementing most of the
build.mlfile (I used records instead of first-class modules) and then providing some docker helper functions (including a docker-compose-based CI). But not much beyond what could be extracted here.One really great feature would be private GitHub repository support, which I think such a deployer library would need. I'll add my voice to that issue if I can find (and if it exists, I think it does)
tmcgilchrist commentedon Feb 6, 2023