Message from JavaScript discussions
January 2018
— Sure, more tooling available, but there's nothing wrong with using anything else over Python. It's "ok" to build neural networks on JS.
Is .env file still the best practice to save environment configuration? Even with a js stack? (express and so on)
— I like the idea of config.js
— But in general, there is no best practice for JS yet
— Ok
— I am looking for a clean method for storing db passwords and shit without pushing it to git
— Local Password Database
— I recommend KeePassX
— * Needs a master password (Never share, write down, or otherwise compromise this, this should exist ONLY in your head, and when you type it to unlock the database)
— * Database file will be only a few kilobytes, safe to transfer and store anywhere you please (Generally a bad idea to store it publicly though, use some file backup service (Dropbox, Telegram, etc)
— I have a web with landing page on domain.com, spa web app on customer.domain.com and another spa web app on merchant.domain.com
— Both of them using jwt for authentication and i store it on my localstorage, am wondering how can i share the token (localstorage data) between my subdomain