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

Keter not building under fresh Ubuntu 18.04 LTS #200

Open
jamiepauson opened this issue Jan 3, 2020 · 3 comments
Open

Keter not building under fresh Ubuntu 18.04 LTS #200

jamiepauson opened this issue Jan 3, 2020 · 3 comments

Comments

@jamiepauson
Copy link

Following instructions on https://github.com/snoyberg/keter/blob/master/README.md.

The "cabal install keter" command fails with:

Keter/Main.hs:41:53: error:
Module
'Network.HTTP.Conduit'
does not export
'conduitManagerSettings'

@lucch
Copy link
Collaborator

lucch commented Apr 29, 2020

You probably want to build Keter using stack instead of cabal. Stack will download and use the appropriate versions of package dependencies and the GHC compiler.

  1. Install stack (https://docs.haskellstack.org/en/stable/README/#how-to-install).
  2. Clone this repository (eg: git clone https://github.com/snoyberg/keter.git).
  3. Move into the cloned directory and run stack build.
  4. Copy the generated keter binary to the appropriate location (eg: /opt/keter/bin).

This should work! 🙂

However, as per the documentation, note that:

For a production system, we recommend building the keter binary on a separate system, and tracking it via a package manager or similar strategy.

I use to build Keter on my local machine using Docker and then deploy the compiled binary to the server simply using scp. Stack also facilitates that because of its Docker integration.

@mmzx
Copy link
Collaborator

mmzx commented Apr 29, 2020

Great to see bigger traffic here eventually. I can confirm cabal new-build with ghc-8.6 would work. In case you use stack for building, choose the lts version wisely.

@lucch
Copy link
Collaborator

lucch commented Apr 29, 2020

I default to using whatever LTS comes in stack.yaml. Just built keter/1.4.3.2 using its kinda outdated resolver and deployed to a new CentOS server I've got. At least for my current needs, it's doing the job.

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

No branches or pull requests

3 participants