| const express = require("express"); | |
| const path = require("path"); | |
| const hbs = require("hbs"); | |
| const app = express(); | |
| let PORT = 8080; | |
| // servers any appropriate static files(i.e. css, js, etc) | |
| const publicPath = path.join(__dirname, "../../public"); | |
| app.use(express.static(publicPath)); | |
| // setups hbs view path, where express will look for files |
| .nav-list { | |
| display: inline-block; | |
| } | |
| .nav-list li{ | |
| display: inline; | |
| } | |
| .nav-list li:first-child { | |
| margin-right: 25vw; | |
| } |
| This post links my 3Box profile to my Github account! Web3 social profiles by 3Box. | |
| ✅ did:muport:QmePdm21DNFojfCz2NTivh7G73okQqGjd3kakttWaXELFr ✅ | |
| Create your profile today to start building social connection and trust online at https://3Box.io/ |
Anyone who has had to work with other developers working with different Operating Systems knows the strange bugs and issues that come up due to OS specific issues.
Furthermore, managing the dependencies and configurations needed for production deployment can be extremely time consuming.
Docker fixes these issues by:
Modern applications are, at least to some extent, data-rich. What this means is that often times applications will have features like the Twitter Feed, aggregated statistics, friends/followers and many other features that rely on complex inter-related data.
Its this data that provides the vast majority of the application value. Twitter would be quite useless if the only thing you could do is post and could only see a handful of others' tweets.
The biggest pitfall most developers can fall to is re-using the production database for development
Due to the complexity of this data, during the early development process of an application, its tempting to use the same database for production as for development.