SurrealDB

[girish]

@Odonno I saw a request today to join 'cloudron' group but this is not the workflow. Can you give me your username on gitlab (not sure if it was you who requested) ? I have to up the repo limit before you can create a repo there.

There's a whole bunch of apps in https://git.cloudron.io/cloudron/ (with the -app suffix). You can push the package code with your preferred opensource license .

[girish]

I don't have much idea of SurrealDB . Can you tell us a bit about how SurrealDB is backed up and restored? Does it store it's data in files or is it backed by another database?

[Odonno]

@girish Yes, it is stored in a single file for this particular purpose.

[Odonno]

@girish Yes, it is me. My name is David Bottiau.

[Odonno]

@girish What is the workflow then? I am unable to create a surrealdb-app repository.

[girish]

@Odonno You should be able to create repos on gitlab now (under your name). Once it's pushed, can you let me know? I will then move it under the cloudron organization.

[Odonno]

I have created the project here https://git.cloudron.io/Odonno/surrealdb-app

I have started to write tests but I don't how it can work. I have this error for the first test...

[girish]

@Odonno It seems the license on the package is BSL. We try to keep the package source code as proper opensource licenses . Note that surrealdb itself can be BSL, this is not a problem. The license in the repo only on the license of the package. This allows us (cloudron team) to continue to provide updates to the package reliably.

[Odonno]

@girish Ok, this is done. As long as it does not violate the SurrealDB license, I suppose it's ok.

[girish]

@Odonno Ok, I have forked it into our namespace - https://git.cloudron.io/cloudron/surrealdb-app . You should also be a maintainer of the repo.

So, the next step, is to get the tests working . Then, we will take a look into getting it published. Thanks for all the work!

[Odonno]

@girish Thank you. I can write the required tests. I am just stuck with the first one in error...

[girish]

@Odonno The message is just saying, you have to run cloudron build first before you can run cloudron install . Maybe you changed the repo directory or something? When that happens, it "forgets" the previous cloudron build image information.

[Odonno]

@girish Ah yes, that explains why. I don't know how it keeps track of the correct docker image. I suppose there is a key-value store somewhere.

Well, I finished to write a pretty good set of e2e tests. I think it is ready. Thank you for your help.

[girish]

@Odonno indeed, the key value store is in ~/.cloudron.json

[Odonno]

@girish Good to know! So, what's the next step?

[girish]

@Odonno we will have to find the time to review and publish the package.

[Odonno]

Any update on this @girish ?

[girish]

@Odonno haven't found the time yet. We are still working on getting a few apps updated before we start looking into new ones.

[Odonno]

@girish Very good practice indeed.

I have updated to the latest release 1.2.0. Gonna need that really really soon. But I suppose I can stick with my currently built local docker image.

[Odonno]

Updated to 1.3.0