| { | |
| "email": "me@email.com", | |
| "zone": "CLOUDFLARE_ZONE", | |
| "token": "CLOUDFLARE_TOKEN" | |
| } |
One Paragraph of project description goes here
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');Those suck for maintenance and they're ugly.
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
| [ | |
| { "city" : "Beograd", "_id" : 11000 }, | |
| { "city" : "Beograd Vozdovac", "_id" : 11010 }, | |
| { "city" : "Beograd Čukarica", "_id" : 11030 }, | |
| { "city" : "Beograd Zvezdara", "_id" : 11050 }, | |
| { "city" : "Beograd Palilula", "_id" : 11060 }, | |
| { "city" : "Novi Beograd", "_id" : 11070 }, | |
| { "city" : "Beograd Zemun", "_id" : 11080 }, | |
| { "city" : "Beograd Rakovica", "_id" : 11090 }, | |
| { "city" : "Kaluđerica", "_id" : 11130 }, |