bluzi / bluzi/name-db

Review deployment script

Open
#191 1 comment 0 reactions 0 assignees View on GitHub
good first issue hacktoberfest help wanted
Dominant language
JavaScript
Stars
60
Forks
217
PR merge metrics
No merged PRs in 30d

Description

I recently added [a deployment script](https://github.com/bluzi/name-db/blob/master/deploy/deploy.collection.js) and [Travis deployment](https://github.com/bluzi/name-db/blob/master/.travis.yml)

I'd love if someone review it and write in this issue if there are things that could be better implemented.

Thanks!

*Some info about what this script actually does:*
Every time a branch/pull request is being merged to the master branch, Travis execute the deployment script at`deploy/deploy.collections.js`.
This script connects to a MySQL database, checks to see what changed in `collection/`, and updates the database. (removes/changes/adds data, so it'll be exactly like `collection/`)

The MySQL database from above, is being used by [the API](http://54.161.117.62/david) to deliver the data. ([see code](https://github.com/bluzi/name-db/tree/master/api))

Contributor guide

No contributing guide indexed for this repository

Research direction

Read deploy/deploy.collection.js, the similarly referenced deploy/deploy.collections.js, and .travis.yml first. Trace how the deployment script processes collection/ and synchronizes MySQL, then compare its assumptions with api/. Done means documenting actionable findings in the issue and identifying any agreed improvements.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, mysql
Domain
api, databases, devops
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.