1
0
This repository has been archived on 2023-12-27. You can view files and clone it, but cannot push or open issues or pull requests.
Tony Grosinger 643d4121c0 Add Access-Control-Allow-Origin header middleware
Fixes #3. Use the "Origin" header to specify what domain the request is
coming from. If that domain is approved
(https?://(localhost|dotdeploy.works)) it will include that origin in
the response headers.
2014-07-14 17:40:23 -07:00

DotDeploy

This website is the server backend for the DotDeploy frontend. You can learn more about DotDeploy by visiting the homepage or learn more about this API by exploring it with Swagger

Usage

  1. Visit the Google Developers Console and either create a project or enter an existing on.
  2. In your new project, click on "APIs" in the left side bar and ensure that Google+ API and Google+ Domains API are enabled
  3. Click "Credentials" on the left side bar and create a new Client ID. Ensure that you enter your URIs in the "Redirect URIs" and "Javascript Origins" section. Write down the "Client ID" value for later.
  4. Create a new "Public API access" key, giving it access from your IP address. Write down your API key for later.
  5. Create a new file in the root of this project called client-keys.json and insert the template found below with the values from the previous two steps filled in.
  6. Launch the application with lein ring server-headless followed by an optional port number to start on.
{
    "client-id": "your-id-here.apps.googleusercontent.com",
    "api-key": "your-key-here"
}

License

Copyright © 2014 Tony Grosinger, Spencer Thomas, Ansel Santosa

Distributed under the Apache 2 License.

Description
Synchronize dotfiles on all your computers.
Readme 814 KiB
Languages
JavaScript 81.3%
CSS 11.4%
Clojure 6.3%
HTML 1%