Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
4 contributors

Users who have contributed to this file

@martinmr @gpahal @danielmai @Aelbannan
61 lines (44 sloc) 1.68 KB

Building and running ratel

Local development

# Build ratel
# Note that ratel needs to be in your GOPATH for this to work. Otherwise,
# main.go will not be able to import the server code correctly.
./scripts/build.prod.sh

# You may need to manually install go-bindata using the following command
go get github.com/jteeuwen/go-bindata/go-bindata

# Start the ratel server.
./build/ratel
# Visit localhost:8000 to use ratel.

# If you want client hot-reloading, run:
./scripts/start.sh
# Visit localhost:3000 to use hot-reloaded ratel.

Production build

./scripts/build.prod.sh

Serving over HTTPS

By default Ratel will serve the UI over HTTP. You can switch to serve the UI with only HTTPS by setting the -tls_crt and -tls_key flags with the certificate and key files used to establish the HTTPS connection.

./build/ratel -tls_crt example.crt -tls_key example.key

Publishing to AWS S3

Instructions to publish ratel assets (JS and CSS files) to AWS S3 bucket.

Before publishing

  • Install the AWS CLI - see docs.
  • Get access to AWS credentials and configure the AWS CLI - see docs.

Publishing

# Builds the Go server and JS and CSS client files. Also uploads the JS and CSS
# files to AWS S3. Optionally, you can also pass a version as `--version 1.0.0`.
./scripts/build.prod.sh --upload

After this you can invalidate the AWS Cloudfront cache (see docs) so that users see the latest code upon refreshing.

You can’t perform that action at this time.