| Filter | Description | Example |
|---|---|---|
| allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
| intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
| inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
| allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
| intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |
| /* | |
| * `getip.c' | |
| * | |
| * Copyright (C) 2015, 2016 Lukas Himsel <lukas.himsel@web.de> | |
| * | |
| * This program is free software: you can redistribute it and/or modify | |
| * it under the terms of the GNU General Public License as published by | |
| * the Free Software Foundation, either version 3 of the License, or | |
| * (at your option) any later version. | |
| * This program is distributed in the hope that it will be useful, |
| #!/bin/sh | |
| # Written by Lukas Himsel <lukas.himsel@web.de> | |
| # | |
| # -> backup your complete linux system <- | |
| # | |
| # Variables: | |
| # BACKUP_DEVICE is the *mounted* harddrive for the backup | |
| # BACKUP_DATE is the actual date and it's used to create a folder | |
| # with the actual date | |
| # |
https://github.com/techqueria/website
Techqueria is one of the largest communities of Latinx professionals in the tech industry. We build Latinx-centered spaces that revolve around career advice, technical talks, mentorship, open jobs, upcoming events/conferences, speaking opportunities, and open-source. We come from all walks of life and believe that the diversity of our community is the most reliable asset we have.
Sammlung von Lizenz-Schildern (Badges) für die README-Datei deines Projekts. Diese Liste enthält die meist verbreiteten Open Source und Open Data Lizenzen. Kopieren und fügen Sie den Code unter den Badges einfach in Ihre Markdown-Dateien ein.
- Die Schildchen sind mit Shields.io gemacht.
- Diese Badges ersetzen nicht vollständig die Lizenzinformationen dein Projekt, sie sind nur Embleme für das README, so dass der Nutzer die Lizenz auf den ersten Blick sehen kann.
- 🇺🇸🇬🇧 This list in english
- 🇫🇷 Cette liste en français
| 1. composer require server --dev | |
| symfony/process (v4.1.6) | |
| symfony/web-server-bundle (v4.1.6) | |
| Symfony operations: 1 recipe (418553c035c1340534830260d374a8d2) | |
| - Configuring symfony/web-server-bundle (>=3.3): | |
| 2. composer require make --dev | |
| Using version ^1.8 for symfony/maker-bundle |
The absolute requirement is that these must be binaries that could go into /usr/bin one day. No python, ruby or js stuff. Not that dynamic languages are bad/evil, but I think system utilities should be binaries. I also think it's interesting that people are writing replacements in Go/Rust/Other that rethink some unix legacy. Replacement doesn't mean better in all cases. I just think it's an interesting time but also a good measure of what these compiled languages can handle/tackle/address. Will we see larger and more impressive CLIs? Or will the feature sets be about the same but the quality/stability/safety be better?
It's going to be reductive to explain some of these tools in one line.
| <head> | |
| <meta charset="utf-8"> | |
| <meta http-equiv="X-UA-Compatible" content="IE=edge"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0"> | |
| <title>{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}</title> | |
| <link rel="canonical" href="{{ site.url }}{{ site.baseurl }}{{ page.url }}" /> | |
| <meta name="description" content="{% if page.excerpt %}{{ page.excerpt | strip_html | strip_newlines | truncate: 160 }}{% else %}{{ site.description }}{% endif %}"> |
Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
- The badges do not fully replace the license informations for your projects, they are only emblems for the README, that the user can see the License at first glance.
Translations: (No guarantee that the translations are up-to-date)