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

Deploy script problems #39

Open
Parth opened this issue May 10, 2018 · 0 comments
Open

Deploy script problems #39

Parth opened this issue May 10, 2018 · 0 comments
Labels
deploy issues related to improving deployments

Comments

@Parth
Copy link
Owner

Parth commented May 10, 2018

The deploy script uses command -v to figure out if a particular dependency manager is present on the system. This perhaps isn't the best way to answer the question: "which dependency manager to use"

This is problematic as apt is the dependency management tool on Ubuntu, and serves a different purpose in macOS.

Short term I think we can just check for apt-get and use that.

Another consideration to make: should we just be hosting this tool on a dependency management system in the first place? So instead of:

  1. Clone
  2. Deploy
  3. Log out log back

it might be something like:

  1. Apt
    2 Exec
@Parth Parth added bug deploy issues related to improving deployments and removed bug labels May 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy issues related to improving deployments
Projects
None yet
Development

No branches or pull requests

1 participant