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

Codespaces: composer server start produces error message #394

Open
1 task
mikelittle opened this issue Aug 1, 2022 · 0 comments
Open
1 task

Codespaces: composer server start produces error message #394

mikelittle opened this issue Aug 1, 2022 · 0 comments
Labels
bug Existing functionality isn't behaving as expected should have Should be done, medium priority for now

Comments

@mikelittle
Copy link
Contributor

Running composer server start under codespaces generates the following error message

Missing hosts entries for: s3-localhost., s3-console-localhost., cognito-localhost., pinpoint-localhost., elasticsearch-localhost.
Add the following line to your /etc/hosts file:

127.0.0.1 localhost. s3-localhost. s3-console-localhost. cognito-localhost. pinpoint-localhost. elasticsearch-localhost. # altis:localhost.

These local host names may need to be fixed for a Codespaces environment. In particular, s3-console-localhost is used by Tools > S3 Browser in the Dashboard.

This may need mapping to a different url or port number so the functionality continues to work.

I don't know the purpose of the other host names. If they are not required, they should be removed so the error message is not generated.

Acceptance criteria:

  • No error message is generated
@mikelittle mikelittle added bug Existing functionality isn't behaving as expected should have Should be done, medium priority for now labels Aug 1, 2022
@mikelittle mikelittle changed the title Codespaces: composer server start produces erro message Codespaces: composer server start produces error message Aug 1, 2022
@robindevitt robindevitt removed their assignment Oct 24, 2022
@veselala veselala added this to the v12 minor issues milestone Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Existing functionality isn't behaving as expected should have Should be done, medium priority for now
Projects
None yet
Development

No branches or pull requests

3 participants