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

Update main README to explain repo structure #7

Closed
ruebot opened this issue Feb 19, 2015 · 8 comments
Closed

Update main README to explain repo structure #7

ruebot opened this issue Feb 19, 2015 · 8 comments

Comments

@ruebot
Copy link
Member

ruebot commented Feb 19, 2015

No description provided.

@mark-cooper
Copy link
Contributor

Appreciate all the documentation that is being added, really helps while following along 👍

I have an Ansible playbook in progress to shadow what is happening with the shell provisioner in vagrant but with the advantages that Ansible provides (reprovisioning will work properly and the inventory can reflect a production like distributed deployment structure while installing all of the components onto a single VM for testing).

If I can make a suggestion it would be to make the sync documentation clearer (in terms of building and deploying it), but I'm probably getting ahead of things, I realize it's very early in the process.

@ruebot
Copy link
Member Author

ruebot commented Feb 19, 2015

Thanks @mark-cooper! If you do mind, can you create an issue w/r/t the sync documentation, and we'll take care of it.

As for the Ansible playbook, this is great! If you have any thoughts/ideas on how we can incorporate it into our repo, please don't hesitate to let us know!

@daniel-dgi
Copy link
Contributor

Great comment Mark. I'll be sure to add build / deploy instructions as soon as possible. We're still early in the game and things are in flux (just ditched chef for basic bash script), but your feedback is certainly valuable.

@daniel-dgi
Copy link
Contributor

Ruebot beatin' me to the punch. Yeah, what he said :P We'll definitely take care of this for ya.

@mark-cooper
Copy link
Contributor

Thanks both!

"If you do mind, can you create an issue w/r/t the sync documentation, and we'll take care of it." -- will do.

"If you have any thoughts/ideas on how we can incorporate it into our repo, please don't hesitate to let us know!" -- I'll bring it up to equivalency with the shell approach, and then if you think it will be beneficial I'll have no issue with offering it up.

@ruebot
Copy link
Member Author

ruebot commented Feb 20, 2015

That's great Mark! I'm really happy to see community alternative devops setups this early on in the project.

I'll assume you're covered by the LYRASIS Corporate Contributor License, so we could just transfer over the repo to this Islandora Labs org, and then I could just set you as a contributor here, so you can push to the repo as you please. I'll double check and make sure this is all cool with everybody tomorrow on our roadmap call. (tagging @manez since I don't see a roadmap call agenda.)

ruebot added a commit that referenced this issue Feb 20, 2015
@ruebot
Copy link
Member Author

ruebot commented Feb 20, 2015

Checkout out the main README, and let me know if that addresses this ticket properly.

@mark-cooper
Copy link
Contributor

I'll give a 👍

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

No branches or pull requests

3 participants