-
Notifications
You must be signed in to change notification settings - Fork 11
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
Beginner friendly Readme tutorial :) #34
Comments
Thanks for the kind words! It is odd, because the error is that the HTTP library you're using does not have SSL/TLS support, which is necessary to talk to the Slack API. The OPAM file mentions this, so installing the package should install either the How did you install |
Found solution for the |
Yes, but it should not be necessary because |
Hmm, I realized this however I keep running into errors while building a transitive dependency mirleft/ocaml-tls#385 |
It looks like you're running |
Mmm, actually I am trying out a server ( for the first time ! ) and I the only way I have access to it is I don't quite know how to create user and run ocaml as a user, could you please point me in the right direction ? |
I don't know which operating system your server uses, here's the instructions for Debian GNU/Linux. |
Thanks :)
I'm using something very close, Ubuntu. However I do think that perhaps the
cpuid package isn't able to identify the cpu architecture I'm running on
which is ARMv7 architecture from scaleway bare metal cloud.
You think it's possible to add this to the package?
…On Sun, 7 Oct 2018, 21:18 Marek Kubica, ***@***.***> wrote:
I don't know which operating system your server uses, here's the
instructions for Debian GNU/Linux
<https://www.debian.org/doc/manuals/debian-handbook/sect.creating-accounts.en.html>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMNNXpleA21SkfkUdq1ENyCxJNtqagpnks5uiiItgaJpZM4XL3Si>
.
|
Well it can all be done if you know what you're doing, but the problem is that you'll need to install OPAM 2 and I am not sure there are prebuilt packages for OPAM 2 for ARMv7. Therefore I would suggest you start with a simpler platform first. |
Yup there is - It's works fine on the scaleway ARMv7 bare metal instances!
it's running utop, mirage etc perfectly fine. Still it really bothers me
that the cpuid package is not buildable here. In the meantime, I'd use this
on my linux workstation :)
Anyways, apart from that, I do think that the Readme should atleast have
sample examples like "create message" etc or have you blogged about it ?
…On Mon, Oct 8, 2018 at 11:50 AM Marek Kubica ***@***.***> wrote:
Well it can all be done if you know what you're doing, but the problem is
that you'll need to install OPAM 2 and I am not sure there are prebuilt
packages for OPAM 2 for ARMv7. Therefore I would suggest you start with a
simpler platform first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMNNXqSMGKCCHS50fZV4N3oP4eDNUu0nks5uiu60gaJpZM4XL3Si>
.
|
I think posting a message is quite self-explanatory. If you look in the documentation you'll find slacko/src/cli/slack_notify.ml Line 73 in 5c2ac37
|
(It seems like the API docs are out of date for some reason, looks like I'll have to look into it) |
Hi @Leonidas-from-XIV , have you managed to find time to update the |
Yes, sorry, the docs should be up to date with the current release on OPAM. |
Hello, I tried out Slacko and hit this error. It seems now one needs to install |
Hi @Leonidas-from-XIV
First off, thanks for this wonderful API client in
OCaml
! I am new toOCaml
and I was going through theGitHub
repos to find something I could really learn from and here it is - aslack
client 👍However, being a beginner I'm unable to really start using this in
utop
This is my progress so far
Could you please help me out a little bit here ?
The text was updated successfully, but these errors were encountered: