A demonstration of NuxtJs + Vuetify + Nodejs Backend. The app is not doing anything more than an ajax call, but the ui/ux is very nice, thanks to Vuetify.
A demonstration of NuxtJs + Vuetify (vue.js+material design+ssr+state manager+complete framework). Cells data is received from backend via url /api/cell. There is nothing functional (the app is not doing anything more than an ajax call), but the ui/ux is very nice, thanks to Vuetify. If you are curious about how I've setup backend, http api/server + frontend via nuxt + vuetify + docker dev env + heroku please see the code :) .
Access the app, check out the ui/ux based on Vuetify if you're interested in ssr/pwa/material design. The app is not doing anything more than an ajax call.
nuxt vuetify web server - fastify docker for dev environment
"dependencies": {
"@nuxtjs/axios": "^5.8.0",
"@nuxtjs/pwa": "^3.0.0-0",
"cross-env": "^6.0.3",
"fastify": "^2.10.0",
"nuxt": "^2.10.2",
"got": "^9.6.0",
"prismjs": "^1.17.1",
"vue-prism-editor": "^0.3.0",
"zeul-fuego": "file:zeul-fuego"
},
"devDependencies": {
"@nuxtjs/eslint-config": "^1.1.2",
"@nuxtjs/eslint-module": "^1.1.0",
"@nuxtjs/vuetify": "^1.9.0",
"babel-eslint": "^10.0.3",
"eslint": "^6.7.0",
"eslint-config-prettier": "^6.7.0",
"eslint-plugin-nuxt": ">=0.5.0",
"eslint-plugin-prettier": "^3.1.1",
"husky": "^3.1.0",
"lint-staged": "^9.4.3",
"nodemon": "^2.0.1",
"prettier": "^1.19.1"
}
....
"zeul-fuego": "file:zeul-fuego"
....
"dependencies": {
"ajv": "^6.10.2",
"pino": "^5.14.0",
"uuid": "^3.3.3",
"ws": "^7.2.0"
}
Hm, if it only does API calls, would it have been possible to show the communication somewhere?
Sending messages between the cells would have been nice at least …
But we learned a lot during our 48h as well :-)
Really beautiful demo, and looks/feels amazing on mobile. It just doesn't really serve any purpose lol
Great idea, but if you could improve the instructions on how to use, would have been awesome :)
Nice entry and components. Hope you will check our entry too
ooctavianus
Thank you very much for feedback! I wanted to showcase a distributed queue like system concept via websockets and tiered caches (think kafka (storage in configurable tiered caches) but each topic is a tissue (a group of services with the same DNA(config/api/same entities managers) (cells)) and each tissue can be a broker). I am a bit rusty on front end and the whole thing `was` a bit cloudy in my head, that's how far I managed to bring it :) Some cells interactions would have been indeed, very nice :)