Code Monkey home page Code Monkey logo

docker-liferay-portal's Introduction

About this repo

This repository contains some nonofficial pet-projects on how to use Liferay with Docker.

Available Liferay Releases

  • Liferay 7.3.1 GA2
  • Liferay 7.3.0 GA1
  • Liferay 7.2.1 GA2
  • Liferay 7.2.0 GA1
  • Liferay 7.1.2 GA3
  • Liferay 7.1.1 GA2
  • Liferay 7.1.0 GA1
  • Liferay 7.1 RC 1
  • Liferay 7.1 Betas (1, 2, and 3)
  • Liferay 7.1 Alpha 2
  • Liferay 7.1 Milestone 1
  • Liferay 7.0 GAs (GA1, GA2, GA3, GA4, GA5, GA6 and GA7)
  • Liferay 7.0.0 Betas (7 and 8)
  • Liferay 6.2.0 GA6
  • Liferay 6.1.3 GA3

Environment variables

DEBUG_MODE

This variable is optional and allows you to specify if the container is run using a debug configuration. In the case of Tomcat, port 9000 will be exposed for debugging the application server.

LIFERAY_JVM_OPTS

This variable is optional and allows you to specify any value to the JAVA_OPTS, which will be appended to the existint Tomcat JAVA_OPTS. If no variable is passed, then an empty string will be appended.

Customized Environment support

We have removed the database support from this repo, which means pruning all old branches with code related to databases. For that reason, we will only maintain the base image so you could extend it very easily using, i.e., Docker Compose.

Supported Application Servers

These are the supported App servers:

  • Tomcat

Branch name convention

Since Liferay Portal 7.1, I won't support any other configuration than the default, which is Tomcat + HSQL. For that reason, the convention for branch names, using - as separator, is:

  • Liferay major version: 7.1
  • Liferay release: beta3, ga1, ga2...

So, if you are using Liferay 7.1 Beta3, you should use the 7.1-beta3 branch.

The git branch is named using the same convention, i.e.:

https://github.com/mdelapenya/docker-liferay-portal/tree/7.1-beta3

For previous releases, I've removed the support in this repo for any database, which in the end is a matter of using docker compose for spinning up a database, and configuring the portal to connect to it. For this reason I want to keep this repo as simple as possible.

License

These docker images are free software ("Licensed Software"); you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

These docker images are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; including but not limited to, the implied warranty of MERCHANTABILITY, NONINFRINGEMENT, or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

docker-liferay-portal's People

Contributors

mdelapenya avatar sammonsjl avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

smachado87 jhinkey liftedkilt cristian-trucco sarahcox1 otw1248 acrive82 bilelovic nagai-takayuki will-zhang-1981 amusarra sammonsjl saurabhvatsa eltechno safibaig lordlewo zoltancsaszi chromeilya denissignoretto ruromero omarezzine01 dravida byousri jguillemat miguelcarrondo ewuknadierf newbare criptocosmo ajayyeluri ganeshvidyayug dcfrancisco madhasha huyhvo xoanmallon omarnetfr is4ri jvmonjo biliroy arcko kavindevops

docker-liferay-portal's Issues

Fix gosu installation errors caused by gpg 

+ gpg --keyserver ha.pool.sks-keyservers.net --recv-keys B42F6819007F00F88E364FD4036A9C25BF357DD4
gpg: keybox '/tmp/tmp.EpMAteDQ2E/pubring.kbx' created
gpg: keyserver receive failed: Cannot assign requested address

Document or replace ONBUILD instructions

Could you please take a look @sammonsjl?

When using this image as base, it forces to have configs and deploy folders with any element inside, which could not be present. If we cannot replace that, then we must document that behaviour.

Startup fails because of dependency on MySQL

While starting the image using "docker-compose up", even though MySQL starts before Liferay, It is not available by the time Liferay needs it.
Since Liferay is dependent on MySQL, the startup of Liferay fails.
I tried using "wait-for-it" based on this reference, https://docs.docker.com/compose/startup-order/ . But I couldn't make it work. Any help would be great.

version : liferay-portal-7-ce-ga4-tomcat-mysql

How about liferay docker cluster with one remote database?

Does it possible to use liferay docker cluster with one database? I know we can setup liferay cluster and configure the db connection with one database in portal-ext.properties, but I wonder does it suitable for docker with liferay boundle?

telnet to gogo shell

Hi Manuel.
I'm not able to connect to gogo shell with this command.

After this command,
docker run -p 8080:8080 -p 11311:11311 mdelapenya/liferay-portal

I obtained

16:20:06,301 INFO [Start Level: Equinox Container: a006b0ae-32bb-0017-1b7e-c41741c30fee][BundleStartStopLogger:35] STARTED org.apache.felix.gogo.command_0.12.0 [31]
16:20:06,325 INFO [Start Level: Equinox Container: a006b0ae-32bb-0017-1b7e-c41741c30fee][BundleStartStopLogger:35] STARTED org.apache.felix.gogo.runtime_0.10.0 [32]
16:20:06,366 INFO [Start Level: Equinox Container: a006b0ae-32bb-0017-1b7e-c41741c30fee][BundleStartStopLogger:35] STARTED org.apache.felix.gogo.shell_0.10.0 [33]

Then, I typed

telnet localhost 11311
Trying ::1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

how can I connect to gogo shell after I turned on container?
Maybe, I have to write some options?

Thanks,
Regards
gabbo

persistent volume

Hi,

Im having trouble with the persistent volume.
In which path should I mount it?
Everytime I restart my container it gets back to default.
Im using version 7.2.1

Thanks

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.