MageSpawner | Shell script for quickly creating Magento test installations

by mzeis Shell Version: Current License: No License

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | MageSpawner Summary

MageSpawner is a Shell library. MageSpawner has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This is a little handy shell script that I am using for quite a while now. The goal is to quickly create new (and remove) Magento installations for testing purposes. Testing as in "I want to try something", not as in Unit Testing. Do not use this on a production machine. Ideally, use it on a machine where you don't care about losing everything. The remove script uses a "rm -rf" command, so if something goes wrong, it could go awfully wrong. I solely use this on a VM where everything important is backed up regularily.

Support

Quality

Security

License

Reuse

Support

MageSpawner has a low active ecosystem.

It has 47 star(s) with 8 fork(s). There are 4 watchers for this library.

It had no major release in the last 6 months.

MageSpawner has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of MageSpawner is current.

Quality

MageSpawner has no bugs reported.

Security

MageSpawner has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

MageSpawner does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

MageSpawner releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of MageSpawner

Get all kandi verified functions for this library.

MageSpawner Key Features

No Key Features are available at this moment for MageSpawner.

MageSpawner Examples and Code Snippets

No Code Snippets are available at this moment for MageSpawner.

Community Discussions

No Community Discussions are available at this moment for MageSpawner.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install MageSpawner

Get the files from Github.
Copy config.conf.sample to config.conf and adjust the settings as needed.
Make the files ./install and ./remove executable.
Run ./install and follow the instructions. If you didn't specify otherwise, sudo will be used for the commands chown and chmod. If you don't specify all parameters required for an install, you will be asked for the details in an interactive mode. Furthermore MageSpawner will save downloaded archive files so you don't have to download the file every time.
Add an entry two your hosts file. Your browser has to know which server the domain (e.g. 1702.magentoshops.vm) belongs to. If you use a real domain and have set an wildcard DNS record, then you are good to go. Otherwise, open your hosts file and a line like 192.168.1.2 1702.magentoshops.vm (don't forget to change this to the correct IP and domain).
Add an entry to your server configuration. Your web server has to know how to handle the request. Normally, you would have to add a Virtual Host every single time you setup a new Magento installation. As programmers don't like to repeat themselves and I'm a programmer, I'm using the Apache Module mod_vhost_alias and the nifty VirtualDocumentRoot directive. This is what my configuration looks like: <VirtualHost *:80> ServerAdmin my@email.com ServerName magentoshops.vm ServerAlias *.magentoshops.vm UseCanonicalName Off VirtualDocumentRoot /var/www/magento/shops/%0/ # Some more settings # Magento development settings SetEnv MAGE_IS_DEVELOPER_MODE 1 </VirtualHost> The VirtualDocumentRoot path /var/www/magento/shops/ has to match the MAGE_BASE_DIR setting in config.conf. The script automatically edits Magentos .htaccess so that the RewriteBase is adjusted for this setup.
You may want to do a fully automated installation. This feature was added in v0.3.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: