Using Appery as a Production Environment

I have found no information from Appery about source code management for unit test / integration test/ development production.

Normally, you can have a development environment that promotes code through several layers into production. I can delete my production code, and then reload from development backup into production, and then ready that version for release to apple and google store. 

I cannot do the same for server code. There is no version of "backup" and "release" for server code, when is this going to be offered?

Does the push API key for an existing, live released application change when I delete a an application entirely, then create a new one, and relink it to the database? or is the push API key a feature of the database itself?

The "Application Parameters" service in Appery stores lots of "magic numbers" in the application itself, and further magic numbers - parameters - are stored in services, like the push services. Is there no mechanism to store these external to the application in a database to load at runtime?
1 person has
this problem
+1
Reply
  • Hi Joseph,

    Normally, you can have a development environment that promotes code through several layers into production. I can delete my production code, and then reload from development backup into production, and then ready that version for release to apple and google store.

    This functionality is mainly a versions control of a source code. Appery.io is a visual builder and not a source code editor (though you can edit source code in Appery.io but this is not a main point).

    I cannot do the same for server code. There is no version of "backup" and "release" for server code, when is this going to be offered?

    Let me check this, if such functionality is in our to-do list.

    Does the push API key for an existing, live released application change when I delete a an application entirely, then create a new one, and relink it to the database? or is the push API key a feature of the database itself?

    Push API key is connected to the database mainly.

    The "Application Parameters" service in Appery stores lots of "magic numbers" in the application itself, and further magic numbers - parameters - are stored in services, like the push services. Is there no mechanism to store these external to the application in a database to load at runtime?

    Could you please specify what exact "magic numbers" do you mean?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly

  • Hello!

    There is no version of "backup" and "release" for server code, when is this going to be offered?
    Added in our todo list
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated happy, confident, thankful, excited indifferent, undecided, unconcerned kidding, amused, unsure, silly