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

Private modules #11

Open
kpcyrd opened this issue Oct 24, 2018 · 1 comment
Open

Private modules #11

kpcyrd opened this issue Oct 24, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@kpcyrd
Copy link
Owner

kpcyrd commented Oct 24, 2018

While it's possible to drop custom scripts into ~/.local/share/sn0int/modules/ we should explicitly support private modules. This could conflict with the registry and #8 though.

We could improve support by allowing the user to clone a repo into sn0int/modules/foo/. If we discover a git repo at sn0int/modules/foo/.git we would exclude it from a regular update and instead try to fetch+fast-forward the repo.

We could also invoke git clone for the user if we detect an url argument for sn0int install.

@kpcyrd kpcyrd added the enhancement New feature or request label Nov 13, 2018
@kpcyrd
Copy link
Owner Author

kpcyrd commented Nov 21, 2018

With regards to the scripting guide it might be best if we support registering some paths as namespace in the config file. Those are then considered private.

@kpcyrd kpcyrd added this to the v0.6.0 milestone Nov 21, 2018
@kpcyrd kpcyrd modified the milestones: v0.6.0, v0.7.0 Dec 3, 2018
@kpcyrd kpcyrd modified the milestones: v0.7.0, v0.8.0 Dec 24, 2018
@kpcyrd kpcyrd removed this from the v0.8.0 milestone Jan 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant