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

dillinger: init at 2017-10-08 with module and minimal test #32275

Closed
wants to merge 3 commits into from

Conversation

WilliButz
Copy link
Member

@WilliButz WilliButz commented Dec 3, 2017

Motivation for this change

Adds the markdown editor web-app dillinger

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@WilliButz
Copy link
Member Author

/cc @cillianderoiste :)

Copy link
Member

@Ma27 Ma27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Building the package and running the test works fine on my machine :)

port = mkOption {
type = types.int;
default = 8080;
example = 2342;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think a description and a default is sufficient in this case to understand what the port option is supposed to be :)


user = mkOption {
type = types.nullOr types.str;
default = "nobody";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how about adding a dillinger user (most of such services use a custom user)

Copy link
Member

@matthewbauer matthewbauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge conflict

@WilliButz
Copy link
Member Author

@matthewbauer I just rebased this on the current master but dillinger is based on nodejs-4_x which has already been deprecated. I built this with nodejs-6_x and it still seems to run fine.
I'm not sure if I should either use node 6 or close the PR for now and hope that some day dillinger will use nodejs 6 by default.

@Ma27
Copy link
Member

Ma27 commented Apr 22, 2018

I think that as the README stated that Node v4+ should be fine (see https://github.com/joemccann/dillinger/tree/9581db83096a29948c7059bb421fd27e23f4f7f8#installation)

@WilliButz besides the test have you confirmed the basic functionality of the software? (in this case it should be fine, between NodeJS 4 and 6 aren't too much breaking changes that could cause an issue for us)

As this seems to be a NodeSource powered product (which uses NSolid, see https://nodesource.com/products/nsolid and I don't know anything about this ecosystem except what I just read) I'm not sure how easy it is to perform platform bumps or maintain compatibility among several platforms...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants