Hello everyone,

My name is Bram Wiepjes and I am the founder of Baserow (https://baserow.io) which is an open source no-code database tool and Airtable alternative.

First of all I wanted to tell that Cloudron is an amazing platform! This is the first time that I worked with it, but it is just great! The ease of use, stability, addons and low learning curve make it a fantastic product and I have become a fan.

As a fun weekend side-project I decided to make a Baserow Cloudron app. My initial version can be found here https://gitlab.com/bramw/baserow/-/merge_requests/154 and I would love for people to test it out and review the code. All feedback is welcome and would be much appreciated.

Even though this version works, tested it on Cloudron 6.1.2, there are a couple of issues that I ran into. Baserow depends on Redis version 5 because it uses Django Channels 3. The Cloudron documentation mentioned that the Redis addon installs version 5, but it was always version 4 for me. I solved this by installing Redis 5 locally in the Docker image which is fine for now because the state doesn't necessarily needs to be persistent.

Baserow exists of a backend and web-frontend which communicates only via a REST API and Web Socket with each other. Is there a possibility to to split the backend and web-frontend into two different images? Right now I've combined them into one image. If that is not possible, is it possible to do two health checks? One for the backend and one for the web-frontend?

Lastly, it would be great to get listed in the App Store once this version is stable.

Best,
Bram

Hello everyone, my name is Bram Wiepjes and I am the founder of Baserow. I have created a Baserow Cloudron app. More information can be found here: https://forum.cloudron.io/topic/4389/baserow-cloudron-app.

Thanks everyone for the warm welcome and for the info.

For now it is okay if Redis doesn't keep the persistent state, so we can use the one that is installed within the Basero app image. Would be nice to use the Cloudron addon in the future once Redis 5 is fully supported. Once the Docker healthcheck is supported we can use that.

Looking forward to your feedback!

@doodlemania2 A default user is not created after installation. One could be created via the command line /app/code/env/bin/python /app/code/baserow/backend/src/baserow/manage.py createsuperuser or via the signup page. The first user that signs up via the signup page is automatically getting staff/admin rights.

@girish Apologies for my super late response. I don't check the Cloudron forum that often, but luckily @tomershivani reached out to me via email notifying me about your question. I would love to have Baserow in the Cloudron app store. I am not sure which steps I exactly need to make. Is there a documentation page about this? Or is it just a matter of creating a new repo on git.cloudron.io containing the files that now live here https://gitlab.com/bramw/baserow/-/tree/develop/deploy/cloudron, add automated tests and you will do the rest? Would love to learn a bit more about this process and help with the automated tests would be much appreciated.

This will work for my use case. Thanks!

@nikosgpet Hi @nikosgpet, thanks! I am glad that you like Baserow. The PostgreSQL server is not installed in the Cloudron app. We use the Cloudron PostgreSQL addon, which runs in a different kubernetes pod. In the terminal, you should be able to execute PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} to access the PostgreSQL database.

@timconsidine Glad to hear that it now works for you!

@doodlemania2 Are you looking for a default username and password of Baserow?

@girish Apologies for my super late response. I don't check the Cloudron forum that often, but luckily @tomershivani reached out to me via email notifying me about your question. I would love to have Baserow in the Cloudron app store. I am not sure which steps I exactly need to make. Is there a documentation page about this? Or is it just a matter of creating a new repo on git.cloudron.io containing the files that now live here https://gitlab.com/bramw/baserow/-/tree/develop/deploy/cloudron, add automated tests and you will do the rest? Would love to learn a bit more about this process and help with the automated tests would be much appreciated.

@timconsidine Glad to hear that it now works for you!

@doodlemania2 A default user is not created after installation. One could be created via the command line /app/code/env/bin/python /app/code/baserow/backend/src/baserow/manage.py createsuperuser or via the signup page. The first user that signs up via the signup page is automatically getting staff/admin rights.

@doodlemania2 Are you looking for a default username and password of Baserow?

@nikosgpet Hi @nikosgpet, thanks! I am glad that you like Baserow. The PostgreSQL server is not installed in the Cloudron app. We use the Cloudron PostgreSQL addon, which runs in a different kubernetes pod. In the terminal, you should be able to execute PGPASSWORD=${CLOUDRON_POSTGRESQL_PASSWORD} psql -h ${CLOUDRON_POSTGRESQL_HOST} -p ${CLOUDRON_POSTGRESQL_PORT} -U ${CLOUDRON_POSTGRESQL_USERNAME} -d ${CLOUDRON_POSTGRESQL_DATABASE} to access the PostgreSQL database.

This will work for my use case. Thanks!

I have a quick follow up question. Is it possible for Cloudron to generate a unique secret key and provide that as environment variable? Baserow depends on a secret key to create password reset and invite tokens, but this needs to be unique value for each installation. Otherwise if everyone uses the same key, it will become possible to create password reset tokens which is a security issue.

Thanks everyone for the warm welcome and for the info.

For now it is okay if Redis doesn't keep the persistent state, so we can use the one that is installed within the Basero app image. Would be nice to use the Cloudron addon in the future once Redis 5 is fully supported. Once the Docker healthcheck is supported we can use that.

Looking forward to your feedback!

Hello everyone, my name is Bram Wiepjes and I am the founder of Baserow. I have created a Baserow Cloudron app. More information can be found here: https://forum.cloudron.io/topic/4389/baserow-cloudron-app.

Hello everyone,

My name is Bram Wiepjes and I am the founder of Baserow (https://baserow.io) which is an open source no-code database tool and Airtable alternative.

First of all I wanted to tell that Cloudron is an amazing platform! This is the first time that I worked with it, but it is just great! The ease of use, stability, addons and low learning curve make it a fantastic product and I have become a fan.

As a fun weekend side-project I decided to make a Baserow Cloudron app. My initial version can be found here https://gitlab.com/bramw/baserow/-/merge_requests/154 and I would love for people to test it out and review the code. All feedback is welcome and would be much appreciated.

Even though this version works, tested it on Cloudron 6.1.2, there are a couple of issues that I ran into. Baserow depends on Redis version 5 because it uses Django Channels 3. The Cloudron documentation mentioned that the Redis addon installs version 5, but it was always version 4 for me. I solved this by installing Redis 5 locally in the Docker image which is fine for now because the state doesn't necessarily needs to be persistent.

Baserow exists of a backend and web-frontend which communicates only via a REST API and Web Socket with each other. Is there a possibility to to split the backend and web-frontend into two different images? Right now I've combined them into one image. If that is not possible, is it possible to do two health checks? One for the backend and one for the web-frontend?

Lastly, it would be great to get listed in the App Store once this version is stable.

Best,
Bram