🦁 The fabulous cat of blockchain websites https://www.bigchaindb.com
Go to file
Matthias Kretschmann 07e873b2eb update S3 bucket names for deployment 2016-01-30 15:03:33 +01:00
_src update name & urls 2016-01-30 15:00:49 +01:00
docs document css unit usage 2015-12-21 14:15:41 +01:00
.editorconfig finalized starting point 2015-12-20 05:22:45 +01:00
.gitignore ignore awspublish cache files 2016-01-08 15:37:40 +01:00
Gemfile generic page layout, 404 page, generate sitemap 2015-12-22 13:41:58 +01:00
README.md more urls in readme 2016-01-30 15:02:29 +01:00
_config.yml update name & urls 2016-01-30 15:00:49 +01:00
gulpfile.js update S3 bucket names for deployment 2016-01-30 15:03:33 +01:00
package.json 0.1.0 2016-01-30 14:56:26 +01:00

README.md

BigchainDB

Landing page for BigchainDB

Live | Beta | Styleguide

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

Development build

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

gulp

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.

Production build & beta 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 beta
gulp deploy:beta

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