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

Simplify BeagleBone setup and code deployment using Ansible. #458

Open
AhmedSamara opened this issue Feb 10, 2016 · 3 comments
Open

Simplify BeagleBone setup and code deployment using Ansible. #458

AhmedSamara opened this issue Feb 10, 2016 · 3 comments

Comments

@AhmedSamara
Copy link
Member

Introduction

Currently writing and runnning code on the BeagleBone involves one of two different methods:

  • Writing code locally and using rsync to bring it over (good but occasionally tedious without aliases and scritps)
  • Writing code directly on Bone (bad)
  • Writing code locally, pushing it to github, and pulling it on the BBB (very bad!)

Requirements

A reasonably robust way to set up the BeagleBone without getting internet access on it.

@mynameis7
Copy link
Contributor

could we push code to its ip via git? doesnt gits decentralized nature work well with things like this? Git should be able to set up the beaglebone as a remote repository and then you could push and pull to and from it with an additional parameter in the git commands.

There might be more potential for merge conflicts like this, but for commiting and revising code this would work good i think.

For the user's sake, we could make shell or bat scripts for working with git specific to the bot. Currently, the git defaults to the github repo, which should be intended. maybe we could make a bat or shell script to commit and push code to the github repo and the bot.

@AhmedSamara
Copy link
Member Author

We are now using Raspberry pi, but it would be good to have a setup that works on both.

@mynameis7
Copy link
Contributor

If we setup a git server on the bot (maybe try gitlab community edition https://about.gitlab.com/) then we could add the bot as a remote, so then we can allow pushes directly to the bot when connected over USB or something like that. I'm not sure how PI handles a usb connection, but we could still use some of the spare routers lying around to provide an IP connection I think.

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

No branches or pull requests

2 participants