# .dockerignore usage Published articles for .dockerignore usage. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Docker: guía práctica de contenedores en Linux DevFeed: [Docker: guía práctica de contenedores en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-02T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Docker](), [Linux](), [Docker Compose](), [Dockerfile](), [container](), [Command-line interface](), [Kernel]() Tags: [cgroups](), [cli](), [compose](), [container](), [debian](), [distro](), [docker](), [docker-compose](), [dockerignore-usage](), [kernel](), [linux](), [oci](), [podman](), [python]() ### AI overview A practical Spanish-language guide to Docker on Linux. It explains container isolation through Linux namespaces and cgroups, installation on Ubuntu/Debian, Docker architecture, image layers and Dockerfiles, and introduces networks, volumes, Docker Compose, and security practices. ### Source excerpt Guía práctica de Docker: arquitectura, capas de imagen, redes, volúmenes, Docker Compose y buenas prácticas de seguridad, con ejemplos reales. ## Crosspost Your Blog articles to Social Media DevFeed: [Crosspost Your Blog articles to Social Media]() Original publisher: [Read original article]() Author: Tom Published: 2025-09-14T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [GitHub Actions](), [Hugo](), [RSS Feed](), [Mastodon](), [X (Twitter)]() Tags: [articles](), [boost-blog-traffic](), [crosspost-blog-to-social-media](), [dockerignore-usage](), [github](), [github-actions](), [github-actions-automation](), [how-to](), [hugo](), [hugo-rss-sitemap](), [mastodon](), [mastodon-blog-integration](), [rss](), [seo](), [twitter](), [twitter-crossposting](), [wordpress]() ### AI overview A tutorial on automating blog post crossposting to social networks with GitHub Actions. It describes a custom action that reads posts from a Sitemap or RSS/Atom feed, filters and sorts them, and publishes them automatically, with RSS preferred to avoid reposting updated articles. ### Source excerpt Learn how to automatically share your latest blog posts to Mastodon, Twitter/X, and other social networks using GitHub Actions and the crosspost tool. A simple way to regain traffic lost to search engines and AI. ## Introducing Heroku-Streamlit: Seamless Data Visualization DevFeed: [Introducing Heroku-Streamlit: Seamless Data Visualization]() Original publisher: [Read original article]() Author: Anush DSouza Published: 2025-05-01T08:00:09Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Streamlit](), [Template](), [Python](), [web applications](), [Cloud](), [Data visualization](), [Data Science](), [Open Source]() Tags: [ai](), [data-analytics](), [data-visualization](), [deploy](), [deployment](), [developer-tools](), [dockerignore-usage](), [getting-started](), [heroku](), [news](), [open-source](), [prototyping](), [python](), [streamlit](), [web-applications]() ### AI overview Heroku announces Heroku-Streamlit, a ready-to-deploy template for deploying interactive Streamlit data visualization applications on Heroku. The template combines Heroku's cloud platform with Streamlit's Python framework and includes one-click deployment, sample Uber pickup data, customization options, and manual deployment instructions. ### Source excerpt We're excited to announce the release of Heroku-Streamlit, a template that makes deploying interactive data visualization applications on Heroku simpler than ever before. Streamlit is an open-source app framework built for machine learning and data science projects. This Streamlit App brings together Heroku's scalable cloud platform and Streamlit's intuitive Python-based data application framework. Whether you're [...] The post Introducing Heroku-Streamlit: Seamless Data Visualization appeared first on Heroku. ## HTML Tables with Horizontal Scroll and Sticky Headers DevFeed: [HTML Tables with Horizontal Scroll and Sticky Headers]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2024-10-09T00:00:00Z Content type: tutorial Language: en Sources: [Tania Rascia]() Topics: [HTML](), [Web Development](), [modern web development]() Tags: [container](), [css](), [design](), [dockerignore-usage](), [example](), [headers](), [helps](), [html](), [javascript](), [table](), [tables]() ### AI overview A tutorial on building HTML tables that support horizontal scrolling and sticky headers. It explains why sticky positioning can fail inside an overflow container and presents a table-wrapper height as the solution, producing a vertically and horizontally scrollable datagrid-style view. ### Source excerpt Turns out, creating an HTML table that has both horizontal scroll and fixed headers can be a tricky problem. As another developer said about... ## Farewell from the Reproducible Builds Summit 2023! DevFeed: [Farewell from the Reproducible Builds Summit 2023!]() Original publisher: [Read original article]() Published: 2023-11-02T00:00:00Z Content type: news Language: en Sources: [reproducible-builds.org]() Topics: [reproducible builds](), [reproducibility](), [builds](), [Embedded Systems]() Tags: [adb](), [apache](), [buildroot](), [builds](), [coreboot](), [debian](), [dockerignore-usage](), [fedora](), [germany](), [github](), [linux](), [maven](), [openwrt](), [org](), [reproducibility](), [reproducible-builds](), [security](), [summit](), [systemd](), [ubuntu]() ### AI overview A recap of the seventh Reproducible Builds summit in Hamburg, Germany, covering project updates, reproducibility practices, verification services, filesystem images and containers, package reproducibility, SBOMs, and related discussions. ### Source excerpt Farewell from the Reproducible Builds summit, which just took place in Hamburg, Germany: This year, we were thrilled to host the seventh edition of this exciting event. Topics covered this year included: Project updates from openSUSE, Fedora, Debian, ElectroBSD, Reproducible Central and NixOS Mapping the "big picture" Towards a snapshot service Understanding user-facing needs and personas Language-specific package managers Defining our definitions Creating a "Ten Commandments" of reproducibility Embedded systems Next steps in GNU Guix' reproducibility Signature storage and sharing Public verification services Verification use cases Web site audiences Enabling new projects to be "born reproducible" Collecting reproducibility success stories Reproducibility's relationship to SBOMs SBOMs for RPM-based distributions Filtering diffoscope output Reproducibility of filesystem images, filesystems and containers Using verification data A deep-dive on Fedora and Arch Linux package reproducibility Debian rebuild archive service discussion ... as well as countless informal discussions and hacking sessions into the night. Projects represented at the venue included: Debian, openSUSE, QubesOS, GNU Guix, Arch Linux, phosh, Mobian, PureOS, JustBuild, LibreOffice, Warpforge, OpenWrt, F-Droid, NixOS, ElectroBSD, Apache Security, Buildroot, Systemd, Apache Maven, Fedora, Privoxy, CHAINS (KTH Royal Institute of Technology), coreboot, GitHub, Tor Project, Ubuntu, rebuilderd, repro-env, spytrap-adb, arch-repro-status, etc. A huge thanks to our sponsors and partners for making the event possible: Event facilitation Platinum sponsor If you weren't able to make it this year, don't worry; just look out for an announcement in 2024 for the next event. ## Docker Best Practices - Use .dockerignore DevFeed: [Docker Best Practices - Use .dockerignore]() Original publisher: [Read original article]() Author: Tom Published: 2022-09-11T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [build times](), [context]() Tags: [best-practices](), [build](), [build-times](), [docker](), [docker-build-context](), [docker-build-optimization](), [docker-image-efficiency](), [dockerfile-best-practices](), [dockerfiles](), [dockerignore-usage](), [exclude-files-docker]() ### AI overview This tutorial explains that Docker uploads the entire build context to the Docker daemon during an image build. It recommends using a .dockerignore file to exclude unnecessary sources, test results, and other working-directory files, which can help reduce build times. ### Source excerpt Learn best practices for writing Dockerfiles by using .dockerignore to optimize build times and exclude unnecessary files from the build context. ## Replacing Custom Views with View Binding DevFeed: [Replacing Custom Views with View Binding]() Original publisher: [Read original article]() Author: Jossi Wolf Published: 2020-04-19T12:31:58Z Content type: tutorial Language: en Sources: [Stories by Jossi Wolf on Medium]() Topics: [Code](), [XML](), [Kotlin](), [Boilerplate]() Tags: [android](), [androiddev](), [code](), [custom-view-android](), [dockerignore-usage](), [kotlin](), [view-binding](), [xml]() ### AI overview This tutorial explains how a codebase replaced reusable custom views with Android View Binding when custom rendering was unnecessary. It covers generated binding objects, lifecycle-scoped instantiation, reusable binding extension functions, and passing data models to reusable components. ### Source excerpt How we used View Binding to replace Custom Views In our codebase, we use a lot of custom views for reusability -- but most of the time, a custom view was overkill. Here's how we used View Binding to replace some of our custom views. View Binding 101 If you are not familiar with View Binding yet, here is a great post by Sean McQuillan about it. In short: View Binding is a better alternative over Kotlin Synthetics, findViewById and good old Butterknife. It allows you to access the views in a layout in a type-safe and null-safe way. For each XML layout, View Binding generates a binding object. For a layout fragment_login.xml, you'd get a binding object called FragmentLoginBinding. Instantiating the binding objects requires a bit of boilerplate to make sure it is scoped to the components' lifecycle. We use a delegate class as suggested in this post to make the code cleaner and easier to read. About Our Custom Views We used many custom views for our reusable components. Like this one: https://medium.com/media/0d681c4bb6b7d1f682a84aa2e58801ba/href Custom views are awesome if they are used right, but they bring quite a bit of boilerplate and are harder to maintain then XML layouts. For cases where we don't do any custom rendering, View Binding made more sense to use as we could cut down on the boilerplate. Using View Binding for Reusable Components As View Binding generates a binding object for each layout, the first step for migrating was to create a layout: https://medium.com/media/b9c9bf94e38e1b30923d741f6e85d7c4/hrefPreview of the layout Now for our card_user_data.xml, View Binding generates a CardUserDataBinding.java which we can use. Binding the data First, we need to include the card layout in our fragment's layout. https://medium.com/media/1af56e360407fe6f1eaef366f18e6401/href View Binding will automatically cast the type of the to CardUserDataBinding, so we can use it in a type-safe way. That also means we can reuse those bindings across layouts. Beware t ## Rails Test Basics DevFeed: [Rails Test Basics]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-01-27T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Testing](), [RSpec](), [Development]() Tags: [dockerignore-usage](), [errors](), [factorybot](), [rails](), [rspec](), [skip](), [test](), [testing](), [tests]() ### AI overview A practical guide to classical Rails testing for a project using standard Rails tests instead of RSpec. It covers debugging with byebug, skipping tests, running tests with Rails commands, interpreting a confusing zero-test result, using FactoryBot, and writing assertions. ### Source excerpt More than a decade using RSpec has left me flummoxed in terms of "classical" Rails testing. I'm on a new project built using the Jumpstart application template and all the tests are standard Rails tests so here's a quick recap that I wrote, well, to force myself to step back in time and go "old school". And if you don't like my version then you should really read this. And if you are using Devise for authentication then you really must read this. Making Tests Debuggable The ability to use byebug in a testing context for breakpoints and stepping through code is utterly invaluable. Here's what you need to do for that: Add byebug into a development, test group in Gemfile. Add the line require 'byebug' to the very top of test_helper.rb How Do You Skip a Test? You put the keyword 'skip' at the top of the test that you need to skip. This is equivalent to xit in RSpec. Running Tests The very basic of testing is nothing more than test execution so to run all model tests: rails test test/models/ and to run one file rails test test/models/user_test.rb and to run everything: rails test and to run with verbose mode: rails test -v test/models and to run verbosely and fail on the first test failure: rails test -v -f test/helpers/application_helper.rb and to run just one specific test: rails test test/controllers/labels_controller_test.rb:9 Note: RSpec is very good at running the next test if the line number shifts a bit (example you put in :8 but you added a line so its actually :9). With standard rails test, you get this madness: ❯ rails test test/controllers/projects_controller_test.rb:17 Running via Spring preloader in process 95090 Run options: --seed 52687 # Running: Finished in 0.010622s, 0.0000 runs/s, 0.0000 assertions/s. 0 runs, 0 assertions, 0 failures, 0 errors, 0 skips The 0 runs, 0 assertions, 0 failures, 0 errors, 0 skips can best be interpreted as: Yo! Hoser! I don't know what to do here so I'm going to confuse you deliberately. Ha Haw! Death to Fixtures; Viva La F ## Friday Q&A 2018-06-29: Debugging with C-Reduce DevFeed: [Friday Q&A 2018-06-29: Debugging with C-Reduce]() Original publisher: [Read original article]() Author: Mike Ash Published: 2018-06-29T13:35:00Z Content type: tutorial Language: en Sources: [Mike Ash]() Topics: [debugging](), [C](), [test](), [Shell](), [Code]() Tags: [c](), [code](), [debugging](), [dependencies](), [dockerignore-usage](), [how-to](), [shell-script](), [test](), [transformation]() ### AI overview This tutorial explains how C-Reduce automatically shrinks programs into reduced test cases. It covers reduction passes, scriptable interestingness tests, installation, and a simple C example for isolating a compiler warning or bug. ### Source excerpt Debugging a complex problem is tough, and it can be especially difficult when it's not obvious which chunk of code is responsible. It's common to attempt to produce a reduced test case in order to narrow it down. It's tedious to do this manually, but it's also the sort of thing computers are really good at. C-Reduce is a program which automatically takes programs and pares them down to produce a reduced test case. Let's take a look at how to use it. (Read More) ## 5 Useful Gmail Filters for GitHub Users DevFeed: [5 Useful Gmail Filters for GitHub Users]() Original publisher: [Read original article]() Published: 2015-06-07T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [GitHub](), [email](), [pull-requests]() Tags: [dockerignore-usage](), [email](), [github](), [notifications](), [pull-requests]() ### AI overview A practical tutorial on using Gmail filters to organize GitHub notifications, prioritize assigned issues, and reduce the time spent reviewing email alerts. ### Source excerpt Make your life easier with these ## Top Github Languages for 2013 (so far) DevFeed: [Top Github Languages for 2013 (so far)]() Original publisher: [Read original article]() Published: 2013-08-30T00:00:00Z Content type: article Language: en Sources: [Adam Bard]() Topics: [GitHub](), [Programming](), [BigQuery](), [dataset](), [Open Source]() Tags: [bigquery](), [clojure](), [css](), [data](), [dataset](), [dockerignore-usage](), [github](), [go](), [google](), [groovy](), [haskell](), [perl](), [programming](), [repositories](), [ruby](), [scala](), [shell]() ### AI overview The article analyzes GitHub Archive data queried with Google BigQuery to rank programming languages by the number of repositories created during 2013, comparing the results with the same period in 2012. It discusses notable ranking changes and cautions that the data and query may be inaccurate and are not representative of all programmers or programming. ### Source excerpt I just discovered the Github Archive, a dataset of Github events queryable using Google BigQuery. What fun! So I decided to count how many repositories have been created this year by language.