Tanzawa blogging system / indieweb ready

[rmdes]

@timconsidine I used to blog since years with IDNO/WithKnown, it's a ready to use "Indieweb" blog engine, comes ready with indieweb protocols, specs, post types, syndication to social media and ability to use our own blogs to reply/like/subscribe from each participant blog. (check indieweb.org wiki)

But I'm having issues with Known for a while and I suspect the project is not actively evolving, so I wanted to change and Tanzawa is even better in this "ready to use" indieweb approach, the project is active and it would be a great addition to cloudron

[rmdes]

I'm doing posts here https://forum.cloudron.io/category/104/help-wanted-or-offered
I'm at the last step to have this running but can't have my start sh to run

[rmdes]

Alright...got it working : https://blog.rmendes.net/

i'm still exploring the features and testing but I should be able to publish a gitlab/gihub repo with my docker/cloudron ready image in the next few days..

[timconsidine]

@rmdes Yay !
looks nice

[rmdes]

My cloudron package is running since a few days and I'm quite happy with it
my next steps should be :

• making the package more alligned with cloudron best practice (have code a data separated)
• talk with upstream to see how we could use progreSQL and Redis addons from cloudron
• finetune some details like a proper logo, description etc..

then it should be ready to be shared with the community

[micmc]

@rmdes Wow, nice work folk!
I believe it's a very good thing to have Cloudron connected with IndieWeb which contributes greatly to slightly rethink how we publish any content on the Web so people can somehow get the Internet back, at least for communities, and control in their own hands to use freely and dispose of their content at will. It also fits greatly with the so many possibilities in that sense, offered with Cloudron.

For one to grasp the full idea and 'philosophy' that goes along with Tanzawa, which is not just "another blogging platform", and IndieWeb it is important to get a little bit documented however, if you believe in freedom for all to use information technologies I promise you will not waste your time and quickly see all the potential openness in many ways this can have.

Kudos for your will and efforts to make this available to Cloudron community and users.

[rmdes]

@micmc the moment I stumbled on the #indieweb wiki/Irc and community I knew I had found the kind of internet I want to help building, it also connected me back to early 2003 when the internet was very different and blogs were powering a lot of different conversations online.

I miss that time and after a few years of using Known (another indieweb ready blog engine) but also testing the WP and Drupal Indieweb implementation I'm convinced that to make it work, the access to deploying indieweb tools should almost be one-click deploy instead of everyone's cooking their own implementation in their corner, I believe that for this to take off and for people to actually use the built-in "social network" already part of the open web, we need to make it really easy to join, deploy and use.

In many ways the indieweb concepts are so simple and elegant that for many people that don't remember or never met the web before the platforms, it all feels really abstract and complicated, i want to help to change that !

[rmdes]

This is the current state of my cloudron package : https://github.com/rmdes/tanzawa

• git clone
• confirm docker login
• docker build -t username/tanzawa:yourtag . --no-cache
• docker push username/tanzawa:yourtag
• cloudron install --image username/tanzawa:yourtag --no-wait

OR if update

• cloudron update --image username/tanzawa:yourtag --no-wait --app your.cloudron.domain

[rmdes]

issues I'm having :

the env.sample define an SQLITE database at the root of the image, so I tried to symlink it to /appa/data so that the DB would be backedup but above all writable, the problem is that no matter what I tried, It never worked, in the end my current image has the tanzawa code and the data in the same /app/data space and the only part that works in /app/code is the virtualenv environment used to build the image in the first place.

so the current state of the package is not final, ideally, the entire code should live inside /app/code/ and only staticfiles, media and the SQLite database should be in /app/data/

I tried to find other python packages using sqlite but could find one, so my next step I was thinking of adapting the way the .env defines the variables to build in a way that is closer to how other cloudron packages load environments variables.

I'm also researching for a way to define the sqlite db not from a URL but from a PATH instead, so that I could simple use /app/data/ directly.

if anyone has advice on how to move this forward, I'm taking it

[timconsidine]

@rmdes wish I knew the answers
but well done on getting to where you have
I will look for time to try it out

[robi]

@rmdes where is the repo so people can take a look?

Sqlite is a single file DB, so any references to it should be path based (full path: /app/data/sqlite.db).

[timconsidine]

@robi https://github.com/rmdes/tanzawa

[rmdes]

SQL path : Yes I have finally made it ! thanks to this https://django-environ.readthedocs.io/en/latest/

but thanks @robi

But I still have a few things blocking me, like, tanzawa need to know the domain it is installed into
and this is configured in the .env file but the thing is I don't want people to have to clone the github repo, add their domain, build, push and install to their cloudron

Ideally I need to add something so that the domain variable is passed to the .env file before it runs the first DB migration (which create the sql file the first time and apply migration the second time)

Also now in the current state of my dockerfile, I have managed to put all the code in /app/code and only the .env and the staticfile & micropub media folder in /app/data/ which is exactly what I wanted...

So this is moving forward..

[rmdes]

You can try it with : cloudron install --image buzzworkers/tanzawa:7 --no-wait

and then cloudron update --image buzzworkers/tanzawa:8 --no-wait --app your.domain.com

why these two tags ?

Because I have not figured out how to do the steps of the README.md (tanzawa repo)
in one single shot and directly boot the python server.

So tag number 7 setup the database correctly (but then stay in migration loop)
and tag8 comment the migration parts (start.sh) so that the server boots

using the web terminal to python3 /app/code/apps/manage.py createsuperuser
to create your admin user.

Dashboard is at your.domain.com/a/
Wordpress import at your.domain.com/wordpress

I would love to have this last steps of the setup completely automated but I lack know-how

[rmdes]

Another thing I would like to improve : it seems the sql file is run by root (at least the file is owned by root) I don't think it's a good idea/best practice, so I'm wondering if by running the last command of the start.sh, the python server, with gosu cloudon:cloudron would solve this..

[rmdes]

I'm almost done with it !

• got the sqlite database in /app/data/
• .env file symlink (but can't write to it yet??!!)
• /app/code contains all the code and packaging env

Issues

• I'm not sure what's happening this weekend but my container kept starting in migration loop
• if I recovery into the container and start the python server, all is fine, connected, writable
• when I restart, instead of skipping the steps of migration and start the server, it bootloop in migration, while saying there is no migration to do (obviously, everything is like 1 step before working....Grrrr)

[robi]

@rmdes said in Tanzawa blogging system / indieweb ready:

• when I restart, instead of skipping the steps of migration and start the server, it bootloop in migration, while saying there is no migration to do (obviously, everything is like 1 step before working....Grrrr)

Maybe the migration needs to write somewhere for indicating completion.

[rmdes]

@robi Actually there is no migration apply, look here : https://github.com/jamesvandyne/tanzawa/issues/179

[rmdes]

i've learned a few stuff packaging go-ssb-rooms, will start from scratch for Tanzawa and hopefully have it working smooth

[rmdes]

In this example I think there are some ideas that I can take for Tanzawa, mainly
getting the domain used by cloudron into a variable, which would allow the docker image to be agnostic and not tied/built to a specific domain (mine in my case)