![]() # Based on Liferay 6.2 VERSION 0.0.7 using liferay 6.2-ce-ga4 by Samuel Nasello # 0.2 (20150902): (not yet) working version with the above and Social Office CE plugged in # 0.1 (20150901): working version with persistent postgresql database without plugins The liferay_so_lrsync container is built with the following dockerfile content: # Liferay + Social Office + Liferay Sync + RCS Newsletter Then I launch the Liferay with Tomcat container: sudo docker run -name=lr -p 8080:8080 -v /var/liferay-home/deploy:/opt/liferay-portal-6.2-ce-ga4/deploy -link lep-postgresql:db_lep -d -e DB_TYPE=POSTGRESQL richarduijen/liferay_so_lrsync:latest GRANT ALL PRIVILEGES ON DATABASE lportal to lportal I create a postgresql database: sudo docker run -name lep-postgresql -v /opt/pg_lr/dbdata:/var/lib/postgresql -d postgres:9.4įollowed by: sudo docker run -it -link lep-postgresql:postgres -rm postgres:9.4 sh -c 'exec psql -h $POSTGRES_PORT_5432_TCP_ADDR -p 5432 -U postgres'ĬREATE USER lportal WITH PASSWORD 'lportal' ĬREATE DATABASE lportal WITH ENCODING 'UTF8' Or did I simply make an error when I committed the changed container or pushed the committed image? Any ideas? Has anyone else ventured into these areas? Is there a third way to collect the container contents (not being user data) to the repository (apart from building from dockerfiles, or the committing of changed containers)? Therefore I’m running out of ideas on how to develop the portal container further. I don’t exactly know what steps liferay portal takes to deploy lpkg files. (The push process cost me all morning - soooooo slow that I am also thinking about reconsidering the use of docker altogether.)Īfter a successful push, I ran the image on a different computer… but the plugin was not there. Then commit the - I thought: changed - container. So the plugin must be installed manually after the container has started, if I use this way to develop the website.Īnother idea I had, was to have a container running, then manually install the plugin (by copying it to the deploy directory, after which it is running in the container). ![]() If I copy the plugin.lpkg file to the automatic deploy directory in the Dockerfile, the file is not copied when I run the container. So far so good, I managed to have liferay running in docker on a postgresql database. I’m trying to build a liferay website with plugins in a docker container. I’m still new at using docker, so if this topic is discussed or explained somewhere (else), please point me there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |