bookmark_borderTizen SDK on Fedora 26

I recently bought a Samsung Gear S3 which uses Tizen as its operating system.

As I have been trying to improve my development skills, I would also like to develop some app for the watch ( my first thought was something related to Telegram ).

Let’s start with installing the SDK!

Get the SDK from here. Samsung doesn’t officially support anything other than Windows, Mac OS X or Ubuntu but I thought I could give a try to installing it on my Fedora Workstation.

Once I downloaded the installer and tried to run it:

chmod +x web-ide_Tizen_Studio_1.2_usa_ubuntu-64.bin  

There is apparently something not right:
run installer

So some dependencies are missing? let’s install them:

dnf install libgnome qemu-user expect  

install dependencies

Triggering again the installer brought me to this:
OpenJDK not supported

If you follow the link suggested:

java jdk webpage.

Trying to download the JDK will lead you to:

sdk rpm download

Download the 64 bits RPM (after agreeing to the license, of course…)

Now it’s time to install it:

dnf install jdk-8u144-linux-x64.rpm  

oracle jdk installation

Now, to make the Oracle one the prefered JVM:

alternatives --config java  
alternatives --config javac  
alternatives --config javaws  

java alternatives

Now time to check everything is as we want:

java -version  
javac -version  

java version

Now, running the installer again:


First thing it will ask you is to accept the Software License Agreement:
tizen license

Choose where to install the SDK:
tizen sdk location
And… et voilà:
tizen finish installation

Once the installation has finished, it will by default launch the package manager:
tizen package installation
Some of the packages, like the emulator, will need extra permissions:
tizen package sudo
Here is the list of the packages I installed:
tizen packages installed

Everything is ready…:
tizen first launch
Oh oh… seems that we need to fix something manually…

Quick investigation lead me to finding out there is a tool named sdb and apparently is missing a library:
sdb missing library
A quick research on-line lead me here. I don’t really like the solution of installing the Ubuntu library system wide, so I decided to do a small workaround:

mkdir -p /home/marc/Code/SDKs/tizen/ubuntu_libraries  

And I copied from this package the files and into that folder.
Turn to create a file in /home/marc/.local/.bin/tizen with this content:

#!/usr/bin/env bash                                                                                        
export LD_LIBRARY_PATH=/home/marc/Code/SDKs/tizen/ubuntu_libraries  


chmod +x /home/marc/.local/.bin/tizen  

Now I simply need to type tizen and my Tizen Studio will launch:
tizen studio running

WARNING: if you launch the SDK from the menus this will not work. The menu entry will still launch /home/marc/Code/SDKs/tizen/tizen-studio/ide/ You can either modify the menu entry or start the IDE via my launcher

Happy hacking!!!

bookmark_borderSetting up a blog…

So I have been thinking for a while on getting back to blog and I figured that I could try to set something up on my home server.

My resources are really limited so, even though I actually hate the trend, I decided to run my blog on Ghost.

I also wanted to have some sort of isolation on the things that run on my server thus I had two realistic options: docker or running traditional Virtual Machines. Remember I mentioned that my resources were limited? Thus, docker was the chosen option.

I didn’t want to serve the blog straight from docker, so I opted for running a web server in front (although this one is not running on docker 😉 ).


server {  
     listen 80;
     listen 443 ssl;
     ssl_certificate        /etc/letsencrypt/live/;
     ssl_certificate_key    /etc/letsencrypt/live/;

     root /var/www/blog;

     location /.well-known {
          alias /var/www/blog/.well-known;

     location / {
       proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
       proxy_set_header Host $http_host;
       proxy_set_header X-Forwarded-Proto $scheme;
       proxy_pass http://localhost:2368;

This is not a very complex nginx configuration, essentially it’s just a proxy. The most relevant thing might be the use of Let’s Encrypt ( maybe I write something about it some other time).

Now let’s have a look at how to create the container to run ghost.
Why not use the official image? Well, I actually can’t as my home server is ARM based. I did a quick research on-line and found easypi/ghost-arm and kennethlimcp/armhf-ghost. Neither of them suited me properly as the first one doesn’t have much information regarding how it’s built and the second one, even though looks very nice, builds the images based on Debian and their alpine version seems a little bit outdated. Besides, I got to practice a little bit on how to emulate ARM on my workstation :-).

I followed this guide to set up a VM with ARM emulation so I could quickly build my docker images ( ‘quickly’ is really not the right word, the VM is slow ).

I heavily based my work on the official image with slight changes. You can find the end result here.

Right now I am running the blog on a development version of the docker image but I will try to upload the final one to my recently created docker hub repository.

One the image was built, I only needed to run the container:
docker run -d --restart always -v $blog:/var/lib/ghost -e NODE_ENV=production -p 2368:2368 marcdeop/ghost-arm:0-alpine

The first entry of the blog as it’s looking right now…

I haven’t yet found a theme that I really like, this needs further investigation but so far… I am quite happy with the status.