itsgoingd / itsgoingd/clockwork

Clockwork Chrome Plugin Does Not Work with Docker (Lando)

Open
#634 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
6k
Forks
333
Avg merge
5m
Merged PRs (30d)
1

Description

I am using Lando for development (it is just an abstraction layer for Docker with docker-compose) on Linux Mint 21.1. In Lando/Docker containers, I have my Laravel project. I installed Clockwork via composer into my project, installed the Clockwork plugin in my Edge browser.

But it does not work in DevTools on the page of my Laravel project (e.g. https://laravel-blog.lndo.site/ in my case). So, I went to the Edge plugin settings and try to map the "Code path" like this:

  1. /app/blog/
  2. /home/lukas/Sites/Laravel-Blog/blog/

where 1. is the path in the container (in Docker that would typically be /var/www/html/, in Lando the apps sits in /app/ and 2. is the local path. Both paths are the folder, where is my Laravel app installed.
Please, would someone know how to set it? Or how can I get any error or debugging information so I can find what the error is?

EDIT: I just did some other work for like 15 minutes, than went back and simply refreshed the page and the Edge plugin started to work. The problem is that I have no idea why, I did not do anything. Is there any lag or some cache got flushed or what?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure in the Clockwork browser plugin while using the Laravel project in Lando/Docker, comparing the working /clockwork/app endpoint with the main project page. Inspect the plugin's Code path settings for /app/blog/ and /home/lukas/Sites/Laravel-Blog/blog/ and determine what debugging information is available; done means explaining or correcting the DevTools integration behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, laravel, php
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.