Skip to content
This repository has been archived by the owner on May 22, 2018. It is now read-only.

Issue with running ./script/boxen #704

Closed
leeyoda opened this issue Jan 6, 2015 · 9 comments
Closed

Issue with running ./script/boxen #704

leeyoda opened this issue Jan 6, 2015 · 9 comments

Comments

@leeyoda
Copy link

leeyoda commented Jan 6, 2015

I am following the steps listed in: https://github.com/boxen/our-boxen

For step: git remote rm origin, I am getting:
error: Could not remove config section 'remote.origin'
I bypassed it by:
git remote set-url origin myOwnRepoUrl
Then I ran: git push -u origin master with --push.

For all git commands, I need to add sudo for it to work.

So the next step will be: go to /opt/boxen/repo and run ./script/boxen.
I got:
--> Preparing to auto-update...
--> Complete! Nothing new from upstream.
mkdir: bin: Permission denied
Can't bootstrap, dependencies are outdated.

Then I tried sudo as usual and typed in my password, then I got this from boxen:
Run this as a normal user, I'll sudo if I need to.

So I am in a weird state right now.
PS: And I am using Github(enterprise) for this and I am wondering what it means by:
"If you're making a repository on GitHub, you may not want to fork this repo to get started. The reason for that is that you can't really make private forks of public repositories easily."

Doest this mean that I need to use bitbucket or whatever? If I need to use GitHub, what do i need to do to make it work? The instruction isn't quite friendly throughout my experience.
Please help.

Any input will be appreciated.

@wfarr
Copy link
Contributor

wfarr commented Jan 6, 2015

It appears you have a permissions problem inside /opt/boxen.

Please run:

sudo chown -R <your login>:admin /opt/boxen

Then attempt to run script/boxen again. Please note you should never run script/boxen with sudo -- boxen will escalate to root privileges and prompt you for your password when it needs to do so.

@leeyoda
Copy link
Author

leeyoda commented Jan 6, 2015

Hey @wfarr , it works now after your proposed command.
Now I got stuck on the authentication part. My repo is in our company github repo and I tried to authenticate myself using the email and password. It won't allow me to input the email.
And the user name or password didn't work either.
Anything on top your head that I need to be doing?
Really appreciate your quick response.

@wfarr
Copy link
Contributor

wfarr commented Jan 6, 2015

Just to confirm, have you been following the directions on using boxen with GitHub: Enterprise?

https://github.com/boxen/our-boxen#integrating-with-github-enterprise

@leeyoda
Copy link
Author

leeyoda commented Jan 6, 2015

@wfarr , now I am embarrassed. I didn't notice it since it is like the bottom line. I sincerely apologize since I hate people who don't read instructions.
Proposal to reduce the chance that other people run into this (Hope it is only me):
For the Bootstrapping part, we can add a link or note that points to GitHub Enterprise users so that the extra step can be found there.
Thanks for your time.
I will try adding those variables now and keep you posted before this ticket is closed.

@leeyoda
Copy link
Author

leeyoda commented Jan 6, 2015

After adding those, it goes a little further.
-> Preparing to auto-update...
--> Complete! Nothing new from upstream.
GitHub login: |mli| mli
GitHub password: **********
Password for sudo:
Fact file /opt/boxen/repo/facts.d/example.yaml was parsed but returned an empty data set
Error: Please enable full disk encryption and try again at /opt/boxen/repo/manifests/site.pp:63 on node mlimac1.roving.com
Error: Please enable full disk encryption and try again at /opt/boxen/repo/manifests/site.pp:63 on node mlimac1.roving.com

I tried to add --no-fde specified in the "Distributing" part. Not sure it is the right thing to do, but it seems to creating a bunch of stuff now.
Is this "./script/boxen --no-fde" the right thing to do in the "Bootstrapping" step?

@wfarr
Copy link
Contributor

wfarr commented Jan 6, 2015

If you do not want to check for FDE, using --no-fde is the right way to go. That said, we strongly recommend FDE.

@leeyoda
Copy link
Author

leeyoda commented Jan 6, 2015

I am new to the company, I need to check with my manager whether it is something that should be done. He wants me to try to set up my Mac using Boxen so that it can benefit future hires.

The installing has been running for a while.
It stays at:
Notice: /Stage[main]/Hub/Package[hub]/ensure: created
Notice: /Stage[main]/Boxen::Bin/File[/opt/boxen/bin/boxen]/ensure: created

Does this mean it is finish installing the default configuration? It is been like this for 20 minutes.
Should I ctrl + c to exit it?

@wfarr
Copy link
Contributor

wfarr commented Jan 6, 2015

I am new to the company, I need to check with my manager whether it is something that should be done. He wants me to try to set up my Mac using Boxen so that it can benefit future hires.

FDE, or Full Disk Encryption, is a net positive in security in the case of physical compromise of the machine, or someone getting hold of the disk.

Does this mean it is finish installing the default configuration?

It'll let you know when it's done. Progress is printed after each step completes due to some limitations of the underlying software. If you exit the program you can re-run it again later. If you're curious what it's doing that's taking so long now, check out pstree on the boxen process. Most likely it's compilation of a ruby version or a homebrew package.

@leeyoda
Copy link
Author

leeyoda commented Jan 6, 2015

I will definitely try to push for FDE tomorrow in the standup meeting in the team. Extra layer of security definitely helps.
And appreciate your second tip. I need to be more patient I guess.
Thanks a lot for being patient with rookies like me. It can be a little intimidating sometimes when there is very little help from the community.

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

No branches or pull requests

2 participants