This section covers the installation process of the Qobrix onto a new environment. For now, we are focusing on the development environment. Once you are comfortable with that, we’ll get into deployment process for remote servers and environments. We assume that by now you have a development environment setup on your computer, and you also have access to the code repository, as well as an Internet connection. We’ll rely on the command line interface in order to document all the necessary steps of the installation. If you are using a graphical user interface (GUI) or integrated development environment (IDE), you’ll need to adjust the steps below to your tool chain accordingly.
Getting the Source Files
The fastest and the most reliable way to get the copy of the latest source files is to use git version control.
# Navigate to your projects folder cd ~/Work # Clone the repository (adjust the URL) git clone email@example.com:QoboLtd/example.com.git # Navigate into the project (adjust the directory name) cd example.com
Qobrix relies on dozens of third-party libraries and tools. You can install all of them using Composer dependency manager. While you might already have a system-wide installation of composer, it is recommended to use the copy which comes with the project files.
# This will take a minute ... get some coffee. ./bin/composer install
Now that you have all the source files and dependencies, it is time to setup the application. Run the following command to create and populate the database, fix file and folder permissions, initiate the cache, and so on.
# Robo run ./bin/build app:install DB_NAME=my_app
If all of the above commands finished successfully, you can now run the application.
# PHP built-in web server with a few settings ./bin/phpserv
Navigate your browser to HTTP, localhost, port 8000.
If all went well
Normally, things should just work. If everything went without a hitch, you should see Qobrix login screen in your browser.
If something went wrong
It’s nice when things just work. But sometimes they don’t. Mostly this is because there are numerous factors and variables varying between your development environment and what we are used to. In case something went wrong and you don’t see the login screen as above, but a fatal error instead, or one of the previous steps failed, here’s what you can do.
# Undo the setup ./bin/build app:remove # Generate the configuration file ./bin/build project:dotenv-create # Adjust the configuration file vim .env # Save and exit Vim 🙂 asjksdkljklxxxqqwq^C^C^C^C^Mas # Run the setup again ./bin/build app:install
Now you can try running the application again.