1
0
mirror of https://github.com/bigchaindb/site.git synced 2024-10-31 23:35:38 +01:00
🦁 The fabulous cat of blockchain websites https://www.bigchaindb.com
Go to file
2017-04-11 12:58:51 +02:00
_aws document AWS bucket policy 2017-03-01 14:55:11 +01:00
_ci Refactor for gulp 4 (#107) 2017-03-22 16:34:05 +01:00
_src build quick fix: use Jekyll's native slug variable 2017-04-11 11:14:24 +02:00
docs Updated front page & restyled menu & happy little things (#79) 2016-11-14 11:59:16 +01:00
_config.yml updated branding (#99) 2017-04-10 17:14:35 +02:00
.babelrc Build improvements (#108) 2017-03-28 17:55:40 +02:00
.editorconfig finalized starting point 2015-12-20 05:22:45 +01:00
.gitignore build tweaks 2017-03-04 23:15:46 +01:00
.travis.yml hero cleanup (#101) 2017-03-02 14:27:08 +01:00
favicon.ico Update assets 2017-02-07 23:42:23 +01:00
Gemfile lock jekyll-sitemap version for now 2017-04-11 11:57:14 +02:00
gulpfile.babel.js just another build fix 2017-04-11 12:58:51 +02:00
package.json Notify search engines upon every live deployment (#113) 2017-04-11 12:43:45 +02:00
README.md prevent search engine indexing of beta & gamma 2017-03-20 16:19:53 +01:00

BigchainDB

Landing page for BigchainDB

Build Status

Live | Styleguide | Beta | Gamma

Development

You need to have the following tools installed on your development machine before moving on:

Install dependencies

Run the following command from the repository's root folder to install all dependencies.

npm i && bundle install

or

yarn && bundle install

Development build

Spin up local dev server and livereloading watch task, reachable under https://localhost:1337:

gulp

Continuous Delivery

The site gets built & deployed automatically via Travis under the following conditions:

  • every push builds the site
  • every push to the master branch initiates a live deployment
  • every pull request initiates a beta deployment

Manual Deployment

The site is hosted in an S3 bucket and gets deployed via a gulp task.

Prerequisite: Authentication

To deploy the site, you must authenticate yourself against the AWS API with your AWS credentials. Get your AWS access key and secret and add them to ~/.aws/credentials:

[default]
aws_access_key_id = <YOUR_ACCESS_KEY_ID>
aws_secret_access_key = <YOUR_SECRET_ACCESS_KEY>

This is all that is needed to authenticate with AWS if you've setup your credentials as the default profile.

If you've set them up as another profile, say [bigchain] you can grab those credentials by using the AWS_PROFILE variable like so:

AWS_PROFILE=bigchain gulp deploy --live

In case that you get authentication errors or need an alternative way to authenticate with AWS, check out the AWS documentation.

Staging build & beta deployment

The staging build is essentially a full production build but it prevents search engine indexing & Google Analytics tracking.

# make sure your local npm packages & gems are up to date
npm update && bundle update

# make staging build in /_dist
gulp build --staging

# deploy contents of /_dist to beta
gulp deploy --beta

There's also a second beta deployment target called gamma under http://gamma.bigchaindb.com:

# build preventing search engine indexing & Google Analytics tracking
gulp build --staging

# deploy contents of /_dist to gamma
gulp deploy --gamma

Production build & live deployment

# make sure your local npm packages & gems are up to date
npm update && bundle update

# make production build in /_dist
gulp build --production

# deploy contents of /_dist to live
gulp deploy --live