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

have a way to deploy/install all or one src/package #4

Closed
aherreraGH opened this issue Oct 3, 2018 · 2 comments
Closed

have a way to deploy/install all or one src/package #4

aherreraGH opened this issue Oct 3, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@aherreraGH
Copy link

Just a feature request... to have some REST API to submit a JSON object to, and have the information inside that to download from a repo with ssh keys or token - if needed. Or be able to upload a *.gz file containing the entire repo and OS.js uploads/downloads it to its staging directory, extracts the contents and goes through the motions of npm install or npm package:install

@andersevenrud
Copy link
Member

In the case of installable packages via the client, this is actually not the correct repository.

Running npm commands and the likes via HTTP APIs etc. might be a bit ugly because these are intended for deployment and not services in general.

This could be solved by having a separate registry for packages intalled via the client. The Package Manager stuff supports multiple sources, so this should be pretty trivial. This is actually on the TODO list, and I had it somewhat working on v2, so I'd like to have this again.


However, this is a task for the CLI as well, becaise having a package:install command that could detect the following and install into a defined area (src/packages by default) would be nice:

  • Git repo (url or ssh ending in .git$)
  • Compressed archive (path)
  • Directory (path)
  • npm package (string)
  • URL (^(https?|ftp):)

@andersevenrud andersevenrud added the enhancement New feature or request label Oct 3, 2018
@andersevenrud andersevenrud self-assigned this Nov 1, 2018
@andersevenrud
Copy link
Member

As of now you can use git, npm, archives or whatever method preferred in the deployment-side of things (i.e. CLI) because you can just use your own utilities and use an arbitrary path for package discovery.

When it comes to doing this from the client and such, this issue will be used for that: os-js/osjs-client#21

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

2 participants