UB Containers as a Service (UB CaaS, formerly WebApps ) is a webhosting service providing access to various programming languages and databases. It is often used in conjunction with a UB Content Management System site to add additional functionality.
A Virtual Private Network may be required for access. See below.
UB Web developers maintaining official UB websites may request an account through the UBIT Help Center. Use of UB CaaS is subject to our terms of service.
Submit a request to your departmental IT support to have the new contributor's UBITName added to the project's AD Group.
UB CaaS is comprised of two parts: OpenShift and UB Version Control System.
Use OpenShift to create "pods" (or "Linux containers") that will host your Web applications. Think of each one as your very own server, with file systems and logs that only you can access.
This is where you keep your code. A "version control system" records changes to a file or set of files over time so that you can recall specific versions later. We highly recommend that all developers use UB's Version Control System (UBVCS) to manage their application code. UBVCS is powered by git, a distributed revision control system aimed at speed, data integrity, and support for distributed, non-linear workflows.
No. UB CaaS is a way to extend the UBCMS's functionality. Applications you create in UB CaaS can be included in UBCMS Web pages through the External Embed or HTML Snippet components.
Yes. We encourage anyone doing active development of their site to have both a live/production pod and a development pod.
Sorry, direct (S)FTP access to the containers is not available. However, a CLI utility is available for Windows, Linux and Mac that provides more advanced features such as rsh and rsync.
We recommend using a MySQL central database. You may request one through the UBIT Help Center Online.
The following available CaaS database pods are NOT backed up or currently administered, and are therefore NOT recommended for production environments:
Consider joining the CaaS Listserv: firstname.lastname@example.org