![]() |
VOOZH | about |
Free open source ecommerce platform created in 2024. https://mahocommerce.com
10K+
This image is specifically designed for deployment in cloud-based production environments such as Sevalla, DigitalOean, and similar PaaS providers. This image does not include MySQL or any database. You will need to provision a managed MySQL database separately through your cloud provider.
nightly: dev-main version of Maho, running on latest FrankenPHP +PHP 8.5latest: latest stable release version of Maho (26.1.0), running on latest FrankenPHP +PHP 8.526.1.0-php8.526.1.0-php8.426.1.0-php8.325.11.0-php8.425.11.0-php8.325.9.0-php8.425.9.0-php8.325.7.0-php8.425.7.0-php8.325.5.0-php8.425.5.0-php8.325.5.0-php8.2local.xml file with all configurationslocal.xml and change the configuration options as needed (eg: replacing database hostname, user, pass etc)MAHO_LOCAL_XML and copy the contents of the previously edited local.xml into itcore_config_data table, fixing the domain name for the websiteMAHO_LOCAL_XML and paste the contents of the local.xml into it (the previously created file would be lost by a new deployment or by an update of the docker image)Remember that Maho stores file uploads (eg: product images) in the public/media folder. Since you do not want to lose those important files, you should configure a persistent disk through your cloud infrastructure and mount it on /app/public/media, then restart the whole infrastructure and test that files actually get saved to that disk.
Note: most of the cloud providers will allow you to mount a persistent disk to one container/machine only, that means that at the moment you won't be able to have more than one frontend nodes. In case you need more power, you have two options:
NFS share for the public/media folder, then mount it into the frontend nodesWe're working on supporting S3 compatible storage for better horizontal scaling but that's not available at the moment.
docker-compose configurationservices:
php:
container_name: maho
image: mahocommerce/maho:latest
environment:
- SERVER_NAME=maho.local
ports:
- ${HTTP_PORT:-80}:80
- ${HTTPS_PORT:-443}:443
- ${HTTPS_PORT:-443}:443/udp
restart: unless-stopped
volumes:
- .docker/data:/data
- .docker/config:/config
- ./app:/app/app
- ./media:/app/public/media
tty: true
mysql:
container_name: mysql
image: mysql:latest
environment:
- MYSQL_DATABASE=maho
- MYSQL_USER=maho
- MYSQL_PASSWORD=askmd72BBSspak
- MYSQL_ROOT_PASSWORD=MaajwekSNUsk242sred
ports:
- "3306:3306"
restart: unless-stopped
volumes:
- ./mysql-data:/var/lib/mysql
This configuration with have the app (which mainly will contain local.xml), media and mysql-data folders directly mapped on the host, but you can manage those the way you prefer the most.
After starting the containers, you can install Maho with:
docker exec -it maho ./maho install --license_agreement_accepted yes --locale en_US --timezone Europe/London --default_currency EUR --db_host mysql --db_name maho --db_user maho --db_pass askmd72BBSspak --url https://maho.local/ --secure_base_url https://maho.local/ --use_secure 1 --use_secure_admin 1 --admin_lastname admin --admin_firstname admin --admin_email [email protected] --admin_username admin --admin_password qwe123098poiqwe123098poi --sample_data=1
docker exec -it maho ./maho index:reindex:all
docker exec -it maho ./maho cache:flush
We all know an ecommerce project needs addon modules and custom development, thus, most probably, you won't be able to use this image as is. Our suggestion is to import it in your project repository and build your own on top if it. This way you'll take advantage of the official developments/support/updates, with the power of your custom implementations.
Content type
Image
Digest
sha256:587e1f064…
Size
281.8 MB
Last updated
about 12 hours ago
docker pull mahocommerce/maho:nightlyPulls:
359
Last week