Hi dragon788, Thanks for the response, I will investigate that. Borja. El viernes, 17 de septiembre de 2021 a las 0:15:22 UTC+2, dragon788 escribió:
> I believe there is a vagrant package command that allows you to export the > current state of a box and then you could share that file with your > colleagues and they could do a vagrant box add. > > > > On Thursday, September 16, 2021 at 9:43:40 AM UTC-5 jmc...@gmail.com > wrote: > >> While other uses are possible, the two main uses of Vagrant are to >> instantiate virtual machines with a defined configuration for either >> testing or for a particular ensemble of development tools, reproducibly. >> >> The virtual machines created with vagrant are not particularly different >> from VMs created using other methods; they may be a bit less secure because >> of some considerations that went into vagrant's conventions; they are >> reproducible to the extent that every version of every kernel module, >> program and library is initially fixed in the "box" file that the VM is >> created from. >> >> But for a coworker to take advantage of Vagrant's features, they would >> need a vagrant setup of their own. Given a copy of your vagrantfile, they >> could then produce a replica of your vagrant machine, but it's considerably >> more involved than a URL or click. >> >> The problem you are trying to solve does not look like a particularly >> good fit. >> >> I read your question as wanting to know how to reproduce a working >> development environment where you may not have started out with strict >> control over all of the versions of all of the modules, libraries, or other >> development tools. You might be able to use a Vagrant-related tool like >> Packer to freeze a particular existing environment for purposes of >> reproducing it elsewhere, but it does not truly solve the underlying >> problem of gaining control over the library dependencies, etc. >> >> With most VM hypervisors or tools like docker, there are ways to snapshot >> any existing workspace so that it could be duplicated and shared with >> someone else. And there are any number of configuration and provisioning >> tools like Ansible, Puppet, or Chef that allow you to more closely control >> and document the building of your development environment so the >> configuration can be more controlled (and also regenerated). >> >> -- jmcg >> >> >> >> >> >> >> >> On Thu, Sep 16, 2021 at 7:13 AM Borja Aizpurua Altuna < >> a90...@alumni.unav.es> wrote: >> >>> Hi, >>> I have been working with a raspberry and have created a new program that >>> requires some libraries. My boss has asked me to see if I can use Valgrant >>> to save a session with the new program and all the necessary libraries so >>> that he can whenever he wants access it with an URL or a click. Is it >>> possible? >>> >>> I have read about Valgrant funcionalities, and I am not sure if this is >>> possible. Moreover, I have understood that he could access my working >>> access only if it is running, I mean, my Valgrant workingspace should then >>> be active whenever he needs it. Am I correct? >>> >>> Any help is appreciated, >>> Thanks, >>> Borja. >>> >>> -- >>> This mailing list is governed under the HashiCorp Community Guidelines - >>> https://www.hashicorp.com/community-guidelines.html. Behavior in >>> violation of those guidelines may result in your removal from this mailing >>> list. >>> >>> GitHub Issues: https://github.com/hashicorp/vagrant/issues >>> Discuss: https://discuss.hashicorp.com/c/vagrant/24 >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to vagrant-up+...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/vagrant-up/93c3b630-503d-428e-b07b-931701a05cf5n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/vagrant-up/93c3b630-503d-428e-b07b-931701a05cf5n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/402a5117-2dbc-452d-bad9-1b825cd5685bn%40googlegroups.com.
