Estadísticas y predicciones de 2. Bundesliga

Momentos Clave a Seguir Durante los Partidos

• Inicios Agresivos: Observa cómo comienzan los equipos; algunos podrían optar por un ataque temprano para sorprender al rival.
• Tiempo Muerto: Los cambios tácticos durante el tiempo muerto pueden cambiar drásticamente el flujo del juego.
• Finales Intensos: Los equipos a menudo aumentan su intensidad hacia el final del partido cuando están luchando por puntos cruciales.
techtronics/techtronics.github.io<|file_sep|>/_posts/2020-05-21-Using-WSL-to-create-a-Python-virtual-environment.md --- layout: post title: Using WSL to create a Python virtual environment description: Creating a Python virtual environment on Windows Subsystem for Linux. date: '2020-05-21' tags: - linux - windows - wsl - python - virtualenv --- It's been a while since I've done any Python development on my Windows laptop. I've been using [Visual Studio Code](https://code.visualstudio.com/) as my IDE, which is pretty nice and supports WSL well. One thing I found lacking was the ability to use the standard `python -m venv` command to create a virtual environment inside WSL. The way it worked was that when I ran the `python -m venv` command in bash, it would create the `venv` folder but not populate it with the correct files. When I tried to activate it with `source bin/activate`, I'd get an error that the file didn't exist. After some research I found that this was due to a bug in [Ubuntu 20](https://bugs.launchpad.net/ubuntu/+source/python3-virtualenv/+bug/1861355). ### The fix To fix this issue you need to run `apt-get update` and then run the following: sudo apt-get install --reinstall python3-distutils This will reinstall the `python3-distutils` package which should fix the bug. Now if you run `python -m venv myvenv` it should create the virtual environment correctly. <|file_sep|># Site settings title: "Techtronics" email: "[email protected]" description: "A blog by Jason Bickford" baseurl: "" url: "https://techtronics.github.io" # Build settings markdown: kramdown # Blog settings paginate: 10 plugins: - jekyll-paginate # Author settings author: name: "Jason Bickford" email: "[email protected]" # Social media links social: github: techtronics # Disqus comments disqus: shortname: techtronics # Google Analytics tracking ID google_analytics_tracking_id: # Site colors (for styling) colors: primary_color: "#000000" secondary_color: "#ffffff" <|repo_name|>techtronics/techtronics.github.io<|file_sep|>/_posts/2018-01-04-Moving-from-jekyll-now-to-github-pages.md --- layout: post title: Moving from jekyll-now to GitHub Pages description: Moving my site from jekyll-now to GitHub Pages. date: '2018-01-04' tags: - github-pages --- I originally started this blog using [jekyll-now](https://github.com/barryclark/jekyll-now), but after reading about [GitHub Pages](https://pages.github.com/) I decided to try it out. The only difference is that you need to put your site files in a repository called `.github.io`. You also don't need to push your `_config.yml` file. So far it's been working great and I'm happy with how easy it is to set up and use. <|file_sep|># Techtronics Blog My personal blog built with Jekyll and hosted on GitHub Pages. ## License The contents of this repository are released under the [MIT license](LICENSE). <|repo_name|>techtronics/techtronics.github.io<|file_sep|>/_posts/2018-01-09-Building-my-first-Jekyll-theme.md --- layout: post title: Building my first Jekyll theme description: Building my first Jekyll theme for my blog. date: '2018-01-09' tags: - jekyll --- I decided to try and build my own theme for my blog instead of using [jekyll-now](https://github.com/barryclark/jekyll-now). It took me about an hour or so to get something basic working, but I'm really happy with how it turned out. ## Using a starter theme I used [Jekyll Bootstrap](https://jekyllbootstrap.com/) as my starting point, which already had most of the stuff I needed built in. I just needed to add in some custom CSS and change some of the HTML. ## Creating posts I had to modify the `_config.yml` file so that posts were stored in `_posts`. The default location is `_site`. ## Linking posts There were a few changes I needed to make when linking between posts. The first was updating all of my post links from `http://example.com/blog/` to just `/blog/`. The other thing was updating my pagination links from `<%= page.previous_page %>` and `<%= page.next_page %>` to `<%= prev_page_path %>` and `<%= next_page_path %>`. ## Conclusion Overall it was a really fun experience building my own theme, and now that it's working I'm looking forward to adding more features and customizing it even more. <|file_sep|>// Typography $font-size-base : 1rem; $line-height-base : 1.5; $font-family-sans-serif : -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Oxygen-Sans,"Ubuntu C",Cantarell,"Helvetica Neue",sans-serif; // Colors $color-primary : #333333; $color-secondary : #ffffff; $color-success : #28a745; $color-info : #17a2b8; $color-warning : #ffc107; $color-danger : #dc3545; // Spacing $space-base : $font-size-base * $line-height-base; // Links $link-color : $color-primary; $link-hover-color : darken($link-color,15%); $link-decoration : none; // Code formatting code { font-family : SFMono-Regular,Menlo,Monaco,Lucida Console,Liberation Mono,Courier New,monospace; } // Layout styles body { font-size : $font-size-base; line-height : $line-height-base; } .container { max-width : 960px; } header { margin-bottom : $space-base * 3; } footer { margin-top : $space-base * 3; } // Post styles .post { } .post__header { } .post__title { } .post__meta { } .post__content { } <|file_sep|># Site navigation links # Navigation Links for header main_nav: # Links in footer navigation bar (1st level nav) footer_nav: # Links for social footer (icons in bottom right footer section) social_nav: # Contact information displayed at top of contact page (if applicable) contact_info: <|repo_name|>techtronics/techtronics.github.io<|file_sep|>/_posts/2020-08-27-Automatically-deploying-to-GitHub-Pages-using-GitHub-actions.md --- layout: post title: Automatically deploying to GitHub Pages using GitHub actions description: Automatically deploying updates to your GitHub Pages site using GitHub actions. date: '2020-08-27' tags: - github-pages --- I recently updated my site from [Jekyll Now](https://github.com/barryclark/jekyll-now) to [GitHub Pages](https://pages.github.com/) and wanted to automate the deployment process. I decided to use [GitHub Actions](https://github.com/features/actions) for this since they are free for public repositories and make it easy to automate deployments. ## Setting up your GitHub Actions workflow First you need to create a `.github/workflows` directory in your repository if one doesn't already exist. Next you need to create a new YAML file inside this directory with your workflow configuration. In my case I named mine `deploy.yml`. yaml name: Build and deploy Jekyll site on: push: branches: - master # Change this if you use a different branch name jobs: build-and-deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@master - name: Setup Ruby Environment uses: actions/setup-ruby@v1 with: ruby-version: '2.x' - name: Build site run: | gem install bundler bundle install bundle exec jekyll build - name: Deploy site uses: peaceiris/actions-gh-pages@v3 with: github_token: ${{ secrets.GITHUB_TOKEN }} publish_dir: ./_site This will automatically build and deploy your site whenever you push changes to your master branch. ## Adding a secret token for authentication To deploy your site you need to add a secret token for authentication. You can do this by going into your repository settings and selecting "Secrets". Then click on "New repository secret" and enter `GITHUB_TOKEN` as the name and generate a new token. Make sure you copy this token somewhere safe because you won't be able to see it again! Once you've added this secret token, your workflow should be able to authenticate with GitHub and deploy your site automatically whenever you push changes. <|repo_name|>techtronics/techtronics.github.io<|file_sep|>/_posts/2018-01-12-Supporting-javascript-in-Jekyll.md --- layout: post title: Supporting JavaScript in Jekyll description: Supporting JavaScript in Jekyll by adding script tags dynamically using Liquid templating language. date: '2018-01-12' tags: - jekyll --- Jekyll doesn't natively support JavaScript files, so you have to add them manually using Liquid templating language. To do this you can create a new file called `_includes/javascript.html` and add the following code: +liquid {% raw %} {% endraw %} Then include this file in your layout file like so: +liquid {% raw %} {% include javascript.html %} {% endraw %} This will add the `script.js` file located in the `assets/js` directory of your project. You can also add multiple script files by creating separate includes for each one and including them all in your layout file. ## Conclusion Adding support for JavaScript in Jekyll is easy once you know how