Baserow Cloudron app - Airtable alternative

[timconsidine]

@bruno sure

Maybe best is to visit https://github.com/bram2w/baserow/blob/master/docs/guides/installation/install-on-cloudron.md

That has a tutorial on installing to Cloudron
I think I did it slightly different, but as that comes from @bram, best to start with that.

In general, installing a custom app package that someone else has made (still beyond me to make one myself) is fairly simple. Article above covers it.

• ensure you have Docker Desktop installed LOCALLY (not server)
• ensure you have a docker repo (I use docker hub free account)
• ensure you have Cloudron CLI installed LOCALLY
• clone the repo (which should have all files needed)
• cd to the directory
• docker build -t <yourreponame>/<appname>:<tag>
• docker push <yourreponame>/<appname>:<tag>
• cloudron install --image <yourreponame>/<appname>:<tag>
  Follow the instruction.

Generally fairly easy.
Shout if you face any issues

[robi]

@timconsidine since you've already built it, it may be a good idea to connect with @atridad who has an unofficial repository of packaged apps before they're published in the App store.

Sharing the docker hub repo makes it easier for others to try, and there is a feature in Cloudron now to set a custom repo.

[timconsidine]

@robi sure will do

although my build seems old now : V1.3
https://hub.docker.com/repository/docker/tcmbp132021/baserow
Must update it

I think I recall that someone here said CloudronManifest.json must be in the same directory when attempting to use cloudron cli, so probably still worth following @bram guide

[Bruno]

@timconsidine Many thanks!

[girish]

@bram Sorry, this is blocked totally by us. We have already started updating some of the long standing apps and will also start publishing many of the already available apps this week and the next.

[nebulon]

Hi everyone, I was finally able to pickup the package, to get this forward into our app library.

@bram already did a wonderful job and for the moment I only had to do some cleanup of the package, not because it was wrong, but really only so the package is consistent with our other packages. This is less about the functionality but merely so it is easier for us to deal with them.

Also since we tend to update our tests and the test dependencies quite often, I also moved @bram's original files into a repo in our own gitlab next to all the other apps: https://git.cloudron.io/cloudron/baserow-app
@bram you should also have push rights to that repo by now.

To give some outlook, I think I will only have to now add the e2e tests for it and I will publish this in the next few days as unstable for everyone interested to test.

[bram]

@nebulon It's great to hear that you've added Baserow. I saw an email notifying me that I have developer permissions to the project . Let me know if there is anything that I can help you with in the meantime.

How would it work if we we're releasing a new version in the future? Should we then create a merge request in GitLab with the necessary changes?

[nebulon]

@bram usually we track upstream releases and then adjust the package repo accordingly, then build a new app package from that and run the tests. Once done we issue a new package release. So unless there are specific data migration steps to be made on a new release, I think you don't have to do anything from your side as we will maintain the package.
You have developer rights mainly, since you know your app better and possibly there might be useful adjustments to be made for the package in future versions, so feel free to push those directly into the app repo then.

[potemkin_ai]

@nebulon great, thank you for hearing and picking this up!

[nebulon]

I will lock this topic since the app is published by now and the forum section is https://forum.cloudron.io/category/136/baserow