Hi Girish,
Great work bundling up Directus 9, however, I've run into a problem.
While looking to implement the built in map interface, it errored because PostGIS isn't installed.
The logs files during startup also highlights this issue -
PostGIS isn't installed. Geometry type support will be limited.
A quick google suggests this is an extension that can be added to Postgres.
Is this something I can add into the postgres bundled with Cloudron?
Thanks!
They seem to have just bypassed a finalised version of 9 completely.
https://github.com/getredash/redash/releases/tag/v10.0.0
There are some instructions on the github release page to upgrade from v8.
I'm happy to assist in testing an updated version if that helps?
Hi Guys,
It looks like Directus has finally been released as stable.
Is this something we can look to add to the official cloudron release?
@atridad has a custom app built on the release candidates that I assume would be a good starting point for this?
A follow on question for me would be, is there a way to migrate the directus custom app data on my cloudron instance into the official release app once it drops?
Thanks
Mark
This is the info from the logs
Aug 13 13:30:10 box:locker Acquired : box_update
Aug 13 13:30:10 box:tasks startTask - starting task 8741 with options {"timeout":72000000,"nice":15,"memoryLimit":400}. logs at /home/yellowtent/platformdata/logs/tasks/8741.log
Aug 13 13:30:10 box:shell startTask spawn: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 8741 /home/yellowtent/platformdata/logs/tasks/8741.log 15 400
Aug 13 13:30:10 box:shell startTask (stdout): Running as unit: box-task-8741.service
Aug 13 13:30:20 box:apphealthmonitor app health: 7 running / 3 stopped / 0 unresponsive
Aug 13 13:30:23 box:shell startTask (stdout): Finished with result: success
processes terminated with: code=exited/status=0
runtime: 23.433s
time consumed: 3.003s
Aug 13 13:30:23 box:shell startTask (stdout): Service box-task-8740 finished with exit code 0
Aug 13 13:30:23 box:tasks startTask: 8740 completed with code 0
Aug 13 13:30:23 box:tasks startTask: 8740 done. error: null
Aug 13 13:30:23 box:shell startTask (stdout): Finished with result: exit-code
processes terminated with: code=exited/status=50
runtime: 13.106s
time consumed: 2.661s
Aug 13 13:30:23 box:shell startTask (stdout): Service box-task-8741 failed to run
Aug 13 13:30:23 box:shell startTask (stdout): Service box-task-8741 finished with exit code 1
Aug 13 13:30:23 box:shell startTask code: 1, signal: null
Aug 13 13:30:23 box:tasks startTask: 8741 completed with code 1
Aug 13 13:30:23 box:locker Released : box_update
Aug 13 13:30:23 box:updater Update failed with error {
stack: 'BoxError: update exited with code 1 signal null\n' +
' at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:78:17)\n' +
' at ChildProcess.emit (node:events:513:28)\n' +
' at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)',
name: 'BoxError',
reason: 'Spawn Error',
details: {},
message: 'update exited with code 1 signal null',
code: 1,
signal: null
Aug 13 13:30:23 box:tasks startTask: 8741 done. error: {
stack: 'BoxError: update exited with code 1 signal null\n' +
' at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:78:17)\n' +
' at ChildProcess.emit (node:events:513:28)\n' +
' at Process.ChildProcess._handle.onexit (node:internal/child_process:293:12)',
name: 'BoxError',
reason: 'Spawn Error',
details: {},
message: 'update exited with code 1 signal null',
code: 1,
signal: null
Great, thanks @girish!
Great, thanks @girish, it's working now.
Hi All,
Looking at the Redash forums the devs have indicated a number of times that the latest beta - 9.0.0-beta.b42121 is also the production version.
There doesn't seem much inclination at their end to create a new prod tag using the same beta baseline.
Is it possible to allow the use of this version in Cloudron?
It's apparently what they're using in the redash hosted offering. So it would seem to be production ready.
There are a number of features in 9.0 that would be very useful to me on my cloudron instances.
Thanks
Mark
I'm pretty new to Jupyter and I'm unclear how I go about updating JupyterLab to v4? Is this something that needs to happen in the Cloudron image or is it something I can do myself?
I'd like to test out an extension that doesn't work in any JupyterLb versions less than v4.
Thanks
Mark
Thanks @girish, looking forward to it.
Agree regarding v9.0. Ever since they've been bought by databricks their focus seems to be in making everything work with the databricks stack first, then releasing to the public second.
Hopefully, now that they've bedded down the transition, releases will become a little more regular again.