.gitignore

+cilogon_idp_selector.txt
+style.min.css
+style.min.css.map
+.DS_Store
\ No newline at end of file

.gitingore

-cilogon_idp_selector.txt
\ No newline at end of file

README.md

 # csusb jupyterhub custom templates
 
-GitLab page to test jupyterhub templates
+GitLab page to test CSUSB JupyterHub templates
 
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://gitlab.nrp-nautilus.io/youngsu_kim/csusb-jupyterhub-custom-templates.git
-git branch -M main
-git push -uf origin main
+## How we use it 
+We add the following into value.html.
 ```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://gitlab.nrp-nautilus.io/youngsu_kim/csusb-jupyterhub-custom-templates/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!).  Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+hub:
+  initContainers:
+    - name: git-clone-templates
+      image: alpine/git
+      args:
+        - clone
+        - --single-branch
+        - --branch=main
+        - --depth=1
+        - --
+        - https://gitlab.nrp-nautilus.io/youngsu_kim/csusb-jupyterhub-custom-templates.git
+        - /etc/jupyterhub/custom
+      securityContext:
+        runAsUser: 0
+      volumeMounts:
+        - name: custom-templates
+          mountPath: /etc/jupyterhub/custom
+  extraVolumes:
+    - name: custom-templates
+      emptyDir: {}
+  extraVolumeMounts:
+    - name: custom-templates
+      mountPath: /etc/jupyterhub/custom
+  extraConfig:
+    templates: |
+      c.JupyterHub.template_paths = ['/etc/jupyterhub/custom']
+```
\ No newline at end of file

cilogon_idp_selector.txt

-https://www.cilogon.org/oidc
-
-Optional Authorization Parameters
-CILogon's Authorization endpoint (https://cilogon.org/authorize) supports the following optional query parameters:
-
-idphint or selected_idp: A comma-separated list of url-encoded SAML EntityIDs and/or OIDC issuers to be shown to the user in the "Select an Identity Provider" selection list. This parameter complies with AARC-G049 - A specification for IdP hinting and allows a client to specify one or more Identity Providers to be shown to the user. For SAML-based IdPs (e.g., those registered by InCommon and eduGAIN), the entityID value is used. For OIDC-based IdPs (e.g., Google, GitHub, ORCID, Microsoft), the "iss" (issuer) value is used. See https://cilogon.org/idplist/ for the list of identity providers supported by CILogon. https://cilogon.org/include/idplist.xml is also available if more details on SAML entities are needed. If multiple IdPs are specified, the first IdP in the list is used as the initially displayed IdP for new visitors. Example showing Google, GitHub, ORCID, and UIUC: https://cilogon.org?idphint=https%3A%2F%2Faccounts.google.com,https%3A%2F%2Fgithub.com,https%3A%2F%2Forcid.org,urn%3Amace%3Aincommon%3Auiuc.edu
-
-initialidp: A url-encoded SAML EntityID or OIDC issuer to be initially selected in the "Select an Identity Provider" selection list. Typically, ORCID is shown as the default IdP for new users. The "initialidp" parameter allows a client to specify a different IdP to be initially selected. See "idphint" above for the format of the value of this parameter (i.e., entityID for InCommon/eduGAIN IdPs, "iss" (issuer) for OIDC-based IdPs). Notes: (1) The "idphint" parameter takes precedence over "initialidp" since the first IdP in the "idphint" list is used as the default IdP. (2) The "initialidp" parameter only affects new users since a user's previously selected IdP is saved in a browser cookie for future visits. Example showing ORCID as the default IdP: https://cilogon.org?initialidp=https%3A%2F%2Forcid.org
-
-skin: The name of the custom CILogon interface skin for your application. Skins are available for Essential and Full Service subscriptions. Contact help@cilogon.org to request a custom skin.
-
-See below for examples using curl, mod_auth_openidc, and OAuth for MyProxy.
-
-See also: Drupal, Globus, JupyterHub, Galaxy, and Open OnDemand
-
-{"EntityID":"https://idp.csusb.edu/idp/shibboleth","OrganizationName":"California State University, San Bernardino","DisplayName":"California State University, San Bernardino","RandS":true}
\ No newline at end of file

login.html

@@ -2,32 +2,59 @@
 {# https://github.com/jupyterhub/jupyterhub/issues/1385#issuecomment-738447175 #}
 {% extends "templates/login.html" %}
 
-{% set announcement = 'test announcement message' %}
+{% set announcement = 'We are testing customized style / The server works the same way as before' %}
 {% set csusb_hub_title = 'Welcome to Cal State San Bernardino JupyterHub' %}
-{% set csusb_cilogon = 'The following login process uses CSUSB\'s DUO login system' %}
+{% set csusb_cilogon = 'The login process (the orange button) uses CSUSB\'s DUO system' %}
 
 {% block login %}
-<div class="container text-center csusb">
-    <h1>{{ csusb_hub_title  }}</h1>
-    <h4>
-      <p>{{ csusb_cilogon | safe }}</p>
-      <p>For more information about the login system and HPC at CSUSB, please visit <a href="https://www.csusb.edu/high-performance-computing" target="_blank">CSUSB High Performance Computing Initiative</a></p>
-    </h4>
+<div class="container text-center">
+    <h2>{{ csusb_hub_title  }}</h2>
+    <h5>
+        <p>{{ csusb_cilogon | safe }}</p>
+        {# <p>Visit <a href="https://www.csusb.edu/high-performance-computing" target="_blank">CSUSB High Performance Computing Initiative</a> for more information about CSUSB HPCI 
+        </p> #}
+    </h5>
+</div>
+<p> &nbsp </p>
+<p> &nbsp </p>
+<p> &nbsp </p>
 {{ super() }}
+<p> &nbsp </p>
+<div id="login-cilogon-info" class="service-login">
+    <h5>      
+    <p>Be sure to choose <ins>California State University San Bernardino</ins> on the next page instead of <del>ORCID</del>
+    </h5>
+</div>
+<div class="container text-center">
+<details>
+    <summary>Click here for more details</summary>
+    <img id="idp_selector_info" style="width: 70%" src="{{ static_url("select_idp_cilogon.png") }}" alt="CILogon-CSUSB-Select">
+</details>
 </div>
 {% endblock %}
 
 {% block stylesheet %}
 {{ super() }}
 <style>
-#login-main {
-    margin-top: 5%;
+#login-main{
+    margin-top: 1%;
     height: 100%;
 }
-
-<!-- #login-main form {
-    vertical-align: top;
-} -->
+#login-cilogon-info{
+    text-align: center;
+    display: table;
+    vertical-align: middle;
+    margin: 1% auto auto auto;
+    padding-left: 0%;
+    width: 380px;
+}
+#idp_selector_info {
+    max-width:100%;
+    height:auto;
+    max-height:100%;
+}
+p.extra-space {
+    line-height: 0.7;
+}
 </style>
-{% endblock %}
-
+{% endblock %}
\ No newline at end of file

page.html

+{% extends "templates/page.html" %}
+
+{% block stylesheet %}
+{{ super() }}
+<style>
+.footer-bottom {
+    position: auto;
+    bottom: 0px;
+    text-align: center;
+    width: 100%;
+    z-index: -1;
+}
+</style>
+{% endblock %}
+
+{% block footer %}
+<p> &nbsp <br> &nbsp </p>
+<p> &nbsp <br> &nbsp </p>
+<div class="footer-bottom">
+    <hr style="width:30%; margin-bottom: 5px;">
+    <p style="font-size: 80%">This JupyterHub is provided by the <a href="https://www.csusb.edu/high-performance-computing" target="_blank">High Performance Computing Initiative </a><br/> 
+    at California State Univeristy San Bernardino
+    </p></div>
+{% endblock %}
+

spawn_pending.html

 {% extends "templates/spawn_pending.html" %}
-
 {% block message %}
-{{ super() }}
-<p>This step may take several minutes.</p>
-<p>Most of the time, the issue or delay is related to the server (upgrading or temporary maintanance).</p>
-<p>For errors lasting for an extended period of time, please contact one of the <a href="https://www.csusb.edu/high-performance-computing#team" target="_blank">CSUSB HPCI team members</a>.</p>
-<br>
-{% for scope in allowed_scopes %}
-    {{ scope }}
-{% endfor %}
-<br>
-{% endblock %}
+{# {{ super() }} #}
+<p>Your server is starting up and it may take several minutes</p>
+<p>Most issues are related to the server upgrade or temporary maintanance</p>
+<p>If it does not start for an extended period of time, <br> please contact one of the <a href="https://www.csusb.edu/high-performance-computing#team" target="_blank">CSUSB HPCI team members</a></p>
+<p> &nbsp <br> &nbsp </p>
+{% endblock %}
\ No newline at end of file