-
Notifications
You must be signed in to change notification settings - Fork 9
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
Ready to go VM images #21
Comments
This sounds like a good idea. Do you need some place to upload it to? I have some spare resources and could easily spin up a vm for you. |
Thanks. |
Sounds like a good plan. We can either host it on google drive, or do some private hosting (as said, resources shouldn't be the problem). Or maybe we just mirror them. |
My rationale for using something like Google Drive or Dropbox is simply, that it would seem more secure. As a user I'd feel better, if the giant collection of software, which a VM basically is, is hosted by a company, who would at least make sure that it isn't basically one huge root kit. But I just realize, that this would be a perfect use case of Vagrant! I'm going to explore this possibility. |
Indeed. 👍 for Vagrant. |
I could upload a VM image with a working setup somewhere. This should make debugging and development a lot easier.
The text was updated successfully, but these errors were encountered: