Copying One Project to Another

5 posts, 0 answers
  1. Jesse Herrera
    Jesse Herrera avatar
    39 posts
    Member since:
    Jul 2006

    Posted 07 Oct 2013 Link to this post

    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
  2. Steve
    Admin
    Steve avatar
    10941 posts

    Posted 08 Oct 2013 Link to this post

    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.
  3. Jesse Herrera
    Jesse Herrera avatar
    39 posts
    Member since:
    Jul 2006

    Posted 10 Oct 2013 Link to this post

    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
  4. Lyubomir Dokov
    Admin
    Lyubomir Dokov avatar
    43 posts

    Posted 11 Oct 2013 Link to this post

    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.
  5. Jesse Herrera
    Jesse Herrera avatar
    39 posts
    Member since:
    Jul 2006

    Posted 11 Oct 2013 Link to this post

    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. 
Back to Top