FCC API & Microservices

Project 01: Timestamp Microservice

User stories:

1. The API endpoint is GET [project_url]/api/timestamp/:date_string?
2. A date string is valid if can be successfully parsed by new Date(date_string). NOTE: The unix timestamp needs to be an integer (not a string) specifying milliseconds. In the FCC test we will use date strings compliant with ISO-8601 (e.g. "2016-11-20") to ensure an UTC timestamp.
3. If the date string is empty it should be equivalent to trigger new Date(), i.e. the service uses the current timestamp.
4. If the date string is valid the api returns a JSON having the structure: {"unix": <date.getTime()>, "utc" : <date.toUTCString()> }
   i.e. {"unix": 1479663089000 ,"utc": "Sun, 20 Nov 2016 17:31:29 GMT"}.
5. If the date string is invalid, the API returns a JSON having the structure you get from the date manipulation functions use above:
   i.e.: {"unix": null, "utc" : "Invalid Date" }.

Example usage:

• https://curse-arrow.hyperdev.space/api/timestamp/2015-12-15
• https://curse-arrow.hyperdev.space/api/timestamp/1450137600000

Example output:

• { "unix": 1450137600, "natural": "December 15, 2015" }

The Project:

On the front-end:

1. Edit public/client.js, public/style.css and views/index.html
2. Drag in assets, like images or music, to add them to your project
   On the back-end:
3. Your app starts at server.js
4. Add frameworks and packages in package.json
5. Safely store app secrets in .env (nobody can see this but you and people you invite)