Yes, when you create a Python virtual environment inside your project folder, it will isolate all the installed packages and dependencies within that environment. This means that the files related to the virtual environment (e.g., Python executables, pip, and any installed packages) will reside in the project folder itself, and nott clutter global directories like APPDATA on Windows.

Thanks for commenting. I think the ".cache" folder gets created earlier in the video when we did `pip install `or `mkdocs build`

Thanks so much for this feedback - highly appreciated.

Glad it was helpful!

Thanks for taking the time to write this comment. Lots more content planned ☺️

Check the GitHub settings , maybe you missed setting to the new branch ?

Yes its possible. By default, MkDocs uses the gh-pages branch for deployment. However, you can change this behavior by specifying the remote-branch option in the mkdocs.yml configuration file or by passing it as a command-line argument. For example, if you want to deploy from the docs branch, you can run: mkdocs gh-deploy --remote-branch docs Make sure to also update the branch in the GitHub settings when you are configuring GitHub Pages

Sorry to hear you are having this problem. It's hard for me to diagnose without seeing your repo, but theres a few things you might want to try: 1. Ensure the CNAME File is in the Correct Location The CNAME file should be in your source directory (e.g., docs/) so that it gets copied to the root of the built site during deployment. 2. Modify Your GitHub Actions or Deployment Script GitHub Actions might be overwriting or exclude the CNAME file during each deployment. You can modify your workflow to ensure that the CNAME file is always included in the deployment. You can add a step to ensure that the CNAME file is copied into the build output before deploying, e.g: jobs: deploy: runs-on: ubuntu-latest steps: - name: Checkout repository uses: actions/checkout@v2 - name: Set up Python uses: actions/setup-python@v2 with: python-version: '3.x' - name: Install dependencies run: pip install mkdocs mkdocs-material - name: Build site run: mkdocs build - name: Add CNAME file run: echo "yourcustomdomain.com" > ./site/CNAME - name: Deploy to GitHub Pages run: mkdocs gh-deploy --force 3. Check GitHub Pages Settings Check your repository's GitHub Pages settings, Go to Settings > Pages. Make sure that under "Custom domain," your custom domain is listed and saved. Hope that helps...

Glad you enjoyed it!

Thank you 👍

Glad it was helpful!

Glad you liked it!

Glad it was helpful!

Appreciate that - thank you ! 🙏

Thanks - appreciate your feedback ☺️

Good question - I’m pretty sure you can nest multiple times. Make sure you enable “navigation.sections” in your config . See squidfunk.github.io/mkdocs-material/setup/setting-up-navigation/#navigation-sections

Glad to hear that! Thanks for letting me know :)

Great to hear! Please share a link , would love to take a look

Thanks for the feedback. I'd need to see your code to debug the error, but it looks like you might have a typo in your feature file

Yes its amazing for a blog. Hoping to create a video for this soon.

Glad you enjoyed the video. Yes Gatling can handle all these things. Check my other video if you need help

Thanks Roman - much appreciated :)

Glad you liked it! Appreciate the feedback - what else would you like to see covered?

Thanks Charlie - glad it was helpful. Honestly I'm not sure without seeing your code. However, I am currently working on a brand new getting started video for MkDocs Material where I cover this, so following that might help. It should be out in a week or so.

I'm not sure I understand the docstring question, could you elaborate? For reordering see if github.com/squidfunk/mkdocs-material/discussions/3482 is helpful

Thanks for the kind words! I'm not aware of any issues with regards to rendering and plugin to be honest... I'm actually working on an updated version of this tutorial that should be out in a next next or two - so I'll keep an eye out for any issues around this in the latest version of the plugins

Glad you enjoyed it - thanks for commenting :)

Partly yes, but I also used Premier Pro though for some of it

Got it! Thanks for letting me know. I have the video planned in my pipeline amongst some other new projects :)

Good choice! Let me know how it goes!

Thanks Boris - really appreciate you taking the time to watch and comment. Anything in particular you would like to see covered?

Thanks for the feedback. So I asked the Gatling team this question around a month ago, and they didn’t yet have any profiling data to compare the versions . With that being said , the JS version is essentially a wrapper on top of the original Scala code , so I would expect the resource consumption to be similar

@@james-willett Thanks so much for your response! Great to know that resource consumption in the JS version is similar to the original Scala version

Thanks - really appreciate it . And im also pleased to be back uploading ☺️

Thank you!!

So this only applies to API testing? If not, could you illustrate on the UI part as well please? Thanks alot

@@mr_possible6197​​⁠this video just covers api testing yes - I’ll look at creating a follow up video for UI testing if that’s interesting for you 😊

@@james-willett Oh Yes! Cheers!!

This is amazing James ! I want to try and show demo at karate at my work I shall try this cheers

@@MaheshJoshi_wellingtongreat to hear - let me know how it goes 😊