Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Joel Anderson
authored and
Calvin Winkowski (Telnoratti)
committed
Sep 29, 2016
1 parent
9648b35
commit 82eb6b5
Showing
2 changed files
with
19 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,21 +29,34 @@ RUN yum install -y java-1.8.0-openjdk-devel unzip perl postgresql | |
#RUN alternatives --set java /usr/lib/jvm/jre-1.8.0-openjdk.x86_64/bin/java | ||
|
||
# Install glassfish | ||
RUN curl -L http://download.oracle.com/glassfish/4.1/release/glassfish-4.1.zip -o /glassfish-4.1.zip && cd /usr/local && unzip /glassfish-4.1.zip && rm /glassfish-4.1.zip | ||
RUN curl -L http://download.oracle.com/glassfish/4.1/release/glassfish-4.1.zip -o /glassfish-4.1.zip \ | ||
&& cd /usr/local \ | ||
&& unzip /glassfish-4.1.zip \ | ||
&& rm /glassfish-4.1.zip | ||
|
||
# Patch Weld for dataverse | ||
RUN rm /usr/local/glassfish4/glassfish/modules/weld-osgi-bundle.jar && cd /usr/local/glassfish4/glassfish/modules/ && curl -L http://central.maven.org/maven2/org/jboss/weld/weld-osgi-bundle/2.2.10.SP1/weld-osgi-bundle-2.2.10.SP1-glassfish4.jar -o weld-osgi-bundle-2.2.10.SP1-glassfish4.jar | ||
RUN rm /usr/local/glassfish4/glassfish/modules/weld-osgi-bundle.jar \ | ||
&& cd /usr/local/glassfish4/glassfish/modules/ \ | ||
&& curl -L http://central.maven.org/maven2/org/jboss/weld/weld-osgi-bundle/2.2.10.SP1/weld-osgi-bundle-2.2.10.SP1-glassfish4.jar -o weld-osgi-bundle-2.2.10.SP1-glassfish4.jar | ||
|
||
# Install dataverse, jq, jdbc driver, and jhove config | ||
RUN curl -L https://github.com/IQSS/dataverse/releases/download/v4.5/dvinstall.zip -o /dvinstall.zip && unzip dvinstall.zip && rm dvinstall.zip && curl -L http://stedolan.github.io/jq/download/linux64/jq -o /usr/bin/jq && chmod u+x /usr/bin/jq && cp /dvinstall/pgdriver/postgresql-9.1-902.jdbc4.jar /usr/local/glassfish4/glassfish/lib/ && cp /dvinstall/jhove.conf /usr/local/glassfish4/glassfish/domains/domain1/config | ||
RUN curl -L https://github.com/IQSS/dataverse/releases/download/v4.5/dvinstall.zip -o /dvinstall.zip \ | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
telnoratti
Contributor
|
||
&& unzip dvinstall.zip \ | ||
&& rm dvinstall.zip \ | ||
&& curl -L http://stedolan.github.io/jq/download/linux64/jq -o /usr/bin/jq \ | ||
&& chmod u+x /usr/bin/jq \ | ||
&& cp /dvinstall/pgdriver/postgresql-9.1-902.jdbc4.jar /usr/local/glassfish4/glassfish/lib/ \ | ||
&& cp /dvinstall/jhove.conf /usr/local/glassfish4/glassfish/domains/domain1/config | ||
|
||
# Specify volume for shared storage | ||
VOLUME /data/dvn:/usr/local/dvn/data | ||
|
||
# | ||
COPY run_dataverse.sh /run_dataverse.sh | ||
RUN chmod u+x run_dataverse.sh | ||
COPY install /dvinstall/install | ||
RUN chmod u+x /dvinstall/install | ||
#COPY install /dvinstall/install | ||
#RUN chmod u+x /dvinstall/install | ||
RUN sed -i -e "s/. \x22\x27 NOSUPERUSER CREATEDB CREATEROLE INHERIT LOGIN\x22;/. \x22\x27 NOSUPERUSER CREATEDB CREATEROLE INHERIT LOGIN; grant $CONFIG_DEFAULTS{\x27POSTGRES_USER\x27} to postgres\x22;/g" /dvinstall/install | ||
|
||
# | ||
CMD /run_dataverse.sh |
Rather than hardcoding "https://github.com/IQSS/dataverse/releases/download" as the place we download dvinstall.zip from, can we make this a parameter? As part of the Dataverse release process we upload "dvinstall.zip" manually after we tag a release. If we're going to use dataverse-aws to deploy pre-release code, we need to automate the building of "dvinstall.zip" and put it in a known location, right? Where? S3? I'm open to suggestions! 😄