https://github.com/cored/connect
Namely Connect – Integrate with Namely.
https://github.com/cored/connect
Last synced: 24 days ago
JSON representation
Namely Connect – Integrate with Namely.
- Host: GitHub
- URL: https://github.com/cored/connect
- Owner: cored
- Created: 2015-01-08T15:06:40.000Z (over 11 years ago)
- Default Branch: master
- Last Pushed: 2016-05-04T15:20:47.000Z (about 10 years ago)
- Last Synced: 2025-02-21T12:35:08.626Z (over 1 year ago)
- Language: Ruby
- Homepage:
- Size: 1.75 MB
- Stars: 0
- Watchers: 1
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Namely Connect
[](https://codeclimate.com/github/namely/connect)
[](https://circleci.com/gh/namely/connect)
Simple web app for connecting external apps with Namely.
Planned integrations:
* Jobvite (create new Namely Profiles based on candidate data)
## Getting set up
0. Install Docker & Docker Machine & Docker Compose
osx:
```sh
brew install docker-compose
```
1. Build docker image
```sh
docker-compose build
```
2. Run all services
```sh
docker-compose up
```
3. Run the tests:
```sh
docker-compose run web rake
```
When changing feature specs that make API calls, you will need to rebuild one or
more VCR fixtures (in `spec/fixtures/vcr_cassettes`). When running these specs
without a saved VCR cassette, you will have to set the following environment
variables in your `.env` file:
* `TEST_JOBVITE_KEY` and `TEST_JOBVITE_SECRET`: A valid Jobvite API key and
secret.
* `TEST_NAMELY_SUBDOMAIN`: The subdomain of a Namely sandbox account, e.g. if
the account is at `foobar.namely.com`, you would set this to `foobar`.
* `TEST_NAMELY_ACCESS_TOKEN`: A valid access token for the Namely sandbox
account specified by `TEST_NAMELY_SUBDOMAIN`.
* `TEST_NAMELY_AUTH_CODE`: An OAuth auth code for the Namely sandbox account
specified by `TEST_NAMELY_SUBDOMAIN`.
## Importing data from Jobvite to Namely
To import newly hired Jobvite candidates for all users, run:
```sh
docker-compose run web rake jobvite:import
```
This task can be invoked by a cron job or otherwise scheduled to regularly
import newly hired candidates.
## Development
### Pull Requests
#### Tags
We tag pull requests, so their state is obvious. The following tags should be used in the subject as [TAG] My contribution.
* WIP - Work In Progress. The pull request will change, and there is no need to review it yet.
* RFC - Request For Comment. The request is ready for +1s (:+1:) and/or comments.
* RDY - The request is ready to be merged. The request must have received at least 2 +1s (:+1:) (approvals) from other developers before being marked RDY.
NOTE: When you approve a pull request (ie, give a +1), please add a short comment about your decision.