build: added a nix flake #197
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
teto
force-pushed
the
flake
branch
2 times, most recently
from
467de02
to
ebca791
Compare
run with nix develop we need nixpkgs to export some variables to help luarocks
assume "coffee" to be in PATH
it's cleaner, avoid conflicts etc
wip adding an input.csv to regenerate nix code from added README fixed lapis build ! nix build .#lapis works and put it in the devShell so one can straight run "lapis server" ok wip we need to use a lua5.1 env since openresty relies on luajit, else you get missing symbol errors. copying nginx.conf to service mount luarocks-site folder for its config in the VM. But needs to add lapis.coroutine to luaEnv more dependencies
it's not portable. It's best to assume luajit already in PATH
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to help the community contribute to luarocks.org (with a few issues in mind see nvim-neorocks/luarocks-tag-release#73) . As it stands, testing changes seems like an obstacle:
which is why I would like to submit a nix package. nix is a package manager that focuses on reproducibility, basically what works on my machine works on yours. Many technologies promise this but nix delivers.
Here is my attempt at it (in my constrained time so anyone feel free to pick up).