docker-selenium VS tokens

Edit: I got some parts of it running. This video is very helpful. I gave up on the official docker repository for change detection io and switched to the LSIO version. I had to first install and run the docker Selenium container (available here). I installed the standalone version of Chrome from that page. Now I added one line to the docker-compose.yml in the environment section (as mentioned in the video. I did not add BASE_URL) and that was "WEBDRIVER_URL=http://192.168.1.15:4444" (this has to be an actual IP address, can't use "localhost" or anything else. I redeployed the container and the webdriver worked.

Selenium with Docker Selenium Grid https://github.com/SeleniumHQ/docker-selenium. Isolated and scalable.

Next is the image that we are using to run the docker command. Here we are using the Selenium Firefox standalone image with tag 4.0.0-rc-1-prerelease-20210618. More information about the latest versions available can be found from the official Selenium Github repository and the Docker hub public registry.

If you run your own, you need to account for your computer's processing power. That is the bottleneck. Check out this repo for more info. https://github.com/SeleniumHQ/docker-selenium

Same. I had sucess with https://github.com/SeleniumHQ/docker-selenium

If you look on selenium's dockerhub, there are many images to chose from which are much newer. As far as I'm concerned, that image is abandoned and I would definitely not use it. Not saying it is the reason for whatever happened to you, but kind of shocking that change detection is recommending it.

Playwright has a limitation that restricts running tests in Selenium Grid to only the version prior to 4.5.2-20221021 (at the time of this writing - February/2023).

I literally clicked on your link, followed the instructions and found this.

Click on your profile in the top right corner > Settings > Developer settings, or visit: https://github.com/settings/tokens.

First of all, you need to generate a new GitHub Token. You can generate a token in your GitHub account settings at https://github.com/settings/tokens. Make sure to add the ‘read:packages’ scope to your token.

First, generate the GitHub token here.

Environment Variables Create a file .env in the root folder and add your own github api token as below

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

Versioning The initial step in this workflow involves generating version numbers based on git tag numbers. To access repository information, it's necessary to include a GitHub token in the secrets. You can create a GitHub token by following this link. Please keep in mind that secret names cannot start with the term GITHUB. For instance, you might save your GitHub token as TOKEN_GITHUB.

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

Generate a classic PAT (personal access token) from Github with repo and admin:org scopes at least.

YOUR_TOKEN="no_token_for_you" # IMPORTANT: your Github API access key, make one at "https://github.com/settings/tokens"

You should click on that and then you will see Tokens (classic) which will bring you to https://github.com/settings/tokens