lib and project

[philippecoenen]

Hello Mark,

I have tried to simply copy the lib from one project to another.
But it seems it was not working.
Finally, I create a stack with an empty sample and that was good. I can now log in properly.

Is it in the config file that the project is identified? So if I copy the config things will work?
And what is the format of the config (it looks like an encoded array I didn't check though)
I suspect that it's mandatory to create a new stack using an empty sample (or one of the samples) to export a project config?
But what if I want to change the project keeping the same stack? How does it work?

It's not 100% useful for me to know that but I feel a little uncomfortable not knowing what is what.
How do the libraries (or my stack) understand which project to connect to?

In a couple of days, I will start some more serious development and I would prefer to know where I put my feet 

I thank you already, 

-Phil

[mark_talluto]

Hi Phil,

The config file is encrypted JSON on disk. It is converted to an array when loaded by the libraries into LiveCode. This file contains all the information about your table schema structure. It is project based. LiveCloud Manager (LCM) will export your entire canelaDB folder containing your config and libraries. Your database folder is auto created for you on first run of your app.

If you start work on one computer and transition to another computer, you can safely grab the whole project and copy it over. You may continue working on that project from the new location.

If you start a new project, you will want to export your toolKit for every new project.

If you modify your schema (add/remove table or keys), you need to export your toolKit over your existing canelaDB folder. LCM will only replace your config file and libraries when you do this. Your database folder will remain as it is.

A copy of your updated config is automatically stored for you in the cloud. Your clients will be able to get the updated config with all your changes automatically.

LCM can create a starter project for you. It is a good place to start because it will automatically create the project with your initializeLiveCloud code in place. You can create one with or without a log in screen. The log in code is automatically set up for you. There are comments in the code to tell your software where to go or do on successful authentication or failed authentication.

We have some good starter information about some of this here: https://docs.livecloud.io/Setup/
This may benefit others just getting started.

I look forward to your next moves in your development.

-Mark

[philippecoenen]

Hi Phil,

The config file is encrypted JSON on disk. It is converted to an array when loaded by the libraries into LiveCode. This file contains all the information about your table schema structure. It is project based. LiveCloud Manager (LCM) will export your entire canelaDB folder containing your config and libraries. Your database folder is auto created for you on first run of your app.

If you start work on one computer and transition to another computer, you can safely grab the whole project and copy it over. You may continue working on that project from the new location.

If you start a new project, you will want to export your toolKit for every new project.

If you modify your schema (add/remove table or keys), you need to export your toolKit over your existing canelaDB folder. LCM will only replace your config file and libraries when you do this. Your database folder will remain as it is.

A copy of your updated config is automatically stored for you in the cloud. Your clients will be able to get the updated config with all your changes automatically.

LCM can create a starter project for you. It is a good place to start because it will automatically create the project with your initializeLiveCloud code in place. You can create one with or without a log in screen. The log in code is automatically set up for you. There are comments in the code to tell your software where to go or do on successful authentication or failed authentication.

We have some good starter information about some of this here: https://docs.livecloud.io/Setup/
This may benefit others just getting started.

I look forward to your next moves in your development.

-Mark

Hello Mark,

I see. OK. Your answer is clear and complete. I didn't know that it's OK to modify the database and have the users updated automatically. 
That's good.

Now it need a good amount of confidence to have a part or the app in a black box.

Thanks for the info.

Best,

-Phil