# Requirements for Foodomaa ### Google Cloud Account A Google Cloud Account with proper **Billing Setup** is the most important thing required to use Foodomaa™.\ Foodomaa™ relies on many APIs provided by Google Maps.\ \ Geocoding API, Maps Javascript API, Places API, Maps Static API, GeoLocation API, Distance Matrix API are the APIs Foodomaa™ uses without which it is **impossible** to use Foodomaa™.\ \ Also, we cannot replace the Google APIs dependency with any other services like MapBox or OpenStreetMap or anything else as our system is fully coupled with Google Services internally. [Click here](/configurations/google-maps-api-keys.md) to learn how to set up a Google Cloud Account with billing and APIs.
### Server We provide a **`.htaccess`** configuration file that works well with any Apache server.\ \ Nginx or LiteSpeed or any other server is **NOT** officially supported and we **CANNOT** help with the server configuration of any kind if your server uses anything other than Apache.
### Hosting Services Foodomaa™ works very well with all major managed hosting providers. To name a few, GoDaddy, Hostinger, NameCheap, BlueHost, SiteGround, HostGator.\ \ All managed hosting provides would support an easy to use cPanel through which Foodomaa™ can literally be installed in just 5 minutes. (We also offer installation support for these hosting providers) If you use a Cloud Hosting service like AWS, GCloud, DigitalOcean, etc, we **DONOT** support for installation or server configuration on these services. \ \ If you use a Cloud Hosting or a dedicated server where you have configured the server on your own, the support will only be resumed after you have completed installation and setup for Foodomaa™. ### PHP Version Foodomaa™ requires PHP v7.3.\ Although PHP v7.4 can be used with Foodomaa™ but later if you face any issues, the first thing which we would suggest over support ticket to you will be to fall back to PHP v7.3 as that's the only Officially support PHP version.
### PHP Extensions The following PHP extensions are mandatory to use Foodomaa™: * OpenSSL PHP Extension * PDO PHP Extension * Mbstring PHP Extension * Tokenizer PHP Extension * XML PHP Extension * Ctype PHP Extension * JSON PHP Extension * ZIP PHP Extension * FileInfo PHP Extension * BCMath PHP Extension * ionCube Loader PHP Extension * GD PHP extension Optionally, you should also enable the **`OpCache PHP Extension`** for better performance. It is not mandatory but recommended. #### How to Enable PHP Extensions? On a manages hosting provider (like GoDaddy, Hostinger, etc) you will have an option to change the PHP Configuration under the name "**Php Versions**" or "**Php Configurations**" or "**Php Extensions**" or some similar names. There you can find a similar view as shown below:
![](/files/-MR3SJulZBXU1ezRxVnN) From this list, check all the required extensions and Save/Apply the settings.
{% hint style="warning" %} From version 2.5.0 Foodomaa™ requires **ionCube Loader PHP Extension** 99% of the hosting providers have this Extension pre-installed and you will just need to enable it as shown above.\ \ But if your hosting provider doesn't have ionCube Loader installed, you will need to contact your hosting provider support. \ \ If you are on a Cloud/Dedicated server like AWS, GCloud, or similar servers, please follow [this documentation](https://www.ioncube.com/loaders.php) to install the ionCube Loader yourself. \ \ You could also refer to any other article that suits your hosting server. \ \ NOTE: Support **CANNOT** be provided to install any of these PHP extensions on your server. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.foodomaa.com/extras/requirements-for-foodomaa.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.