Adminator-admin-dashboard
Adminator-admin-dashboard copied to clipboard
integration with docker
this pull request is to make this awesome repository docker compatible so that users may start working without running into environment setup issues.
@aagarwal2286 There is an ERROR when docker-compose up --build after cloning your branch.
ui | npm ERR! code ERR_TLS_CERT_ALTNAME_INVALID ui | npm ERR! errno ERR_TLS_CERT_ALTNAME_INVALID ui | npm ERR! request to https://registry.npmjs.org/babel-polyfill failed, reason: Hostname/IP does not match certificate's altnames: Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net ui | ui | npm ERR! A complete log of this run can be found in: ui | npm ERR! /root/.npm/_logs/2018-09-01T09_51_37_221Z-debug.log ui | ui | > [email protected] docker-dev /home/node/app ui | > webpack-dev-server ui | ui | sh: 1: webpack-dev-server: not found ui | npm ERR! file sh ui | npm ERR! code ELIFECYCLE ui | npm ERR! errno ENOENT ui | npm ERR! syscall spawn ui | npm ERR! [email protected] docker-dev:
webpack-dev-serverui | npm ERR! spawn ENOENT ui | npm ERR! ui | npm ERR! Failed at the [email protected] docker-dev script. ui | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. ui | npm WARN Local package.json exists, but node_modules missing, did you mean to install? ui | ui | npm ERR! A complete log of this run can be found in: ui | npm ERR! /root/.npm/_logs/2018-09-01T09_51_37_536Z-debug.log
You should also change the name of the container.
ui | npm ERR! request to https://registry.npmjs.org/babel-polyfill failed, reason: Hostname/IP does not match certificate's altnames: Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net
Seems it's temporary issue from npm side and resolved now. I have checked it in my local and it's working as expected. Please refer discussion -> https://npm.community/t/registry-npmjs-org-certification-invalid/1860/5
@aagarwal2286 You were right. It works.
Thanks for contributing this. I'm wondering if it is necessary though, as our only dependency is node-12.
You could just run the node-12 image directly, mounting your current directory (adminator) into /app:
docker run -v $(pwd):/app -p 3000:3000 -it node:12-buster-slim /bin/bash
Scripts for cloning the repository (init.sh) I wouldn't add in the repository.
Should we close as stale?
Closing, let me know if you think it should be reopened.