Rename .env to something else and reconfigure autoenv.
980 karma · joined June 18, 2012
Rename .env to something else and reconfigure autoenv.
The workaround that I've found for this problem is to set "AUTOENV_ENV_FILENAME=.env.user" and then inside the project folder, I'm now using ".env.user" instead of just ".env".
I'll use this hack until Docker guys fix Docker Compose.
Now we have a lot of useful and legitimately needed functionality and unscalable system.
Make sure that you always measure and present the numbers of your systems abilities along with new product features to the management.
It is a very tricky balance. Hard to master. Communicate!
What are the major differences to Scala with Akka?
Why o why is this not written in a way to support TypeScript?
Why o why is this thing not written with/for TypeScript?
- https://speakerdeck.com/itakeshi/metaprogramming-in-scala-th...
- https://geirsson.com/post/2016/02/scalameta/
Some Ruby scripting and ffmpeg was also involved. Here is the code - https://github.com/otobrglez/movement
- More functional principles and more resilient implementations.
- Complete decoupling from lower levels. Meaning that you don't care about servers anymore. Apps are Dockerized and resources are dedicated automatically.
- No more human designed APIs. Why write APIs if modern machine learning principles can replace the whole concept?
- More lambda / serverless concepts.
- APIs and integrations will be automated and auto discovered.
- More (micro)services, mixing of different languages and stacks.
- More streams, more events,...