Skip to main content

Jira server Firefox mobile

Make Jira server to deliver the mobile version when using Firefox Mobile.

My use case

I mostly receive Jira notifications by Email, read on my telephone.
When I want to comment the notification from my telephone, I usually choose Firefox Mobile.

Problem

Unfortunately (dunno if it has to do with fortune), Firefox Mobile is not a supported web browser, so that Atlassian has made the choice to deliver the desktop version if the client is the client browses with an unsupported browser.

Solution

I have an Apache reverse proxy in front of my Jira instance: I can force a Redirection to the mobile URL if I match the Firefox Mobile User-Agent.

    ...
    RewriteCond "%{HTTP_USER_AGENT}"   "^Mozilla\/[1-9]\.0 \(Android [1-9]\.0\.0; Mobile; rv:[1-9][1-9]\.0\) Gecko\/[1-9][1-9]\.0 Firefox\/[1-9][1-9]\.0$"
    RewriteRule   "^/browse/(.+)$"  "https://jira.rktmb.org/plugins/servlet/mobile#issue/$1"  [R,L,NE]
    RewriteRule   "^/browse/(.+)#add-comment$"  "https://jira.rktmb.org/plugins/servlet/mobile#issue/$1"  [R,L,NE]
    ...

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: https://issues.jenkins-ci.org/browse/JENKINS-57495 Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs TypeScript Development

Emacs Configuration for Typescript In order to comfortably develop on Node, React or Angular projects with Emacs, TIDE is a good solution. We have TypeScript code highlight (that is the minimum!) and code completion based on the codebase (not only on locally defined and builtins) In order to achieve that: Install Emacs (24+) Install Node Install Typescript (which will provide "tsserver") Install TIDE and some usefull dependencies Configure Emacs to use all those Node is then installed in " /home/mihamina/Apps/node-v12.18.0-linux-x64/bin ": you should add it to your PATH. Installing Typescript is done with: npm install --save typescript @types/browserify After that, "tsserver" will be in " /home/mihamina/node_modules/.bin " Then comes the installation of TIDE: With the Emacs package manager, M-x package-install , install "tide". Do the same for "web-mode", "flycheck", "company" "js2-mode" and "