The thalia working environment is split into three parts: development, testing, and production.
Development: thalia-dev.mit.edu
The development server is used by developers to deploy and test new code before
Our CI system will build the code from SCM every night and deploy the binary the development server if the build and smoke test are successful.
On thalia-dev, the value in the webserviceclient.properties file for alfresco is: http://thalia-dev.mit.edu:8180/alfresco/api
Test: thalia-test.mit.edu
thalia2, thalia11 host the IME
thalia3, thalia12 host alfresco (currently only thalia3 is in use)
thalia4, thalia13 host the mysql db
On thalia-test, the value in the webserviceclient.properties file for alfresco is: http://isda-thalia12.mit.edu:8080/alfresco/api
The test server is used by QA testers and CAT users. The code on the test server is more stable than that on the development server. During the two week QA process, we will release a new build to QA every three days or whenever important bug(s) are fixed. A release note will be sent to QA along with the new release containing a list of issues resolved in this release.
We will give our final release candidate to QA three business days before the actual release date. Currently, we are releasing on Monday night every 4 weeks.
Production: thalia.mit.edu
thalia5, thalia8 host the IME
thalia6, thalia9 host alfresco (currently only thalia6 is in use)
thalia7, talia10 host the mysql db (currently only thalia7 is in use)
On production, the value in the webserviceclient.properties file for alfresco is: http://isda-thalia6.mit.edu:8080/alfresco/api
The production servers have their own sets of passwords to protect the production environment: the tomcat manager password on thalia5 and 8, the alfresco admin user's password and regular user's password. Only root instances are allowed in .k5login files.