This is a migrated thread and some comments may be shown as answers.

Copying One Project to Another

4 Answers 52 Views
General Discussion
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Jesse Herrera
Top achievements
Rank 1
Jesse Herrera asked on 08 Oct 2013, 01:33 AM
is it possible to copy one project to another or to create additional fields and tables using a script? I want to be able to quickly create a new empty version of a project without having to add the fields and tables one at a time. Using a script it would be nice to also e able to insert some default data for lookups etc.

Thanks

4 Answers, 1 is accepted

Sort by
0
Steve
Telerik team
answered on 08 Oct 2013, 03:04 PM
Hello Jesse,

It is possible to create your own "template" by modifying one of the default ones. After you're done, you can export your project. When you want to create a new one but start with your "template", just use the Blank template and use the recreate your project from archive option.

You can also skip step 2 of creating a blank template and importing your project and directly clone your "template" from a git repository (you need to push it there first). See recreate Your Project from Git Repository help article.

Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
Jesse Herrera
Top achievements
Rank 1
answered on 10 Oct 2013, 09:26 PM
Thanks for the response! I'll give this a shot and see how it works. My end goal is to have a single application using multiple Everlive databases. Each database is a different customer but all of the structures are the same. My idea was that I would then swap out the API keys based on the customer entry page being used. Does this sound like the right approach? Thanks for your time.

Thanks,
Jesse
0
Lyubomir Dokov
Telerik team
answered on 11 Oct 2013, 09:15 AM
Hello Jesse,

What you describe is a valid approach. However, you should consider using the same app for all customers. If you are concerned about security and permissions, you could use the Everlive security system. Since the last release it became really powerful. We support role permissions, owner permissions and granular permissions. This means that you can make some data only available to its owner(the user that created it). You can change owners, give permissions to specific roles. Additionaly, it is possible to allow sharing of items among users, if you need to. This can be easily achieved using granular permissions. You can find more information in the Everlive documentation under Security.

It is indeed possible to create Everlive applications through code. If you decide that you will use different app for each customer, you can do it. For more information on this please check the Metadata API in the Everlive documentation. Note, however, that if you create an app for each of your customers, you might turn up with a great number of Everlive apps, which would be harder to manage from the Everlive portal.

Let us know if you have other questions, we will be happy to help.


Regards,
Lyubomir Dokov
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
Jesse Herrera
Top achievements
Rank 1
answered on 11 Oct 2013, 01:50 PM
The problem I saw with using a single Everlive database for multiple customers was that it was very likely that users for different customers may want to use the same login ID. I didn't want that to be an issue. 
Tags
General Discussion
Asked by
Jesse Herrera
Top achievements
Rank 1
Answers by
Steve
Telerik team
Jesse Herrera
Top achievements
Rank 1
Lyubomir Dokov
Telerik team
Share this question
or