1
0
mirror of https://github.com/bigchaindb/site.git synced 2024-11-01 07:45:41 +01:00
site/README.md

110 lines
3.1 KiB
Markdown
Raw Normal View History

2016-01-30 15:00:49 +01:00
# BigchainDB
2015-12-19 20:56:04 +01:00
2016-01-30 15:00:49 +01:00
> Landing page for BigchainDB
2015-12-19 20:56:04 +01:00
[![Build Status](https://travis-ci.com/ascribe/bigchain-website.svg?token=3psqw6c8KMDqfdGQ2x6d&branch=master)](https://travis-ci.com/ascribe/bigchain-website)
2016-03-03 17:56:56 +01:00
[Live](https://www.bigchaindb.com) | [Styleguide](https://www.bigchaindb.com/styleguide/) | [Beta](http://beta.bigchaindb.com) | [Gamma](http://gamma.bigchaindb.com)
2015-12-22 15:35:12 +01:00
2015-12-19 20:56:04 +01:00
## Development
You need to have the following tools installed on your development machine before moving on:
- [node.js](http://nodejs.org/) & [npm](https://npmjs.org/)
2016-11-11 00:15:26 +01:00
- (optional) use [Yarn](https://yarnpkg.com) instead of npm for faster dependency installations
- [Ruby](https://www.ruby-lang.org) (for sanity, install with [rvm](https://rvm.io/))
- [Bundler](http://bundler.io/)
### Install dependencies
Run the following command from the repository's root folder to install all dependencies.
```bash
npm i && bundle install
```
2016-11-11 00:15:26 +01:00
or
```bash
yarn && bundle install
```
### Development build
Spin up local dev server and livereloading watch task, reachable under [https://localhost:1337](https://localhost:1337):
```bash
gulp
```
2016-03-03 17:54:45 +01:00
## Continuous Delivery
The site gets built & deployed automatically via Travis under the following conditions:
2016-03-03 17:54:45 +01:00
- every push builds the site
- every push to the master branch initiates a live deployment
- every pull request initiates a beta deployment
2016-03-03 17:54:45 +01:00
## Manual Deployment
2016-01-08 12:00:57 +01:00
The site is hosted in an S3 bucket and gets deployed via a gulp task.
2016-01-08 12:00:57 +01:00
### 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:
```bash
2017-03-07 16:24:23 +01:00
AWS_PROFILE=bigchain gulp deploy --live
2016-01-08 12:00:57 +01:00
```
In case that you get authentication errors or need an alternative way to authenticate with AWS, check out the [AWS documentation](http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/node-configuring.html).
### Staging build & beta deployment
The staging build is essentially a full production build but it prevents search engine indexing & Google Analytics tracking.
2016-01-08 15:42:05 +01:00
```bash
# make sure your local npm packages & gems are up to date
npm update && bundle update
# make staging build in /_dist
gulp build --staging
2016-01-08 15:42:05 +01:00
# deploy contents of /_dist to beta
gulp deploy --beta
2016-01-08 15:42:05 +01:00
```
2017-03-07 16:24:23 +01:00
There's also a second beta deployment target called gamma under http://gamma.bigchaindb.com:
```bash
# build preventing search engine indexing & Google Analytics tracking
gulp build --staging
2017-03-07 16:24:23 +01:00
# deploy contents of /_dist to gamma
gulp deploy --gamma
```
2016-01-08 12:00:57 +01:00
### Production build & live deployment
```bash
# make sure your local npm packages & gems are up to date
npm update && bundle update
# make production build in /_dist
gulp build --production
2016-01-08 12:00:57 +01:00
# deploy contents of /_dist to live
gulp deploy --live
```