Change Convertigo Server End point with Apps build

Home Forums Convertigo developers Forums as moved to Stack Overflow. Change Convertigo Server End point with Apps build

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #143748

    RItesh K
    Participant

    Hi All

    I need clarification in Convertigo Server End point

    1. I have a Mobile Apps developed through Convertigo
    2. I hosted my Convertigo Studio in IP abc.def.g.h
    3. I generated my build using Convertigo studio whose server endpoint is http://abc.def.g.h/convertigo
    4. I uploaded this build in Apple Store/Google Store
    5. I want When customer A will come and download the apps he should use end point server as
    http://abc.def.g.h/convertigo, which will be already there since i generated build with this IP
    6. When customer B download the apps from store
    he should use some other end point server like http://123.456.7.8/convertigo

    Basically customer should ask me to point which endpoint server and run their Apps

    Please let me know how can i achieve this.
    Can in my app login page define the Convertigo end point server address when user try to login.
    But how to make it parametrize?

    Regards
    Ritesh

    #143751

    jmc
    Participant

    Hi Ritesh,

    unfortunately this is not possible for the moment…

    The app is build with the hardcoded endpoint you provided and so cannot be changed.

    jmc

    ps : you can change the behavior of the server depending on the customer A or B or use a load balancer that will dispatch to another server regarding the customer.

    • This reply was modified 5 years, 3 months ago by jmc.
    #143761

    RItesh K
    Participant

    Hi jmc

    Thanks for this Reply.
    Is this the case really? I am afraid then this is a very big gap in the product. The whole purpose of MBaaS server flexibility is failed here.

    That means we cannot use this product if we really want to distribute via Google Store or Apple Store, if distributed then always use with hardcoded endpoint server

    Oh God, or we have some gap in understanding here.

    Have you confirmed this with Convertigo team members?

    Regards
    RItesh

    #143762

    admin
    Keymaster

    Hello,

    Lets make things clear here …

    Yes, the end point is hardcoded in the APK/IPA because there is not need to change it and this is definitely not something you want to show to your users! You will have only one production endpoint in the life of your app. end even if you change physical server address, this will be done by changing the DNS record and not the endpoint URL.

    Maybe your question is “how an I build a Distributed app to be published on the Appstores with the production endpoint ?”..

    To do this, just configure in your Mobile Device object the “Convertigo server endpoint” property with the production endpoint URL. Convertigo Studio will build an APK/IPA with This production endpoint in it, even if you build it from your studio. You will then be able to deploy this to AppStores. And your users will connect to the production Convertigo Server.

    Now, a very common case is that you want to have production servers and testing servers (testing server being sometimes Studio itself..) and you would like to have the same project to access the different server endpoint. This is done using Symbols.

    Any Convertigo property can be defined using symbols (see: http://www.convertigo.com/document/latest/operating-guide/using-convertigo-administration-console/global-symbols)
    You write in the property this way :

    ${your_symbol_name=default_value}

    This way, you can set the Mobile Device endpoint property to a symbol. The symbol will take different values according to the server you run the cloud build on.

    1) In your production server admin console define an END_POINT symbol pointing to the production URL
    2) In your test server admin console define an END_POINT symbol pointing to the test URL
    3) In your project define the Mobile Devices endpoint property to ${END_POINT}
    5) Deploy your project on test server and build mobile apps using test platform ON THIS SERVER ==> Test your app against this server. When OK ,
    4) Deploy your project on production server and build mobile apps using test platform ON THIS SERVER ==> Publish the APK/IPA to AppStores

    Hope This makes it clear.
    Convertigo Support Team.

    • This reply was modified 5 years, 3 months ago by admin.
    #143764

    RItesh K
    Participant

    Hi Admin

    Thanks for the clarification.
    I have some different use cases, will see how i can resolve my issues using above mentioned case

    Regards
    Ritesh

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.