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

hpal new <projectname> doesn't work in a closed environment #19

Open
reedog117 opened this issue Oct 4, 2018 · 6 comments
Open

hpal new <projectname> doesn't work in a closed environment #19

reedog117 opened this issue Oct 4, 2018 · 6 comments
Labels

Comments

@reedog117
Copy link

I am attempting to use hpal new <projectname> in a closed environment with no Internet access. When I try to run it, I get the following message:

Couldn't create a new project. It seems you may be offline- ensure you have a connection then try again.

Our repos are proxied through verdaccio so we can still install whatever we need to, but I'm wondering if other external calls are being made.

@wswoodruff
Copy link
Member

@reedog117 That command does require access to the hapipal boilerplate repo https://github.com/hapipal/boilerplate -- it clones the latest version on the pal branch into the given foldername

@devinivy
Copy link
Member

devinivy commented Oct 4, 2018

Exactly! Roughly, the steps look like this,

git clone --depth=1 --origin=pal --branch=pal [email protected]:hapipal/boilerplate.git my-project
cd my-project
git checkout --orphan master # New branch without history
git fetch pal --tags
npm init

@reedog117
Copy link
Author

Is this the only command that calls out to the Internet? i.e. can I clone it manually and copy it in, but still be able to use the other commands?

@devinivy
Copy link
Member

devinivy commented Oct 4, 2018

hpal docs is the only other case—it also calls out to github to download and search API documentation. One thing I would love to have is a cache for hpal docs.

@reedog117
Copy link
Author

Excellent. It would be very nice if the boilerplate and docs were accessible via npm calls as it would be a great help for those developing in closed/restricted environments.

@devinivy
Copy link
Member

devinivy commented Oct 4, 2018

That is a really interesting idea. It would take some planning to imagine exactly how that would work—especially for the documentation, which currently does not travel with the packages in order to keep production installations small. The other tricky thing is flavors, which we implement with git tags and git cherry-picking. But I can definitely imagine a plain installation working by downloading and unpacking an npm tarball into a directory.

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

No branches or pull requests

3 participants