vbatts/quay
Archived
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Merge pull request #3276 from KeyboardNerd/about_page

Browse source 
Add dependent packages in about page
This commit is contained in:
Sida Chen 2018-10-30 12:57:18 -04:00 committed by GitHub
commit 203bffbbbb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 3904 additions and 4281 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
Dockerfile
View file

@ -112,6 +112,7 @@ RUN cat requirements.txt | grep -v "^-e" | awk -F'==' '{print $1}' | xargs venv/
rm pipinfo.txt
# JS compile
COPY bill-of-materials.json bill-of-materials.json
COPY static static
RUN yarn build \
&& jpegoptim static/img/**/*.jpg \

8132
bill-of-materials.json
View file

File diff suppressed because it is too large Load diff

8
static/js/pages/about.js
View file

@ -1,11 +1,17 @@
import billOfMaterials from "../../../bill-of-materials.json"
(function() {
/**
* About page.
*/
angular.module('quayPages').config(['pages', function(pages) {
pages.create('about', 'about.html', null, {
pages.create('about', 'about.html', AboutCtrl, {
'title': 'About Us',
'description': 'About Us'
});
}]);
function AboutCtrl($scope){
$scope.billOfMaterials = billOfMaterials
}
}());

44
static/partials/about.html
View file

@ -40,9 +40,45 @@
<div class="row">
<div class="col-sm-12">
<h3>Our Story</h3>
<p>Quay was originally created out of necessity when we wanted to use Docker containers with our original IDE product. We were using Docker containers to host and isolate server processes invoked on behalf of our users and often running their code. We started by building the Docker image dynamically whenever we spun up a new host node. The image was monolithic. It was too large, took too long to build, and was hard to manage conflicts. It was everything that Docker wasn't supposed to be. When we decided to split it up into pre-built images and host them somewhere, we noticed that there wasn't a good place to host images securely. Determined to scratch our own itch, we built Quay, and officially launched it as an aside in our presentation to the <a href="http://www.meetup.com/Docker-NewYorkCity/events/142142762/">Docker New York City Meetup</a> on October 2nd, 2013.</p>
<p>After launch, our customers demanded that Quay become our main focus. They rely on us to make sure they can store and distribute their container images, and we understand that solemn responsibility. Our customers have been fantastic with giving us great feedback and suggestions.</p>
<p>In August, 2014, Quay joined <a href="https://coreos.com">CoreOS</a> to provide registry support for the enterprise. As ever, we are working as hard as we can to deliver on the promise and execute our vision of what a top notch container registry should be.
<p>Quay was originally created out of necessity when we wanted to use Docker containers with our original IDE
product. We were using Docker containers to host and isolate server processes invoked on behalf of our users
and often running their code. We started by building the Docker image dynamically whenever we spun up a new
host node. The image was monolithic. It was too large, took too long to build, and was hard to manage
conflicts. It was everything that Docker wasn't supposed to be. When we decided to split it up into pre-built
images and host them somewhere, we noticed that there wasn't a good place to host images securely. Determined
to scratch our own itch, we built Quay, and officially launched it as an aside in our presentation to the <a
href="http://www.meetup.com/Docker-NewYorkCity/events/142142762/">Docker New York City Meetup</a> on October
2nd, 2013.</p>
<p>After launch, our customers demanded that Quay become our main focus. They rely on us to make sure they can
store and distribute their container images, and we understand that solemn responsibility. Our customers have
been fantastic with giving us great feedback and suggestions.</p>
<p>In August, 2014, Quay joined <a href="https://coreos.com">CoreOS</a> to provide registry support for the
enterprise. As ever, we are working as hard as we can to deliver on the promise and execute our vision of what
a top notch container registry should be.
</div>
</div>
</div>
<div class="row">
<div class="col-sm-12">
<h3>Packages and Projects used</h3>
<table class="co-table co-fixed-table" style="margin-top: 20px;">
<thead>
<tr>
<td>Project Name</td>
<td>Project License</td>
<td>Type</td>
</tr>
</thead>
</table>
<div style="height: 300px; overflow-y: auto;">
<table class="co-table co-fixed-table">
<tr ng-repeat="project in billOfMaterials">
<td>{{project.project}}</td>
<td>{{project.license}}</td>
<td>{{project.format}}</td>
</tr>
</table>
</div>
</div>
</div>
</div>