In today’s article, I describe the Akeneo PIM installation process on the Ubuntu 16.04 system using a docker.
If you don’t have a docker installed (along with docker-compose), you can do it according to the instructions here: https://docs.docker.com/install/linux/docker-ce/ubuntu/
You can install Docker-compose with these commands:
curl -L https://github.com/docker/compose/releases/download/1.22.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose chmod +x /usr/local/bin/docker-compose
Let’s start off running Akeneo PIM. We start with cloning the repository:
git clone https://github.com/akeneo/pim-community-standard.git
As you can see, Akeneo has already prepared a file
docker-compose.yml, or you, which will significantly affect the amount of our work.
For starters, you need to decide on which port you will have access to your Akeneo PIM instance. I work in a dedicated environment for PIM, so I’ll be using the standard port 80. If another service already occupies this port, choose another (the popular choice will be 8080, or 8888).
In the file
docker-compose.yml prepared by Akeneo, the port is determined by the variable
DOCKER_PORT_HTTP. You can, therefore, set the chosen port with the command:
Then you take remote pictures of the docker using the command:
Now you have to take care of basic configuration options for our PIM. Copy the file with Symfony configuration:
cp app/config/parameters.yml.dist app/config/parameters.yml
and change it for the docker environment. In the end, your file should looks like this (the production version should, of course, have better passwords):
parameters: database_driver: pdo_mysql database_host: mysql database_port: ~ database_name: akeneo_pim database_user: akeneo_pim database_password: akeneo_pim locale: en secret: ThisTokenIsNotSoSecretChangeIt product_index_name: akeneo_pim_product product_model_index_name: akeneo_pim_product_model product_and_product_model_index_name: akeneo_pim_product_and_product_model index_hosts: 'elastic:changeme@elasticsearch:9200'
You must also take care of the permissions for our catalog. All operations on the containers will be performed on the docker user. The easiest way to ensure that our system works in terms of permissions is to modify the permissions and assign files to the docker group and enable the group to sign up:
chgrp docker . -R chmod g+w . -R
Now you can start your containers:
docker-compose up -d
You’re only a few clicks away from success. Akeneo has prepared two scripts for you:
Run both. At first, you’ll probably get a message that we have to use our GitHub token to jump over the limitations of repositories. Log into github.com and then go to the link provided in the console. It looks something like this: https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+X-Coding+2018-07-25+1356
Copy the displayed token and paste it in the console (the token is saved in the GitHub account, but it isn’t possible to see it later, we can simply generate another token).
After completion of this process, you can log into our Akeneo PIM instance. The default credentials are admin/admin.
I hope I helped you understand the Akeneo PIM installation process a little better. If there is something else you want to know — let me know in the comments.