This article will teach you how to use Git when you want to deploy your application. While there are many ways to use Git to deploy our application, this tutorial will focus on the one that is most straightforward. I assume you already know how to create and use a repository on your local machine.
I was following the tutorial to setup a Git server on Raspberry Pi1. Then I continued to setup automatic deployment with Git from above article 2.
The setup was going well, until I tried to commit new changes and then pushed it to the Pi server. I got a bunch of errors produced by post-receive hook script, similar like these:
remote: error: unable to unlink old 'filename' (Permission denied)
This month, I’ve got a chance to try Raspberry Pi device. I’ve got the Pi 2 model B from Jakarta Notebook offline store in Semarang. I am going to make it as a home server (actually workspace server 😀 ). Right now, there’s a router here that is connected to internet. But unfortunately, I don’t have sufficient LAN cable to connect Pi to the router. So, I make use of a Ralink USB WiFi adapter for Pi to connect. And actually, set it up via command line is not hard as I thought.
Recently, Mozc, Japanese input methode engine by Google become more popular, compared with Anthy, so does fcitx upon ibus. In the official repository of Fedora, there’s fcitx-anthy, but unfortunately, there’s no fcitx-mozc yet.
Here I will wrap up the workaround for those who want to use fcitx-mozc in Fedora 23. Be careful, that you take responsible of all risks that may happen, as it may lead to dependency hell. Basically, you are going to get favor from OpenSUSE as it has provided fcitx-mozc. You need 3 packages to be downloaded: fcitx-mozc, mozc, and mozc-gui-tools.
Download those 3 packages from https://software.opensuse.org/421/en, select “more version” link, under Direct install button, there you can choose the package version and system architecture, whether 32 bit or 64 bit
Remove ibus-mozc and mozc if already installed via command sudo dnf remove ibus-mozc mozc
Install fcitx if it’s not installed yet, sudo dnf install fcitx kcm-fcitx
Then install the previously downloaded packages via console. sudo dnf install fcitx-mozc.rpm fcitx-gui-tools.rpm mozc.rpm
Once it successfully installed, you can set the default input method to fcitx-mozc via system settings.
at the left list, you may have to uncheck the option “Only show the current language” to show Mozc and move to the right. Apply the settings and just relogin to Plasma to take effect and see the fcitx icon at the taskbar below.
I’ve just successfully connected KDE Connect in my Fedora 23 KDE to Android. Just before, I thought it didn’t work in Plasma 5 or broken in Fedora. Since it could not find the Android devices, although they have KDE Connect app installed. But actually, it’s just blocked by firewall config of Fedora.
According to KDE Wiki, the ports for kde-connect need to be opened, i.e 1714-1764. I’ve never thought that such essential part of the desktop environment would be blocked by firewall. So I had no idea to touch firewall config at all. It was until I found a discussion on Reddit about the same problem I had. A user pointing out about Fedora’s firewall that seems blocking kde-connect. But I could see the ports either TCP or UDP have been opened and listened in the firewall config. But then I found out that kde-connect was unchecked in the Services list.
It means that the firewall didn’t allow kde-connect to access the ports it needs. Then I just had to check it, typed password, and voila… my Android device has been found by kde-connect. So now, I can enjoy syncing Android to KDE and playing some stuffs it has.
Here, i post a brief tutorial how to connect my Kubuntu desktop to OpenVPN server with the default connection manager. Previously, I have set up OpenVPN server in just one click. And after the server is up, it automagically created several OpenVPN config files for the client. I fetched them with scp.
Have a look at this screenshot. It’s my experience when installed OpenWRT system image via command line. I did that way because it’s almost broken and I thought it bricked. But fortunately, it could be connected via SSH, and I reflashed the image with mtd command, after I scp-ed the binary image.