{"id":111365,"date":"2020-04-10T08:00:00","date_gmt":"2020-04-10T08:00:00","guid":{"rendered":"https:\/\/fedoramagazine.org\/?p=30805"},"modified":"2020-04-10T08:00:00","modified_gmt":"2020-04-10T08:00:00","slug":"using-fedora-to-quickly-implement-rest-api-with-javascript","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2020\/04\/10\/using-fedora-to-quickly-implement-rest-api-with-javascript\/","title":{"rendered":"Using Fedora to quickly implement REST API with JavaScript"},"content":{"rendered":"

Fedora Workstation uses GNOME Shell by default and this one was mainly written in JavaScript. JavaScript is famous as a language of front-end development but this time we’ll show its usage for back-end.<\/p>\n

We’ll implement a new API using the following technologies: JavaScript, Express and Fedora Workstation. A web browser is being used to call the service (eg. Firefox from the default Fedora WS distro).<\/p>\n

<\/span> <\/p>\n

Installing of necessary packages<\/h2>\n

Check: What’s already installed?<\/strong><\/p>\n

$ npm -v\n$ node -v<\/pre>\n
You may already have both the necessary packages installed and can skip the next step. If not, install nodejs<\/em>:<\/p>\n
$ sudo dnf install nodejs<\/pre>\n
A new simple service (low-code style)<\/h2>\n
Let\u2018s navigate to our working directory (work<\/em>) and create a new directory for our new sample back-end app.<\/p>\n
$ cd work\n$ mkdir newApp\n$ cd newApp\n$ npx express-generator<\/pre>\n
The above command generates an application skeleton for us.<\/p>\n
$ npm i<\/pre>\n
The above command installs dependencies. Please mind the security warnings \u2013 never use this one for production.<\/p>\n
Crack open the routes\/users.js<\/strong><\/p>\n
Modify line #6 to: <\/p>\n
res.send(data);<\/pre>\n
Insert this code block below var router<\/em>:<\/p>\n
let data = { '1':'Ann', '2': 'Bruno', '3': 'Celine' }<\/pre>\n
Save
\nthe modified file.<\/p>\n
We modified a route and added a new variable data. This one could be declared as a const<\/em> as we didn\u2018t modify it anywhere. The result:<\/p>\n
\"\"<\/figure>\n
Running the service on your local Fedora workstation machine<\/h2>\n
$ npm start<\/pre>\n
Note: The application entry point is bin\/www. You may want to change the port number there.<\/em><\/p>\n
Calling our new service<\/h2>\n
Let\u2018s launch our Firefox browser and type-in:<\/p>\n
http:\/\/localhost:3000\/users<\/em><\/p>\n
\"\"
Output<\/figcaption><\/figure>\n
It\u2018s also possible to leverage the Developer tools. Hit F12<\/strong> and in the Network<\/em> tab, select the related GET request and look at the side bar response tab to check the data.<\/p>\n
Conclusion<\/h2>\n
Now we have got a service and and an unnecessary index accessible through localhost:3000<\/em>. To get quickly rid of this:<\/p>\n
    \n
  1. Remove the views<\/em> directory<\/li>\n
  2. Remove the public<\/em> directory<\/li>\n
  3. Remove the routes\/index.js<\/em> file<\/li>\n
  4. Inside the app.js<\/em> file, modify the line 37 to:
     \n
    \n
    res.status(err.status || 500).end();<\/div>\n<\/div>\n<\/li>\n
  5. Remove the next line res.render(‘error’)<\/em><\/li>\n<\/ol>\n
    Then restart the service:<\/p>\n
    $ npm start<\/pre><\/p>\n","protected":false},"excerpt":{"rendered":"
    Fedora Workstation uses GNOME Shell by default and this one was mainly written in JavaScript. JavaScript is famous as a language of front-end development but this time we’ll show its usage for back-end. We’ll implement a new API using the following technologies: JavaScript, Express and Fedora Workstation. A web browser is being used to call […]<\/p>\n","protected":false},"author":2,"featured_media":111366,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[971,972,45,973,42,43,974,46,47],"class_list":["post-111365","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fedora-os","tag-api","tag-back-end","tag-fedora","tag-fedora-workstation","tag-for-developers","tag-for-system-administrators","tag-javascript","tag-magazine","tag-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/111365","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=111365"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/111365\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/111366"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=111365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=111365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=111365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}