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

Update config to run addons-frontend with addons-server locally #9956

Merged
merged 1 commit into from
Jan 7, 2021

Conversation

willdurand
Copy link
Member

@codecov-io
Copy link

Codecov Report

Merging #9956 (4ec8b1b) into master (08769d6) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    mozilla/addons-server#9956   +/-   ##
=======================================
  Coverage   98.39%   98.39%           
=======================================
  Files         262      262           
  Lines        7609     7609           
  Branches     1374     1374           
=======================================
  Hits         7487     7487           
  Misses        114      114           
  Partials        8        8           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 08769d6...4ec8b1b. Read the comment docs.

@willdurand willdurand marked this pull request as draft January 5, 2021 16:43
@willdurand willdurand changed the title Update config to run frontend locally Update config to run addons-frontend with addons-server locally Jan 5, 2021
@willdurand willdurand marked this pull request as ready for review January 7, 2021 08:42
Copy link
Contributor

@bobsilverberg bobsilverberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking care of this @willdurand! It seems to be working for me. I'm getting an error on the search API, but I believe that's related to my local addons-server install and not this. I am able to view an add-on detail page using data from the local add-on server with this patch, so I believe it's working. I had one question about the port, but otherwise r+wc.

@@ -37,10 +37,9 @@ Here are some commands you can run:

| Command | Description |
| --- | --- |
| yarn amo | Start the dev server/proxy (for amo) using data from Docker. _This is not currently working. See [issue-7196][]_. |
| yarn amo:olympia | Start the dev server/proxy (for amo) using data from a local addons-server environment. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think it's worth adding a note that the site will be located at http://olympia.test:4000? I know that is output to the console, so maybe not necessary, but it could be helpful for folks expecting it to be the same location as with amo:dev and amo:stage.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, is it http://olympia.test:4000 or http://olympia.test:3333? Both seem to work.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:3333 is the app, which runs behind the proxy at :4000.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the output is fine. We don't develop with both local envs in parallel usually so I think it's for power users who would read the console output :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

yarn amo no longer works - no styles/JS Stop using port 3000 for addons-frontend in Docker
3 participants