There used to be a gui where you could configure PuPHPet settings for vagrant.
It would allow you to set, shared folders, users, Apache, Mysql, etc.
I can't seem to find this site anymore. Is it gone?
Is there an alternative way to configure a vagrant for Magento?
PuPHPet is abadoned according to it's creator: https://twitter.com/juantreminio/status/1199022035588075520
However, the whole project was open source and you can find the repositories here:
https://github.com/puphpet
Related
I have a new developer coming to work with me soon, and I'd like to make it as simple as possible for them to get a development environment set up.
I'm currently using a Vagrant (Laravel Homestead) box with about 15 domains set up, each with different configurations (different PHP versions etc), and I'd like to just share the existing box with them if possible.
Is it as simple setting up a repository with the VagrantFile, getting them to clone it and provision the box, or are there more steps involved?
Also, I've had to edit the MySQL configuration on the box, is there any way I can include these updates in what I share with them, or will they just need to reconfigure their own version manually?
Any advice appreciated.
Thanks
The easiest way to share the Homestead environment is to use the after.sh file to to perform any customization you may need beyond what Homestead gives you.
You can also copy your Homestead.yaml file to Homestead.yaml.example for the new coworker to easily copy and paste the sites & any other configuration changes.
I'm running an instance of Galaxy NGS in an Ubuntu server, with a basic configuration, postgresql database, and apache.
When I log in as Admin in the Galaxy interface, and try to add a new tool through the tool shed, the tool is installed and I can use it without problems
However, if Galaxy needs to be restarted, the tool does not appear anymore
I followed the instructions here to configure a folder to keep the installed tools, like it explains there, adding a line in config.ini with the desired folder
tool_dependency_dir = dependency_dir
But that doesn't do the trick and the tools are not stored in the folder anyway
Does somebody have a clue on what could I be missing?
The problem was solved after switching from apache to nginx, and changing the line I posted to
tool_dependency_dir = /home/galaxy/tool_deps
I found a nice resource that helped me with the configuration in case somebody faces the same issue.
https://wiki.galaxyproject.org/Events/BioITWorld2014/W14#Setting_up_a_Local_Galaxy_Tutorial_.28Part_I.29
I want to export/import only site structure not the content using Oracle WCS CSDT Plugin command line tool.
Basically, I want empty site to be created on production env without content, and content editors will publish content from staging once basic site is available.
Does anyone has an idea, how I'll do it?
I Think you can mirror the site which doesn't publish any content.
on admin tab, select the site you want and double click on it.
There you will see publish destinations. click on mirror site configuration for required environment and you can do it by selecting required things to mirror.
Well, I don't think this is the recommended way to do so, I actually think the CSDT tool isn't recommended by Oracle (will look up a source and amend my answer ASAP, just wanted to catch you before the irreversible happens).
Instead publish to the production environment from the current one, if it's not reachable you can publish to an installation on a portable machine (laptop or something) or maybe even a JSK (Jump Start Kit) on and the from the JSK to production.
Hope this helps.
Although its been one year, just to answer this question, I am pointing out what I did in my past projects:
I want to export/import only site structure not the content using Oracle WCS CSDT Plugin command line tool.
Yes, this is quite feasible to do so via command line or even by using ANT or maven script
Basically, I want empty site to be created on production env without content, and content editors will publish content from staging once basic site is available.
Once site is imported using CSDT, editors can publish. But note: asset types, attributes, etc. which were created using your local instance or JSK will have different asset id as compared to Staging instance.
Hence, rather than using CSDT, preferred way is to just initialize site and then mirror assettypes, attributes, attribute editors, etc. from Staging to Production and then publish attributes, etc. from Staging to Production. When production is ready with all basic configurations, editors can just publish content as they see fit.
Are there any tools that I can use to automatically build vagrant base boxes on a remote linux server. It'll be better if it is extendable and version control friendly.
Thanks. First question on SO.
Packer can create Vagrant boxes. It's from the same company that have created and maintain Vagrant.
http://www.packer.io/docs/post-processors/vagrant.html
Another valid option is Veewee, as pointed out in a previous answer.
Try out veewee: https://github.com/jedi4ever/veewee
I'm not sure by "extendable" what you mean. veewee should do the job. it supports debian preseed file and other configurations that can be checked into version control.
We have multiple projects that each are going to use Vagrant for managing their development environments. We're happily using Chef for provisioning and all that's working fine. But, we're finding that our Vagrantfiles have a lot of cut'n'paste between them. We'd like to consolidate our Vagrantfile definitions so that they can share from a common Vagrantfile-library (either locally or installed from some remote location). Is this a thing?
One good way could be to include the common directives of your Vagrantfile in a custom box.
A box is just a .tar or tar.gz file containing all the stuff needed by the provider for running the Vagrant instances. As far as I know, all provider-specific formats allow adding a Vagrantfile with common settings to the box.