Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Want to know how the Windows system loads this .env variable into the runtime environment. #987

Closed
parkshinhye opened this issue May 29, 2017 · 3 comments
Labels

Comments

@parkshinhye
Copy link

Info:

  • Docker version ($ docker --version): Docker version 17.03.1-ce, build c6d412e
  • Laradock commit ($ git rev-parse HEAD): f296a39
  • System info : windows 10
  • System info disto/version:

Issue:

What seems to be going wrong?

I have copied the .env file.
Want to know how the Windows system loads this .env variable into the runtime environment.

  I found windows running docker-compose up -d nginx mysql. 80,443,3306 port does not throw, that is .env has not been loaded! The The

Hope to be able to solve, thank you! The The


Expected behavior:

What should be happening instead?

Reproduce:

How might we be able to reproduce the error?

Relevant Code:

// place code here
@wangjialei01
Copy link

you need under laradock folder and run docker-compose up -d nginx mysql

$ pwd
/laradock
$ ls
DOCUMENTATION		aerospike		certbot			hhvm			mailhog			mssql			percona			postgres		selenium
LICENSE			apache2			docker-compose.yml	jenkins			mariadb			mysql			pgadmin			postgres-postgis	squid
README-zh.md		beanstalkd		elasticsearch		kibana			memcached		nbproject		php-fpm			rabbitmq		travis-build.sh
README.md		beanstalkd-console	env-example		laravel-echo-server	minio			neo4j			php-worker		redis			varnish
adminer			caddy			haproxy			logs			mongo			nginx			phpmyadmin		rethinkdb		workspace
$ 

be sure you have .env under this folder and
then you can run docker-compose up -d nginx mysql

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants