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

Add service for glances #23266

Closed
wants to merge 5 commits into from

Conversation

matthiasbeyer
Copy link
Contributor

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
    • Linux
  • 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.

I rudimentarily tested the service on my local device.

The username and password do not work as expected, will shortly push a commit to disable these options.

@mention-bot
Copy link

@matthiasbeyer, thanks for your PR! By analyzing the history of the files in this pull request, we identified @edolstra, @bjornfor and @offlinehacker to be potential reviewers.

@lsix
Copy link
Member

lsix commented Mar 2, 2017

Hi,

The service has options to enable or disable many capabilities of glances. However, some of them only makes sense if glances has the proper support, and this is not always true since it has many optional dependencies. For instance, python*Packages.glances's propagatedBuildInputs argument do not have python*Packages.docker, but the disable-docker option make it look that it could be enabled by default.

Maybe the options should be limited to the ones that only change something?

@matthiasbeyer
Copy link
Contributor Author

@lsix thanks for pointing this out. I will continue to work on this, so that if a certain switch is enabled, the appropriate dependencies of glances are built into the package.


So, this is WIP, don't merge please! 🛩️

@matthiasbeyer
Copy link
Contributor Author

The commits I just pushed are not tested, but I ask for review here, whether this approach is a good idea or not...

@FRidh
Copy link
Member

FRidh commented Apr 30, 2017

I don't know much about glances, but if you think it makes sense to have a service, go ahead, implement it and maintain it. Just don't get too ambitious with all the options.

Also think about whether it makes sense or not to add optional dependencies to the propagatedBuildInputs of the glances application. Perhaps it makes more sense to add an environment where glances has access to those optional dependencies?

@FRidh
Copy link
Member

FRidh commented May 16, 2017

Status update?

@matthiasbeyer
Copy link
Contributor Author

No time atm, but I will rebase to fix merge issues, so others can pick it up easily. Will continue as soon as I have enough free time.

These two flags do not work as expected. I would expect to be able to
pass a parameter to them like so:

    glances --username user --password kittensAreCute

but they do not take any parameters. Therefor, disable them.
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

4 participants