singularityware · DrDaveD · Apr 19, 2018 · Apr 19, 2018
diff --git a/CNAME b/CNAME
diff --git a/_data/demo.js b/_data/demo.js
@@ -15603,7 +15603,7 @@
     ],
     [
       3e-05,
-      "website: http://singularity.lbl.gov/"
+      "website: http://singularityware.github.io/"
     ],
     [
       4.8e-05,
@@ -15827,7 +15827,7 @@
     ],
     [
       2.7e-05,
-      "    http://singularity.lbl.gov/"
+      "    http://singularityware.github.io/"
     ],
     [
       2.7e-05,
@@ -16255,7 +16255,7 @@
     ],
     [
       3.7e-05,
-      "    http://singularity.lbl.gov/"
+      "    http://singularityware.github.io/"
     ],
     [
       3.8e-05,

diff --git a/_includes/metadata.html b/_includes/metadata.html
@@ -5,7 +5,7 @@
 {% if page.title %}
 <meta name="name" content="{{ page.title }}">
 {% endif %}
-<meta name="thumbnail" content="http://singularity.lbl.gov/images/logo/logo.svg">
+<meta name="thumbnail" content="http://singularityware.github.io/images/logo/logo.svg">
 {% if page.targz %}
 <meta name="file" content="{{ site.repo }}/archive/{{ page.targz }}">
 {% endif %}

diff --git a/_posts/presentations/2016-09-30-rpc-podcast.md b/_posts/presentations/2016-09-30-rpc-podcast.md
@@ -6,6 +6,6 @@ permalink: 2016-singularity-featured-rce-podcast
 
 The RCE podcast does a special on <a href="http://www.rce-cast.com/Podcast/rce-106-singularity.html" target="_blank">Singularity</a>
 
-<p><a href="http://www.rce-cast.com/about/about-the-hosts.html#brockp">Brock Palen</a> and <a href="http://www.rce-cast.com/about/about-the-hosts.html#jsquyres">Jeff Squyres</a> speak with Gregory Kurtzer about <a href="/singularity.lbl.gov/">Singularity</a> a container solution for HPC and research environments.  Singularity allows a non-privileged user to "swap out" the operating system on the host for one they control. So if the host system is running RHEL6 but your application runs in Ubuntu, you can create an Ubuntu image, install your applications into that image, copy the image to another host, and run your application on that host in it's native Ubuntu environment.</p>
+<p><a href="http://www.rce-cast.com/about/about-the-hosts.html#brockp">Brock Palen</a> and <a href="http://www.rce-cast.com/about/about-the-hosts.html#jsquyres">Jeff Squyres</a> speak with Gregory Kurtzer about <a href="/singularityware.github.io/">Singularity</a> a container solution for HPC and research environments.  Singularity allows a non-privileged user to "swap out" the operating system on the host for one they control. So if the host system is running RHEL6 but your application runs in Ubuntu, you can create an Ubuntu image, install your applications into that image, copy the image to another host, and run your application on that host in it's native Ubuntu environment.</p>
 
 {% include links.html %}
diff --git a/_posts/recipes/2016-09-23-build-rhel-host.md b/_posts/recipes/2016-09-23-build-rhel-host.md
@@ -6,7 +6,7 @@ permalink: building-ubuntu-rhel-host
 
 This recipe describes how to build an Ubuntu image using Singularity on a RHEL compatible host. 
 
-**NOTE: this tutorial is intended for [Singularity release 2.1.2](http://singularity.lbl.gov/release-2-1-2), and reflects standards for that version.**
+**NOTE: this tutorial is intended for [Singularity release 2.1.2](http://singularityware.github.io/release-2-1-2), and reflects standards for that version.**
 
 In order to do this, you will need to first install the 'debootstrap' package onto your host. Then, you will create a definition file that will describe how to build your Ubuntu image. Finally, you will build the image using the Singularity commands 'create' and `bootstrap`.
 

diff --git a/_posts/recipes/2016-12-27-build-ubuntu-host.md b/_posts/recipes/2016-12-27-build-ubuntu-host.md
@@ -9,7 +9,7 @@ This recipe describes how to build a CentOS image using Singularity, with specia
 {% include toc.html %}
 
 
-**NOTE: this tutorial is intended for [Singularity release 2.2](http://singularity.lbl.gov/release-2-2), and reflects standards for that version.**
+**NOTE: this tutorial is intended for [Singularity release 2.2](http://singularityware.github.io/release-2-2), and reflects standards for that version.**
 
 ## The Problem
 In theory, an Ubuntu host can create/bootstrap a CentOS image by installing the `yum` package, which is a front-end controller for [RPM](https://en.wikipedia.org/wiki/RPM_Package_Manager).  In order for this to work on Ubuntu, a software called [Berkeley DB](https://en.wikipedia.org/wiki/Berkeley_DB) must be identical in version to the version expected by `yum`. Unfortunately, these two versions tend to be different, and this situation poses a difficult challenge for Singularity to deal with. A perfectly working `centos.def` file that can bootstrap a CentOS image from a RHEL-compatible host will not work when executed on Ubuntu, yielding the following error:

diff --git a/_posts/recipes/2017-01-26-singularity-hub-tutorial.md b/_posts/recipes/2017-01-26-singularity-hub-tutorial.md
@@ -30,7 +30,7 @@ The easiest thing to do is to install Singularity on your local workstation:
     sudo make install
 ```
 
-If you are using a Mac, or just need a virtual machine, then you will want to follow the instructions <a href="http://singularity.lbl.gov/install-mac" target="_blank">here</a>. Basically, you need to install vagrant, virtual box, and then do this:
+If you are using a Mac, or just need a virtual machine, then you will want to follow the instructions <a href="http://singularityware.github.io/install-mac" target="_blank">here</a>. Basically, you need to install vagrant, virtual box, and then do this:
 
 ```bash
 vagrant init ubuntu/trusty64

diff --git a/assets/asciicast/install-singularity.js b/assets/asciicast/install-singularity.js
@@ -8766,7 +8766,7 @@
     ],
     [
       2.6e-05,
-      "via a tar pipe\r\n    import        Import/add container contents via a tar pipe\r\n    mount         Mount a Singularity container image\r\n\r\nCONTAINER REGISTRY COMMANDS:\r\n    pull          pull a Singularity Hub container\r\n\r\n\r\nFor any additional help or support visit the Singularity\r\nwebsite: http://singularity.lbl.gov/\r\n\r\n"
+      "via a tar pipe\r\n    import        Import/add container contents via a tar pipe\r\n    mount         Mount a Singularity container image\r\n\r\nCONTAINER REGISTRY COMMANDS:\r\n    pull          pull a Singularity Hub container\r\n\r\n\r\nFor any additional help or support visit the Singularity\r\nwebsite: http://singularityware.github.io/\r\n\r\n"
     ],
     [
       0.000859,
@@ -9035,4 +9035,4 @@
     "TERM": "xterm-256color",
     "SHELL": "/bin/bash"
   }
-}
+}
diff --git a/assets/asciicast/shub-pull.json b/assets/asciicast/shub-pull.json
@@ -3550,7 +3550,7 @@
     ],
     [
       3.3e-05,
-      "via a tar pipe\r\n    import        Import/add container contents via a tar pipe\r\n    mount         Mount a Singularity container image\r\n\r\nCONTAINER REGISTRY COMMANDS:\r\n    pull          pull a Singularity Hub container\r\n\r\n\r\nFor any additional help or support visit the Singularity\r\nwebsite: http://singularity.lbl.gov/\r\n\r\n"
+      "via a tar pipe\r\n    import        Import/add container contents via a tar pipe\r\n    mount         Mount a Singularity container image\r\n\r\nCONTAINER REGISTRY COMMANDS:\r\n    pull          pull a Singularity Hub container\r\n\r\n\r\nFor any additional help or support visit the Singularity\r\nwebsite: http://singularityware.github.io/\r\n\r\n"
     ],
     [
       0.001269,
@@ -4059,4 +4059,4 @@
   ],
   "title": null,
   "version": 1
-}
+}
diff --git a/circle_urls.py b/circle_urls.py
@@ -19,6 +19,6 @@
         content = filey.read()
     for search_name in search_names:
         content = content.replace('%s"' %(search_name),'%s.html"' %(search_name))
-    content = content.replace('/images/logo/logo.svg','http://singularity.lbl.gov/images/logo/logo.svg')
+    content = content.replace('/images/logo/logo.svg','http://singularityware.github.io/images/logo/logo.svg')
     with open(html_file,'w') as filey:
         filey.write(content)
diff --git a/pages/docs/install/install-request.md b/pages/docs/install/install-request.md
@@ -23,7 +23,7 @@ Installation of a new software is no small feat for a shared cluster resource. W
 #### Security
 
  - [Administrator Control](https://github.com/singularityware/singularity/blob/master/etc/singularity.conf.in): The configuration file template is the best source to learn about the configuration options that are under the administrator's control.
- - [Security Overview](http://singularity.lbl.gov/docs-security) discusses common security concerns
+ - [Security Overview](http://singularityware.github.io/docs-security) discusses common security concerns
 
 #### Presentations
 
@@ -36,12 +36,12 @@ Putting all of the above together, a request might look like the following:
 ```
 Dear Research Computing,
 
-We are interested in having an installation of the Singularity software (https://singularityware.github.io) installed on our cluster. Singularity containers will allow us to build encapsulated environments, meaning that our work is reproducible and we are empowered to choose all dependencies including libraries, operating system, and custom software. Singularity is already installed on over 50 centers internationally (http://singularity.lbl.gov/citation-registration) including TACC, NIH, and several National Labs, Universities, Hospitals. Importantly, it has a vibrant team of developers, scientists, and HPC administrators that invest heavily in the security and development of the software, and are quick to respond to the needs of the community. To help learn more about Singularity, I thought these items might be of interest:
+We are interested in having an installation of the Singularity software (https://singularityware.github.io) installed on our cluster. Singularity containers will allow us to build encapsulated environments, meaning that our work is reproducible and we are empowered to choose all dependencies including libraries, operating system, and custom software. Singularity is already installed on over 50 centers internationally (http://singularityware.github.io/citation-registration) including TACC, NIH, and several National Labs, Universities, Hospitals. Importantly, it has a vibrant team of developers, scientists, and HPC administrators that invest heavily in the security and development of the software, and are quick to respond to the needs of the community. To help learn more about Singularity, I thought these items might be of interest:
 
-   - Security: A discussion of security concerns is discussed at http://singularity.lbl.gov/docs-security
-   - Installation: http://singularity.lbl.gov/admin-guide
+   - Security: A discussion of security concerns is discussed at http://singularityware.github.io/docs-security
+   - Installation: http://singularityware.github.io/admin-guide
 
-If you have questions about any of the above, you can email the list ([email protected]) or join the slack channel (singularity-container.slack.com) to get a human response. I can do my best to facilitate this interaction if help is needed. Thank you kindly for considering this request!
+If you have questions about any of the above, you can email the list (singularityware.github.io) or join the slack channel (singularity-container.slack.com) to get a human response. I can do my best to facilitate this interaction if help is needed. Thank you kindly for considering this request!
 
 Best,
 

diff --git a/pages/docs/user-docs/docs-quickstart.md b/pages/docs/user-docs/docs-quickstart.md
@@ -70,7 +70,7 @@ CONTAINER USAGE OPTIONS:
     see singularity help <command>
 
 For any additional help or support visit the Singularity
-website: http://singularity.lbl.gov/
+website: http://singularityware.github.io/
 ```
 Singularity uses positional syntax.  Global options follow the `singularity` invocation  and affect the way that Singularity runs any command.  Then commands are passed followed by their options.  
 

diff --git a/pages/docs/user-docs/docs-usage.md b/pages/docs/user-docs/docs-usage.md
@@ -71,7 +71,7 @@ EXAMPLES:
 For additional help, please visit our public documentation pages which are
 found at:
 
-    http://singularity.lbl.gov/
+    http://singularityware.github.io/
 ```
 
 ## Commands Usage
@@ -116,7 +116,7 @@ CONTAINER USAGE OPTIONS:
     see singularity help <command>
 
 For any additional help or support visit the Singularity
-website: http://singularity.lbl.gov/
+website: http://singularityware.github.io/
 ```
 
 ## Support

diff --git a/pages/docs/user-docs/user-guide.md b/pages/docs/user-docs/user-guide.md
@@ -148,7 +148,7 @@ All of the above steps take approximately 15-25 thousandths of a second to run,
 ## The Singularity Usage Workflow
 The security model of Singularity (as described above, ["*A user inside a Singularity container is the same user as outside the container*"](user-guide#security-and-privilege-escalation)) defines the Singularity workflow. There are generally two groups of actions you must implement on a container; *management* (building your container) and *usage*.
 
-In many circumstances building containers require root administrative privileges just like these actions would require on any system, container, or virtual machine. This means that a user must have access to a system on which they have root privileges. This could be a server, workstation, a laptop, virtual machine, or even a cloud instance. If you are using OS X or Windows on your laptop, it is recommended to setup Vagrant, and run Singularity from there (there are recipes for this which can be found at http://singularity.lbl.gov/). Once you have Singularity installed on your endpoint of choice, this is where you will do the bulk of your container development.  
+In many circumstances building containers require root administrative privileges just like these actions would require on any system, container, or virtual machine. This means that a user must have access to a system on which they have root privileges. This could be a server, workstation, a laptop, virtual machine, or even a cloud instance. If you are using OS X or Windows on your laptop, it is recommended to setup Vagrant, and run Singularity from there (there are recipes for this which can be found at http://singularityware.github.io/). Once you have Singularity installed on your endpoint of choice, this is where you will do the bulk of your container development.  
 This workflow can be described visually as follows:
 
 <a href="/assets/img/diagram/singularity-2.4-flow.png" target="_blank" class="no-after">