Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>try the BFG instead of git filter-branch...</h2> <p>You can use a <em>much</em> more friendly substitution format if you use <a href="http://rtyley.github.io/bfg-repo-cleaner/" rel="nofollow">The BFG</a> rather than <code>git-filter-branch</code>. Create a <code>passwords.txt</code> file, with one password per line like this:</p> <pre class="lang-bsh prettyprint-override"><code>PASSWORD1==&gt;xXxXx # Replace literal string 'PASSWORD1' with 'xXxXx' ezxcdf\fr$sdd%==&gt;xXxXx # ...all text is matched as a *literal* string by default </code></pre> <p>Then <a href="http://rtyley.github.io/bfg-repo-cleaner/#usage" rel="nofollow">run the BFG</a> with this command:</p> <pre><code>$ java -jar bfg.jar -fi '*.php' --replace-text passwords.txt my-repo.git </code></pre> <p>Your entire repository history will be scanned, and all <code>.php</code> files (under 1MB in size) will have the substitutions performed: any matching string (that isn't in your <em>latest</em> commit) will be replaced.</p> <h2>...no escaping needed</h2> <p>Note that the only bit of parsing the BFG does with here with the substitution file is to split on the '<code>==&gt;</code>' string - which probably <em>isn't</em> in your passwords - and all text is interpreted literally by default.</p> <p>If you want to be even more concise, you can drop the '<code>==&gt;</code>' and everything that comes after it on each line (ie, <em>just have a file of passwords</em>) and The BFG will replace each password with the string '<code>***REMOVED***</code>' by default.</p> <p>The BFG is typically <a href="http://rtyley.github.io/bfg-repo-cleaner/#speed" rel="nofollow">hundreds of times faster</a> than running <code>git-filter-branch</code> on a big repo and the options are tailored around these two common use-cases:</p> <ul> <li>Removing <strong>Crazy Big Files</strong></li> <li>Removing <strong>Passwords, Credentials</strong> &amp; other <strong>Private data</strong></li> </ul> <p><em>Full disclosure: I'm the author of the BFG Repo-Cleaner.</em></p>
    singulars
    1. This table or related slice is empty.
    1. POgit-filter-branch to remove strings, but where strings contain $ ' \ and other characters
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRoberto Tyley
    1. USRoberto Tyley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POgit-filter-branch to remove strings, but where strings contain $ ' \ and other characters
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO`*.php` should be quoted, it seems: `'*.php'`
      singulars
      1. PO
      1. USfooquency
    2. COOn a quad-core machine, with 800 strings and a 500MB repository, this seems to be much slower than git-filter-branch, taking 5 minutes to get to 1%. Is that to be expected with this volume?
      singulars
      1. PO
      1. USfooquency
    3. CO@fooquency - thanks for that speed test, very interesting to me - literally the first time I've heard of the BFG being slower than git-filter-branch! It could be that 800 strings is quite a lot to match against- could you time a couple of test runs with an identical setup but just a single password, and then repeat with a few more? It's best to run from a fresh copy of the repo each time, so it's probably worth taking a zip of a fresh copy of your repo, and then unzipping a fresh copy for each run. I'll try to recreate the experiment with a repo of similar size (eg the linux kernel)
      singulars
      1. PO
      1. USRoberto Tyley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload