Olaf Kock 8年 前 Neat. Installing Tomcat Demos is easy already, but this is another order of magnitude. Sounds like well digestible magic ingredients. 投票するためにはログインが必要です。 次として送信する: キャンセル
David H Nebinger 8年 前 My issue has not been getting LR7 up and running, that has been pretty standard if you heed the instructions.But without the build chain in place, I can't do much with it. I have a SB portlet which I just can't build for 7 because SB is broken. There's discussion about having to have a particular version of maven (or other) artifacts but I haven't yet been able to complete a single build targeting LR7.I'm guessing I'm not alone in this challenge.As soon as I can successfully build artifacts targeting LR7, I'll be able to work on converting my plugins and see how they fit in the new environment. Until then all I can really do is look at the brochure site and see how it looks.I'm sure the toolchain will stabilize soon, and I'm just chomping at the bit waiting to get to work... 投票するためにはログインが必要です。 次として送信する: キャンセル Milen Dyankov David H Nebinger 8年 前 - 編集済み You are unfortunately right. Neither `liferayctl` nor the docker images make Liferay 7 more ready then it actually is ;) 投票するためにはログインが必要です。 次として送信する: キャンセル
Milen Dyankov David H Nebinger 8年 前 - 編集済み You are unfortunately right. Neither `liferayctl` nor the docker images make Liferay 7 more ready then it actually is ;) 投票するためにはログインが必要です。 次として送信する: キャンセル
Manuel de la Peña 8年 前 Very nice tool Milen!!It could be great adding the ability to fetch a specific commit instead of a released version. How difficult could it be implement it? 投票するためにはログインが必要です。 次として送信する: キャンセル Milen Dyankov Manuel de la Peña 8年 前 IMHO it makes no sense to use Docker for this kind of thing. I agree that such script / command line tool may come handy. Basically it would need to grab the source code from GitHub, try compile it, deal with all the potential errors, make sure the target artifacts are created properly. At that point it could create a Docker container and put the result in, but honestly speaking I don't see why would one want to do that. Releasing images on Docker Hub that contain Liferay portal built from a particular commit would hardly be useful to anyone but the author IMHO. 投票するためにはログインが必要です。 次として送信する: キャンセル Manuel de la Peña Milen Dyankov 8年 前 What about a continuous-release process? Imagine having that tool to generate dockerfiles for engineers to tests/release an specific commit of Liferay? 投票するためにはログインが必要です。 次として送信する: キャンセル Milen Dyankov Manuel de la Peña 8年 前 - 編集済み So you can actually try it out using the docker image build process from https://github.com/milendyankov/liferay-docker-images/tree/master/liferay-standaloneYou need to: - build Liferay from git tag, commit, ... - zip it and put it `liferay-releases` dir - provide `env` file - run `build.sh`If that is what you are looking for, the steps above can be automated. Images can be put into separate docker repo (for example `liferay-snapshots`) and `liferayctl` can be made to work with those too. It's not too hard to do, just I'm still not sure it's worth the effort. 投票するためにはログインが必要です。 次として送信する: キャンセル
Milen Dyankov Manuel de la Peña 8年 前 IMHO it makes no sense to use Docker for this kind of thing. I agree that such script / command line tool may come handy. Basically it would need to grab the source code from GitHub, try compile it, deal with all the potential errors, make sure the target artifacts are created properly. At that point it could create a Docker container and put the result in, but honestly speaking I don't see why would one want to do that. Releasing images on Docker Hub that contain Liferay portal built from a particular commit would hardly be useful to anyone but the author IMHO. 投票するためにはログインが必要です。 次として送信する: キャンセル Manuel de la Peña Milen Dyankov 8年 前 What about a continuous-release process? Imagine having that tool to generate dockerfiles for engineers to tests/release an specific commit of Liferay? 投票するためにはログインが必要です。 次として送信する: キャンセル Milen Dyankov Manuel de la Peña 8年 前 - 編集済み So you can actually try it out using the docker image build process from https://github.com/milendyankov/liferay-docker-images/tree/master/liferay-standaloneYou need to: - build Liferay from git tag, commit, ... - zip it and put it `liferay-releases` dir - provide `env` file - run `build.sh`If that is what you are looking for, the steps above can be automated. Images can be put into separate docker repo (for example `liferay-snapshots`) and `liferayctl` can be made to work with those too. It's not too hard to do, just I'm still not sure it's worth the effort. 投票するためにはログインが必要です。 次として送信する: キャンセル
Manuel de la Peña Milen Dyankov 8年 前 What about a continuous-release process? Imagine having that tool to generate dockerfiles for engineers to tests/release an specific commit of Liferay? 投票するためにはログインが必要です。 次として送信する: キャンセル Milen Dyankov Manuel de la Peña 8年 前 - 編集済み So you can actually try it out using the docker image build process from https://github.com/milendyankov/liferay-docker-images/tree/master/liferay-standaloneYou need to: - build Liferay from git tag, commit, ... - zip it and put it `liferay-releases` dir - provide `env` file - run `build.sh`If that is what you are looking for, the steps above can be automated. Images can be put into separate docker repo (for example `liferay-snapshots`) and `liferayctl` can be made to work with those too. It's not too hard to do, just I'm still not sure it's worth the effort. 投票するためにはログインが必要です。 次として送信する: キャンセル
Milen Dyankov Manuel de la Peña 8年 前 - 編集済み So you can actually try it out using the docker image build process from https://github.com/milendyankov/liferay-docker-images/tree/master/liferay-standaloneYou need to: - build Liferay from git tag, commit, ... - zip it and put it `liferay-releases` dir - provide `env` file - run `build.sh`If that is what you are looking for, the steps above can be automated. Images can be put into separate docker repo (for example `liferay-snapshots`) and `liferayctl` can be made to work with those too. It's not too hard to do, just I'm still not sure it's worth the effort. 投票するためにはログインが必要です。 次として送信する: キャンセル
Christoph Rabel 8年 前 Very nice, tried it on the weekend, works like a charm.Feature request: Add a deploy option. It is very painful to cp files from the host to the container since only Docker 1.8 (released in August 2015) added a non-painful feature to do that.Also: EE images would be swell. Since one needs a trial key anyway, it shouldn't be a problem (or is it?) and it would be great for testing purposes. 投票するためにはログインが必要です。 次として送信する: キャンセル
Brendan Johan Lee 8年 前 Any chance you could make it expose the tomcat-folder as well? 投票するためにはログインが必要です。 次として送信する: キャンセル
Ritesh Patel 8年 前 We have automated complex Liferay deployments for our customers using Docker and Nirmata. Doing so has given our enterprise customers tremendous productivity boost as the developers dont have to wait for VMs to be setup to develop and test their features. Nirmata provides complete self service provisioning of application containers on any cloud - public or private. Here is a blog describing this:http://nirmata.com/2016/04/flexible-deployment-of-liferay-using-docker-and-nirmata-container-services/Disclaimer: I am a founder or Nirmata 投票するためにはログインが必要です。 次として送信する: キャンセル
Omar Mohsen 7年 前 Thank you for your guide, you have mentioned that the application server used is Tomcat, how can we bundle dockerize Liferay with JBoss?Thank youBest regards 投票するためにはログインが必要です。 次として送信する: キャンセル