All Saleor services started from a single repository
Keep in mind this repository is for local development only and is not meant to be deployed on any production environment! If you're not a developer and just want to try out Saleor you can check our live demo.
- Clone the repository:
$ git clone https://github.com/mirumee/saleor-platform.git --recursive --jobs 3
-
We are using shared folders to enable live code reloading. Without this, Docker Compose will not start:
- Windows/MacOS: Add the cloned
saleor-platformdirectory to Docker shared directories (Preferences -> Resources -> File sharing). - Windows/MacOS: Make sure that in Docker preferences you have dedicated at least 5 GB of memory (Preferences -> Resources -> Advanced).
- Linux: No action required, sharing already enabled and memory for Docker engine is not limited.
- Windows/MacOS: Add the cloned
-
Go to the cloned directory:
$ cd saleor-platform
- Build the application:
$ docker-compose build
- Apply Django migrations:
$ docker-compose run --rm api python3 manage.py migrate
- Collect static files:
$ docker-compose run --rm api python3 manage.py collectstatic --noinput
- Populate the database with example data and create the admin user:
$ docker-compose run --rm api python3 manage.py populatedb --createsuperuser
Note that --createsuperuser argument creates an admin account for admin@example.com with the password set to admin.
- Run the application:
$ docker-compose up
Both storefront and dashboard are quite big frontend projects and it might take up to few minutes for them to compile depending on your CPU. If nothing shows up on port 3000 or 9000 wait until Compiled successfully shows in the console output.
This repository contains newest stable versions. When new release appear, pull new version of this repository. In order to update all of them to their newest versions, run:
$ git submodule update --remote
You can find the latest version of Saleor, storefront and dashboard in their individual repositories:
- https://github.com/mirumee/saleor
- https://github.com/mirumee/saleor-dashboard
- https://github.com/mirumee/saleor-storefront
Most of the time both issues can be solved by cleaning up space taken by old containers. After that, we build again whole platform.
- Make sure docker stack is not running
$ docker-compose stop
- Remove existing volumes
Warning! Proceeding will remove also your database container! If you need existing data, please remove only services which cause problems! https://docs.docker.com/compose/reference/rm/
docker-compose rm
- Build fresh containers
docker-compose build
- Now you can run fresh environment using commands from
How to run it?section. Done!
If you are getting issues with lack of available space, consider prunning your docker cache:
Warning! This will remove:
- all stopped containers
- all networks not used by at least one container
- all dangling images
- all dangling build cache
More info: https://docs.docker.com/engine/reference/commandline/system_prune/
I've been warned
$ docker system prune
docker-compose up api workerfor backend services onlydocker-compose upfor backend and frontend services
- Saleor Core (API) - http://localhost:8000
- Saleor Storefront - http://localhost:3000
- Saleor Dashboard - http://localhost:9000
- Jaeger UI (APM) - http://localhost:16686
- Mailhog (Test email interface) - http://localhost:8025
If you have any questions or feedback, do not hesitate to contact us via Spectrum or Gitter:
Disclaimer: Everything you see here is open and free to use as long as you comply with the license. There are no hidden charges. We promise to do our best to fix bugs and improve the code.
Some situations do call for extra code; we can cover exotic use cases or build you a custom e-commerce appliance.