The devcontainer is working now. (At least on my linux machine).
The .devcontainer contains a docker file named DockerfileUpstream which can be used to build the image ampersandtarski/ampersand-devcontainer:latest. This has been pushed to dockerhub.
How to use this image
When you open the Ampersand repo in vscode, you have the option to re-open it in container:
This will build the container from the image. It contains ghcup and the appropriate versions of ghc, cabal, stack and hls installed. It also contains various plugins, among which the Haskell plugin.
When your environment is loaded, you can trigger the Haskell plugin by opening a .hs file. The first time you do so, it will fast-build the ampersand code. You can observe that in the status bar. It will show a message like processing 1 of 2 or something like that. The first time you use the container, that might take 2 to 3 minutes.
After this is done, the goodies of the Haskell plugin will be available.
The devcontainer is working now. (At least on my linux machine).
The .devcontainer contains a docker file named
DockerfileUpstreamwhich can be used to build the imageampersandtarski/ampersand-devcontainer:latest. This has been pushed to dockerhub.How to use this image
When you open the
Ampersandrepo in vscode, you have the option to re-open it in container:This will build the container from the image. It contains ghcup and the appropriate versions of ghc, cabal, stack and hls installed. It also contains various plugins, among which the Haskell plugin.
When your environment is loaded, you can trigger the Haskell plugin by opening a .hs file. The first time you do so, it will fast-build the ampersand code. You can observe that in the status bar. It will show a message like
processing 1 of 2or something like that. The first time you use the container, that might take 2 to 3 minutes.After this is done, the goodies of the Haskell plugin will be available.
Happy coding!