...
Jasig
...
has
...
an
...
Amazon
...
EC2
...
instance
...
that
...
is
...
integrated
...
with
...
our
...
Bamboo
...
build
...
server.
...
This
...
EC2
...
instance
...
is
...
designated
...
for
...
live
...
nightly
...
builds
...
and
...
curated
...
demos
...
of
...
Jasig
...
projects.
...
If
...
your
...
project
...
is
...
interested
...
in
...
getting
...
a
...
site
...
setup
...
please
...
follow
...
the
...
instructions
...
below
...
and
...
then
...
pass
...
the
...
information
...
on
...
to infrastructure@lists.ja-sig.org infrastructure@apereo.org
Live Site Build Requirements
To get a live build setup for a project a build script is required that does the following from an unmodified checkout from the Jasig SVN server:
- Stops the existing live site if it is deployed and running
- Creates a clean deployment of the project to an application server that Apache can be directed do either via mod_proxy or mod_proxy_ajp
- Starts the application server
For an example of such a script the uPortal assembly ant script can be used: https://source.
...
jasig.org/uPortal/trunk/assembly/build.xml
For the uPortal live nightly build ant live-nightly-stop clean live-nightly live-nightly-start is run, which stops the tomcat instance if it is deployed, cleans all previously built content, builds a new live-nightly site and then starts tomcat. The live-nightly target includes logic that downloads and customizes a Tomcat instance.
Requesting a new Live Site
Please put together a document detailing your choices at each step of this process
Ports and IPs to Use
The following port and IP picking rules MUST be followed to ensure we can have multiple sites hosted on one machine without running into conflicts. The VV in the notes corresponds to the version of the project the site is for
- uPortal Live nightly builds
- 82VV - hsql
- 81VV - tomcat ajp
- 83VV - tomcat http
- 80VV - tomcat shutdown
- 127.0.8.VV
...
- -
...
- localhost
...
- mapping
...
- port
...
- uPortal
...
- Live
...
- demos
...
- 92VV
...
- -
...
- hsql
...
- 91VV
...
- -
...
- tomcat
...
- ajp
- 93VV - tomcat http
- 90VV - tomcat shutdown
- 127.0.9.VV
...
- -
...
- localhost
...
- mapping
...
- port
...
- Other
...
- Projects
...
- Add
...
- a
...
- project
...
- specific
...
- section
...
- here
...
- that
...
- uses
...
- a
...
- unique
...
- port
...
- prefix.
...
Determine
...
the
...
site
...
name
...
The
...
following
...
site
...
name
...
guidelines
...
have
...
been
...
established.
...
For
...
a
...
new
...
project
...
please
...
extend
...
these
...
guidelines
...
to
...
match
...
and
...
document
...
it
...
here.
...
- uPortal
...
- Nightly
...
- live
...
- build
...
- -
...
- upVV-nightly.jasig.org
...
- uPortal
...
- Live
...
- Demo
...
- -
...
- upVV-demo.jasig.org
...
Create
...
Config
...
Files
...
...
- and
...
- customize
...
- it
...
- to
...
- match
...
- the
...
- new
...
- site.
...
- ServerName:
...
up40-nightly.jasig.org
...
- to
...
upVV-nightly.jasig.org
...
- The subdirectory after ${APACHE_LOG_DIR}
...
- in
...
- the
...
- two
...
- error
...
- and
...
- custom
...
- log
...
- lines
...
- (there
...
- are
...
- 4
...
- places
...
- to
...
- make
...
- the
...
- change):
...
${APACHE_LOG_DIR}/up40-nightly/
...
- to
...
${APACHE_LOG_DIR}/upVV-nightly/
...
- The proxy pass/reverse
...
- host
...
- and
...
- IP
...
- based:
...
up40-nightly.local:8140
...
- to
...
upVV-nightly.local:81VV
...
Update hosts file
Look at hosts_additionwhich is appended to the servers hosts file and determine the two additional lines needed for the new site.
No Format 127.0.8.VV upVV-nightly.local 127.0.8.VV upVV-nightly.jasig.org
...