I am very happy to announce next release 0.7 of Puffin. It’s been a while since the last one, but there are many exciting features.
First of all Puffin now supports backup & restore using volume-backup. Before the operation, application needs to be stopped, in order to prevent any data inconsistency. Due to its simplicity, all applications support it out of the box.
Second notable feature is HTTPS support. It can be activated in app settings. Under the hood it uses Let’s Encrypt to generate individual free certificates.
Finally there are two new important apps that I am using daily on Puffin:
- Nextcloud – a free and open-source Dropbox on steroids,
- Mastodon – a decentralized, open source social network.
In the future i hope to keep more regular and frequent release cycle.
I presented a short talk about Puffin in Decentralised Internet developer room at FOSDEM 2017.
Here’s the full video (there’s some technical glitch, audio is shifted a bit, sorry for that):
Please let me know what do you think in the comments.
I made a short Puffin presentation during Docker Paris Meetup on 21 Jan 2016. Now it’s available online: video and slides.
I am happy to announce Puffin, a project I have been working on since December.
The idea behind it is to create lightweight web application catalog based on Docker containers, offering the users smooth experience à la mobile app store.
The reason I think it’s interesting is that containers allow packing hundreds of relatively well isolated applications on a single server, which could bring the price of hosting them to almost zero. In addition easy-to-use orchestration technology lets developers easily describe complex applications in terms of microservices.
The whole thing is free / open source and I am hoping to build a small community around it – see README and CONTRIBUTING for details.
Initially I wanted to write a detailed tutorial based on what I did a couple of months ago, but it turns out it’s no longer necessary. Docker Machine lets you configure your own server using a single command:
docker-machine create -d generic --generic-ip-address [ip] \
--generic-ssh-user [user] --generic-ssh-key ~/.ssh/[key] [name]
– [name]: how you’d like to call your server in Docker
– [ip]: public IP address of your server
– [user]: user login on your server
– [key]: user private key, for example id_rsa or a key file generated by your hosting service
You may also need to update your server’s firewall configuration by opening port 2376 for Docker daemon, along with any other ports the application is using (e.g. HTTP 80).
Now you can activate your server in Docker:
eval "$(docker-machine env [name])"
and you can run any docker image on it, for example nginx (adjust host port number as necessary):
docker run --name nginx1 -d -p 80:80 nginx
Now visit your server in a web browser and you should see familiar “Welcome to nginx!” page.
A while ago I have closed my Facebook and Linkedin accounts. These services were simply not bringing me any value. Apart from that, I don’t like the way they operate by gathering as much data about me as possible (for example when you install an App on your phone, it tries to upload your entire address book with names, phones and emails to a remote server) and manipulating what they show to you (payment-driven newsfeed, targeted ads).
It doesn’t mean that I’ve given up social networking altogether though. I am following very interesting federated social networking standardisation initiative at W3C Social Web Working Group, chaired by Tantek Çelik (of Indie Web Camp) and Evan Prodromou (of pump.io).
For my part after unsuccessfully trying to deploy my own pump.io, I joined Diaspora* – you can find my profile here.