Download the PHP package midgard/midgardmvc-project-template without Composer
On this page you can find all versions of the php package midgard/midgardmvc-project-template. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package midgardmvc-project-template
midgardmvc-project-template
This is a project template for creating new websites or applications powered by the Midgard MVC framework for PHP.
Creating new Midgard MVC projects
This project template is designed to be used together with the Composer PHP dependency management tool. You can create new Midgard MVC projects on your current machine with:
$ composer create-project midgard/midgardmvc-project-template myprojectThis will download the Midgard MVC project template and set it up together with the dependencies. This new project will be set up in the myproject directory.
Where is everything?
The Midgard MVC project template follows a file structure typical for Composer-installed Midgard MVC applications:
application.ymlcontains the application configuration, including site's node hierarchy and list of enabled componentscomposer.jsonlists the dependencies for your applicationmanifest.ymlcontains routes for the site's main component (in this casemidgardmvc_project_template)controllerscontains controllers of the main componenttemplatescontains templates of the main componentvendorcontains all Composer-installed dependencies, including Midgard MVC invendor/midgard/midgardmvc-corevarcontains logs and caches used by the Vagrant setup
Creating development VMs with Vagrant
Vagrant gives an easy way to manage development virtual machines using Midgard MVC.
Dependencies
- Vagrant
- NFS (out-of-the-box in OS X, on Debian-based Linux systems install
nfs-kernel-server)
Installation
To set up a Vagrant project, download this project template, and then:
$ cd setup/vagrant
$ vagrant upThe up command will download a Ubuntu 12.10 base image, start it in VirtualBox and then use the Puppet configuration management system to set up Midgard2, PHP, AppServer-in-PHP, and your Midgard MVC project.
This setup can take a long time depending on your internet connection. Once it is done, there should be a Midgard MVC instance running based on your project setup. You can access it at http://localhost:8181.
Usage
The Vagrant VM will mount your project directory over NFS, and so all of your file changes will apply to the virtual machine instantly. If you need to tweak something on the VM, you can get an SSH connection to it with:
$ vagrant sshYour mounted project directory will be available in /opt/midgardmvc.
Restarting AiP
Since AiP is a persistent PHP process, you'll need to restart it when you make changes to your files. You can do that after vagrant ssh with:
$ sudo service midgardmvc stop
$ sudo service midgardmvc startManaging the virtual machine
You can use the vagrant halt command to stop your virtual machine, and vagrant up to restart it.
If you want to start from scratch, simply run vagrant destroy, and rebuild the VM image with another vagrant up.
If you want to distribute your VM image with your team, read the Vagrant packaging documentation.
