recentpopularlog in

kme : searchandindex   102

« earlier  
Elasticsearch integration | GitLab
Note that you have to have a paid (at least "Starter") license for the Elasticsearch options to even show up in the Admin Area. It doesn't work to just stick some config options in /etc/gitlab/gitlab.rb and 'gitlab-ctl reconfigure'. :-(

<code class="language-bash"># Create empty indexes
sudo gitlab-rake gitlab:elastic:create_empty_index

# index personal snippets
sudo gitlab-rake gitlab:elastic:index_snippets
</code>
gitlab  gitlab-ee  elasticsearch  searchandindex  webmaster  sysadmin  solution 
10 weeks ago by kme
Elasticsearch settings in /etc/gitlab/gitlab.rb not used/mentioned/synced (#1581) · Issues · GitLab.org / GitLab · GitLab
You can't enable Elasticsearch just by putting these in /etc/gitlab/gitlab.rb. You actually have to have a ("Starter" or above) license.

<code class="language-ruby">## ElasticSearch (EE only)
# gitlab_rails['elasticsearch_enabled'] = false
# gitlab_rails['elasticsearch_host'] = "localhost"
# gitlab_rails['elasticsearch_port'] = 9200</code>
gitlab  elasticsearch  searchandindex  solution 
10 weeks ago by kme
ElasticSearch configuration via `gitlab.rb` (#3457) · Issues · GitLab.org / omnibus-gitlab · GitLab
Not a problem I have, just interesting. As of GitLab 12.5.something, you have to enable and configure Elasticsearch through the "Admin Area," and you have to have an active (paid) license.
gitlab  configuration  searchandindex  elasticsearch  interesting 
10 weeks ago by kme
Hardware | Elasticsearch: The Definitive Guide [2.x] | Elastic
A machine with 64 GB of RAM is the ideal sweet spot, but 32 GB and 16 GB machines are also common. Less than 8 GB tends to be counterproductive (you end up needing many, many small machines), and greater than 64 GB has problems that we will discuss in Heap: Sizing and Swapping.


Interesting node about the I/O scheduler used on a system with SSDs:
Check Your I/O Scheduler

If you are using SSDs, make sure your OS I/O scheduler is configured correctly. When you write data to disk, the I/O scheduler decides when that data is actually sent to the disk. The default under most *nix distributions is a scheduler called cfq (Completely Fair Queuing).

This scheduler allocates time slices to each process, and then optimizes the delivery of these various queues to the disk. It is optimized for spinning media: the nature of rotating platters means it is more efficient to write data to disk based on physical layout.

This is inefficient for SSD, however, since there are no spinning platters involved. Instead, deadline or noop should be used instead. The deadline scheduler optimizes based on how long writes have been pending, while noop is just a simple FIFO queue.

This simple change can have dramatic impacts. We’ve seen a 500-fold improvement to write throughput just by using the correct scheduler.
searchandindex  sysadmin  elasticsearch  architecture  systemrequirements  performance 
10 weeks ago by kme
mchaput / whoosh / wiki / Home — Bitbucket
Whoosh is a fast, featureful full-text indexing and searching library implemented in pure Python. Programmers can use it to easily add search functionality to their applications and websites. Every part of how Whoosh works can be extended or replaced to meet your needs exactly.
python  fts  fulltextindex  searchandindex  purepython  library 
10 weeks ago by kme
A (slightly) simpler command-line Spotlight search
Any qualified Spotlight query should be usable with "-interpret", so go ahead with
<code class="language-bash">mdfind -interpret "kind:image flash:1 modified:<=1/1/08 ex-girlfriend"</code>
to find those late-night pictures of last year's special someone.
macos  spotlight  metadata  mdfind  commandline  shellscripting  terminal  searchandindex  tipsandtricks  alternativeto  find 
september 2019 by kme
Where? - BrettTerpstra.com | http://brettterpstra.com/
For people who spread bash functions and aliases across multiple sourced files and then can’t track down where they defined them.
bash  shellscripting  searchandindex 
october 2018 by kme
slocate - Index of /files
I thought I needed this old version to use https://github.com/WojciechMula/locatedb, but nope. I needed the GNU Findutils version of 'locate'.
locate  locatedb  slocate  searchandindex  deadsite 
december 2017 by kme
Finding Files from the Command Line
At it’s most basic level, mdfind is used as follows:

mdfind -name FileName

For example, to find all appearances of “Photo 1.PNG” the command would be:

mdfind -name "Photo 1.PNG"

Because mdfind is like Spotlight, it can also be used to search the content of files and folders for a specific file. To find all documents containing someones name could be done as follows:

mdfind "Will Pearson"
finder  spotlight  commandline  findingthings  searchandindex  cli  mac  osx  tipsandtricks  solution 
july 2017 by kme
Search multiple files with :vimgrep
Ctrl+R, / - insert the last search pattern at the insertion point
vim  tutorial  grep  searchandindex  video  howto 
march 2016 by kme
branch - How can I search Git branches for a file or directory? - Stack Overflow
git log will find it for you:

% git log --all -- somefile

commit 55d2069a092e07c56a6b4d321509ba7620664c63
Author: Dustin Sallings <dustin@spy.net>
Date: Tue Dec 16 14:16:22 2008 -0800

added some file
% git branch --contains 55d2069
otherbranch

Supports globbing, too:

% git log --all -- '**/my_file.png'

The single quotes are necessary (at least if using the bash shell) so the shell passes the glob pattern to git unchanged, instead of expanding it (just like with Unix find).
git  incantation  maybesolution  searchandindex  devel 
january 2015 by kme
About Google Search History - Accounts Help [https://support.google.com/]
It's not in the account settings. It's not in the privacy settings. It's not in the Dashboard. It's in the help. And then you have to scroll to the bottom for a link to a separate web site.

https://www.google.com/history/optout
fuckyougoogle  searchhistory  searchandindex  google  annoyance  privacy 
july 2014 by kme
« earlier      
per page:    204080120160

Copy this bookmark:





to read