@rmdes we're analyzed your logs in more detail, and the only thing that's off, it the Invalid field name(s) given in select_related: 'profile'
error. We're going to look into that. Meanwhile, it would also be great to receive which environment variables you've configured.
bram
Posts
-
Request failed with status code 500 -
Request failed with status code 500I've tried to reproduce it by doing the following:
- Manually install 1.16.1 (Baserow 1.22.1) using
cloudron install -l upgrade-test-2 --image cloudron/io.baserow.cloudronapp:20231221-163612-6274e3e65
- Wait for all the templates to install
- Upgrade to 1.16.2 (Baserow 1.22.2) using
cloudron update --app 30d540a1-9fb8-4d69-b572-5c481df18a7a --image cloudron/io.baserow.cloudronapp:20240115-111341-0207e58dd
But it all works as expected.
- Manually install 1.16.1 (Baserow 1.22.1) using
-
Request failed with status code 500Hi @rmdes, we're currently looking into this problem. We want to reproduce your scenario as close as possible. Do you have any environment variables set?
-
Docuseal - Docusign alternativeI would love to see DocuSeal on Cloudron as well.
-
Update Baserow package to 1.7.1@doodlemania2 Both is going to be included!
-
Update Baserow package to 1.7.1@nebulon It's been working very well for everyone that I've spoken with, so I'm okay with marking it as stable.
@ei8fdb Glad to hear that it's working well for you. We're moving as fast as possible with in terms of development, but we value quality over speed a lot. It might take a bit longer than you would have expected, but the features that we deliver always work really well and stable. We just hired three new developer who will be joining our team in the upcoming months, so you should see a speedup.
@doodlemania2 We're working on public view sharing right now, it will probably be released early January. You can also expect a gallery view, improved user file previews, performance improvements and much more.
-
Update Baserow package to 1.7.1Hey all, this is Bram, the founder of Baserow. We recently release version 1.7.1 (https://baserow.io/blog/november-2021-release-of-baserow) and I was curious what the process would be to update it in the Cloudron app store. We've made some changes here https://gitlab.com/bramw/baserow/-/tree/develop/deploy/cloudron that must also be applied in the app store version.
Let me know if I can be of help!
-
Baserow Cloudron app - Airtable alternative@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?
-
Baserow Cloudron app - Airtable alternativeThanks for the kind words @potemkin_ai!
Good luck with the release @girish! I know from my experience that those can be a bit stressful. Let my know if there is anything that I can help you with regarding moving Baserow to the Cloudron app store.
-
Baserow Cloudron app - Airtable alternative@girish Could you share any progress on having Baserow in the Cloudron App Store?
-
Baserow Cloudron app - Airtable alternative@zagzoog The web socket URL would be on
wss://api.baserow.io/ws/core/?jwt_token=YOUR_JWT_TOKEN
where you would replace api.baserow.io with your self hosted domain. So, if your Baserow copy runs on baserow.example.com, you should replace it with that. Both the backend and the web-frontend run on the same domain in Cloudron. More information about the web sockets and also some examples how to connect directly can be found here https://baserow.io/docs/getting-started%2Fweb-socket-api. -
Baserow Cloudron app - Airtable alternative@jdaviescoates That makes sense. I'll await his response.
-
Baserow Cloudron app - Airtable alternative@girish I just created an account on git.cloudron.io, but it seems like I can't create a new repository. When creating a new project I get the error "Namespace is not valid". All the other repo's are in the cloudron project https://git.cloudron.io/cloudron, but it seems like I can't create a new repo there. Am I missing something?
Alternatively, you can find the deploy code in our own public repo and copy it from there https://gitlab.com/bramw/baserow/-/tree/master/deploy/cloudron. It already has an MIT license there.
How would it work in the future if we release a new version of Baserow? Can we deploy the latest version to the app store?
-
Baserow Cloudron app - Airtable alternative@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.
-
Baserow Cloudron app - Airtable alternative@timconsidine Glad to hear that it now works for you!
-
Baserow - Airtable Alternative@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. -
Baserow - Airtable Alternative@doodlemania2 Are you looking for a default username and password of Baserow?
-
Baserow - Airtable Alternative@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. -
Baserow Cloudron app - Airtable alternativeThis will work for my use case. Thanks!
-
Baserow Cloudron app - Airtable alternativeI 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.