Thanks, that is nice of you to say. The whole site and application have been designed and build by me. I have experience in design, UX, frontend, backend, devops and some business, so I know how to build web applications from scratch.
When creating a website I normally just browse the internet for inspiration. I often have parts of pages that I like and I make notes of that. https://dribbble.com/ is a good place to start. The second step is creating a design using Adobe XD and writing some initial content. This doesn't always come easy and you need inspiration, which I just don't have every day. After that I write the related html/css code. I'm quite strict because I always want it exactly the same as in the design. After that there is always some Javascript or backend that it needs to integrate with. I am not sure how much time I have spend on it in total because there are lots of changes after the first version, but it is definitely more than 60 hours on the homepage alone.
Fun fact is that everything on the baserow.io website like the homepage, blog, docs, etc are a plugin of the Baserow application. This way I can reuse existing components and colors and it integrates nicely with the tool.
Happy to hear that you are going to try out Baserow. While it is actually still in beta, the reliability is still good. Barely see errors in the log and major ones get resolved right away. Did a stress test recently and the current infrastructure can handle about 300 simultaneous very active users. All user data is backed up frequently and we have point in time recovery. The uptime of baserow.io and api.baserow.io is 100% since May 10 2020 according to uptime.com. To put that in perspective, the site was launched on April 30 2020 and there were some minor issues then that were quickly resolved.
You can't self host airtable (but it was thw first implementation of this sort of thing -- I guess I mentioned it as a reference). You can self-host baserow.
If anyone's ever wondered how they could use a tool like NocoDB or Baserow here's an example! I happen to run both for different things ([I've written about the Baserow use before]()), but it was super fun to try out both of these.
As just a side note for the practitioners out there, both NocoDB and the DB behind it are running in VMs just in case! :). I haven't done an audit or anything of NocoDB so always best to at least put the minimum levels of security in place.
I guess we’re back to the simplicity topic again.
The main reasons that I’ve been investigating and exploring this topic is that I’m currently using Notion for my task management and I’m sick and tired of it’s performance on very very simple database queries not to mention no real offline mode. So again keeping things simple is key to me especially for maintenance. The main thing that I do love about Notion is it’s ear of use and how clean, simple and great the UI is.
Thanks for the links I’ll have a look :). I also came across baserow.io which looks cool. I need to dig into it a bit bcz it seems that you can’t bring your own database which I really like the idea of.
There is PhoneTrack in Nextcloud and for all the other sensors you can use HomeAssistant app as it has a large number of available sensors including location and pipe all that data to some store of DB like the influxdb integration. Alternativly your could pipe it all to one of the many no-code DB app that have popped up recently like nocodb or baserow.
there is BaseRow.io, it's an open source Airtable-like, the problem is that it's not a desktop app, but a webapp, so you will need to run a few commands in the terminal in order to use it in localhost:3000.
I think self-hosted could include premium features with one-time fee (with several tiers, depending on the features needed). For example, I might be interested in LDAP that is not included in the free version, but I would be ok without other features. This pricing would fit the academia or institutions (my case) which would like to use open-source solutions without paying a monthly fee per user (mostly students).
For the hosted version (more for enterprises) it makes sense to have a monthly fee.
I understand completely. The premium features are going to be available for the self hosters! Everyone is going to be able to purchase a license on baserow.io and insert that into the his self hosted version which will unlock the features.
>features
You're right, I should have made it clearer whether the premium features are going to be available to the self hosters. I will make the changes on the website soon.
To answer your question, the premium features are going to be available for the self hosters! Everyone is going to be able to purchase a license on baserow.io and insert that into the his self hosted version which will unlock the features.
Oh btw, I would love to hear which established open source or self hosted competitors there are :)
I think you missed where to look. https://gitlab.com/bramw/baserow#try-out-a-demo Check out the section called "try out a demo" that is where it describes self hosting.
If you want the full on details there is also this. https://gitlab.com/bramw/baserow/-/blob/develop/docs/guides/demo-environment.md
Finally there is also this page about manually installing things. https://baserow.io/docs/guides%2Finstallation%2Finstall-on-ubuntu
Edit: I rewrote this a million times... 😬
>I came across https://baserow.io/ which seems to be a very nice tool but unfortunately it doesn't support exporting data yet.
It's a spreadsheet UI built on three of the most popular rdbms out there, writing code to export data is very easy.
I found links in your comment that were not hyperlinked:
I did the honors for you.
^delete ^| ^information ^| ^<3
I've been looking for an airtable replacement for ages. Ran across Baserow recently and while it's pretty much exactly what I'm looking for it's still in the early days and missing many features. Seems like it could use some more contributors!
>FYI; port 8000 is default used for Portainer. I recommend picking a different default port for your project.
Really? You can just choose another port.
Also you can skip the network creation step and you can just not expose the ports apart from the web interface.
https://baserow.io/docs/guides/demo-environment
IMHO the devs shouldn't choose another port just because some other program is using it. That'd be pretty hard to do for every project in the world since I guess there are more than 32767 of them ;)
It doesn't work that way because the user has full control his database. He can for example add, update or delete the fields. It is however possible to generate a Django model based on a table that has been created with Baserow. If you ever want to make a plugin this can be an easy way to fetch that data from the database server. You can read more about this in the docs https://baserow.io/docs/getting-started%2Fdatabase-plugin.