Install on Ibexa Cloud¶
Ibexa Cloud enables you to host your application in the cloud by using the Platform.sh service.
1. Prepare configuration files¶
If you didn't run the
composer ibexa:setup command during installation, run it now:
This command adds to your project configuration files required for using Ibexa Cloud.
You can adapt the configuration in the following places:
.platform.app.yaml- main configuration
.platform/services.yml- additional services such as search engines or cache
.platform/routes.yml- routes to additional services, for example Fastly
For details about available configuration settings, refer to Platform.sh documentation.
The total disk space depends on your Ibexa Cloud subscription level.
You can assign disk space to the main app container under the
You can distribute the remaining space between other containers (for example, the database) or search engine
.platform/services.yaml, under the individual service definitions.
Build and deploy process¶
hooks defines the process of building and deploying your project.
During the build phase (defined in the
hooks.build configuration), files in the project have read/write permissions (can be modified).
During deployment (defined in the
hooks.deploy configuration), all files in the project are read-only.
.platform/services.yaml contains preconfigured setting blocks that you can uncomment
to enable services such as Solr or Elasticsearch, or persistent Redis session storage.
For information about available services, see Platform.sh documentation.
If you enable any of the services, you must uncomment the relevant relationship
relationship key in
.platform.app.yaml as well.
2. Create an account¶
Log in to https://cloud.ibexa.co or create an account if you do not have one yet.
Create a project and select its region.
3. Prepare for hosting¶
After the project is created, the website walks you through preparing your project for hosting. This includes adding an SSH key, and adding Platform.sh as a git remote.
Add your Composer authentication token to the project before pushing it to Platform.sh. You can set this token as an environment variable.
When you do, make sure the Visible during runtime box in Platform.sh configuration is unchecked. This ensures that the token is not exposed.
4. Push the project¶
When you are done with configuration, push your project to the Platform.sh remote:
master is the Platform.sh name for the production branch.