Nanobox is a portable, micro platform for developing and deploying apps. When working locally, Nanobox uses Docker to spin up and configure a virtual development environment configured to your specific needs. When you’re ready to deploy to live servers, Nanobox will take that same environment and spin it up on your cloud provider of choice, where you can then manage and scale your app through the Nanobox dashboard.
Nanobox can be used for local development on any number of projects (not only restricted to PHP). To start working with nanobox you will first create a free Nanobox account, then download and run the Nanobox installer. The account is used only to login to nanobox using the console command. Nanobox will remember your credentials so you only have to do this once. If your intent is only to use nanobox locally, you do not need to do anything else. The same login however can be used later on if you wish to deploy your application to a live environment.
Create a New Project
Create a project folder and cd into it:
mkdir nanobox-phalcon &&cd nanobox-phalcon
Add a boxfile.yml
Nanobox uses the boxfile.yml to build and configure your app’s runtime and environment. In the root of your project, create a boxfile.yml with the following:
Add a bash alias for Phalcon Devtools so you can just use the phalcon command.
Depending on the needs of your application, you might need to add additional extensions. For instance you might want to add mbcrypt, igbinary, json, session and redis. Your extensions section in the boxfile.yml will look like this:
NOTE The order of the extensions does matter. Certain extensions will not load if their prerequisites are not loaded. For instance igbinary has to be loaded before redis etc.
Add Phalcon Devtools to your composer.json
Create a composer.json file in the root of your project and add the phalcon/devtools package to your dev requirements:
NOTE: The version of Phalcon Devtools depends on which PHP version as well as Phalcon version you’re using.
Start Nanobox and Generate a New Phalcon App
From the root of your project, run the following commands to start Nanobox and generate a new Phalcon app. As Nanobox starts, the PHP engine will automatically install and enable the Phalcon extension, run a composer install which will install Phalcon Devtools, then drop you into an interactive console inside the virtual environment. Your working directory is mounted into the /app directory in the VM, so as changes are made, they will be reflected both in the VM and in your local working directory.
# start nanobox and drop into a nanobox console
# cd into the /tmp directorycd /tmp
# generate a new phalcon app
phalcon project myapp
# change back to the /app dircd -
# copy the generated app into your projectcp-a /tmp/myapp/*.# exit the consoleexit
Run the App
Before actually running your new Phalcon app, we recommend using Nanobox to add a DNS alias. This will add an entry to your local hosts file pointing to your dev environment and provide a convenient way to access your app from a browser.
nanobox dns add local phalcon.dev
Alternatively you can use the IP address of your container. The IP address is displayed when you first run your container. If you forgot or did not notice it, on a separate terminal, navigate to the same folder that your project lives on your system and type
nanobox info local
The output of this command will show you all the IP addresses of your containers/components as well as passwords to databases (if applicable).
Nanobox provides a php-server helper script that starts both Apache (or Nginx depending on your boxfile.yml config) and PHP. When passed with the nanobox run command, it will start the local dev environment and immediately run your app.
nanobox run php-server
Once running, you can visit your app at https://phalcon.dev.
Check Out the Environment
Your virtual environment includes everything you need to run your Phalcon application.
# drop into a Nanobox console
# check the php version
php -v# check that phalcon devtools are available
# check that your local codebase is mountedls# exit the consoleexit