Developing Java applications accessing data from Solr [http://lucene.apache.org/solr/] is easier with spring-data-solr [https://docs.spring.io/spring-data/solr/docs/current/reference/html/]. You can just use Repository interfaces, auto generated findBy... methods or @Query [https://docs.spring.io/spring-data/solr/docs/current/reference/html/#repositories.query-methods.
As I spent some time trying to get this to work, so I write my steps down, as personal knowledge base. Docker One of the most useful docker containers out there is jwilder's nginx-proxy [https://github.com/jwilder/nginx-proxy]. There is a companion docker container for let's encrypt [https://github.
Within the last years developing, prototyping and designing software projects I collected a set of best practices for setting up and developing software projects. I wrote down a more general overview in my article about about defining key factors for successful software development [https://paul.wellnerbou.de/2016/09/19/
Update: Unfortunately this solution is not working any more with recent versions of Firefox and FirefoxDriver. I spent some time currently to automate integration tests and webtests, mainly using spock [http://spockframework.org/] and, for the web test part, geb [http://www.gebish.org]. Unfortunately I did not find any
A while ago I was asked about my opinion of key factors for successful and quality software development. There are a few lists published from more or less famous programmers, like this excellent collection from Jens Rantil [https://www.quora.com/What-are-the-best-kept-secrets-of-great-programmers/answer/Jens-Rantil] or this from computer game development
As announced earlier [https://paul.wellnerbou.de/2015/07/13/git-jira-log-1-0-released/], the first public version of the Git Changelog Plugin [https://wiki.jenkins-ci.org/display/JENKINS/Git+Changelog+Plugin] for Jenkins [http://jenkins-ci.org/] is now released and available via Jenkins' offical update site. I got some inspiration from Oleg
While creating a proof of concept of a new, cloud based environment of a big news platform, we used chronicreplay [https://github.com/paulwellnerbou/chronicreplay] to test the behaviour of the new environment under a realistic load, similar to the productive system. chronicreplay replays Apache (or any other) log files
I am working on a library [https://github.com/paulwellnerbou/git-jira-log] and a jenkins plugin [https://github.com/paulwellnerbou/git-jira-log-jenkins-plugin] doing this right, but until then, here is a shell script which creates the URL to a JIRA filter containing the tickets mentioned in all commit messages between the two
JGit [https://eclipse.org/jgit/] does not support getting commits between annotated tags [https://git-scm.com/book/en/v2/Git-Basics-Tagging#Annotated-Tags] (or any revision and an annotated tag) as you might expect. Following code will work perfectly with commit hashs and branch identifiers: public Iterable
getJGitLogBetween(final String rev1,
Bootstrap's standard CSS for forms and inputs does support more than one input elements and labels in one line using bootstrap's CSS class form-inline [http://getbootstrap.com/css/#forms-inline]. You can use Bootstrap's grid system to align your input elements and labels, if you want a more complex, but still
Chrome beta for Linux is supporting HiDPI scaling now [https://code.google.com/p/chromium/issues/detail?id=143619], but Brackets [http://brackets.io/], which is based on Chromium, does not yet. If you don't want to wait, you can use Brandon Bertelsen [http://www.bertelsen.ca/]'s extension ui-too-small
Imagine following, quite common scenario: We have a scss file defining standard font and text styles (font.scss), another scss file which defines link styles ( links.scss) which uses variables and definitions of font.scss and a third scss file which defines styles for form elements (form.scss), which depends
In Git Minutes #32, Adam Spiers talked [http://episodes.gitminutes.com/2015/03/gitminutes-32-adam-spiers-on-git-deps.html] about git-deps [https://github.com/aspiers/git-deps], which was interesting for me. We don't cherry pick usually nor backport commits, but I analyse bugs trying to find out when and with which the buggy code