Skip to content

Fix the order of instructions for initialization #126

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Aug 21, 2025
Merged

Fix the order of instructions for initialization #126

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
17f88a7
Fix the order of instructions for initialization
ehuelsmann May 23, 2025
2011e25
Remove reference to traefik
ehuelsmann May 23, 2025
69b7762
Expose grep container ports
ehuelsmann May 23, 2025
6515045
Change "grep" access references
ehuelsmann May 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,15 +130,15 @@ This will prompt you to confirm removing old indices and setting up mappings on
the Elasticsearch service (say `YES`). It will then proceed to rsync a partial
CPAN in `/CPAN` for its metadata to be imported.

Once the above is done, you should be able to see your local partial CPAN data
in e.g. [http://localhost:5001/recent](http://localhost:5001/recent) and
elsewhere.

Alternatively, if you just want to hack on the web frontend, you can run this
instead of all the above:
After the initialization above completes, the next step is to start the web
frontend with the following command:

docker compose up web-server

Once that is done, you should be able to see your local partial CPAN data
in e.g. [http://localhost:5001/recent](http://localhost:5001/recent) and
elsewhere.

Copy link
Member

Choose a reason for hiding this comment

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

It has been a while since I set up new containers. After docker compose up web-server are you getting the data from your partial index or is it actually routing your requests to the live API? I suspect it's the latter and if that's the case, that's an error in our documentation.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually, I think you're right: I'm seeing full recent history and I'm able to browse the "Crop" release which I don't think was imported. How do I make the web service connect to the local API?

Copy link
Member

Choose a reason for hiding this comment

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

It looks like we are recommending this way: https://github.com/metacpan/metacpan-docker?tab=readme-ov-file#binmetacpan-localapi

It might be worth looking under the hood to see if this is still works and is the best idea. I would say if it does work, maybe we can just move on to the next thing rather than tweaking too much.

From here, you can proceed and hack on the MetaCPAN code at `src/metacpan-api`
and/or `src/metacpan-web` directories, and saving edits will reload the
corresponding apps automatically!
Expand Down