Deze inhoud is niet beschikbaar in uw taal, maar wel in het Engels.

Source control


Updated: June 16, 2015

When using a JavaScript backend, Microsoft Azure Mobile Services can be configured to provide a Git repository to store your server scripts. Server script code files uploaded from your local repository are automatically published to your mobile service. For a tutorial on how to publish server scripts from your local repository to your mobile service, see Store server scripts in source control. A .NET backend mobile service instead uses the publishing facilities of Visual Studio.


Write down the login credentials that you supply when you enable source control and create your Git repository. You will need to provide these credentials to synchronize data between the repository and your local computer. If you lose your credentials or want to change them, you can reset the credentials in the Management Portal. To reset your credentials, click Rest your source control credentials on the Dashboard tab, then supply new credentials and click OK.

The benefits of using source control include the following:

  • Author server scripts on your local computer using your favorite editor, and then publish changes to your mobile service.

  • Maintain a history of changes made to server scripts and permissions, even when changes are made in the portal.

  • Go back to a previous version of your code, if problems occur after deployment.

  • Deploy a set of server script updates in a single changeset.

  • Enable multiple users to work on the same code files simultaneously, and then merge changes in Git.

For more general information about using the Git source control system, see the Git web site. Try out Git commands live in the Git interactive tutorial.


A restart of your mobile service is initiated every time that you commit and push changes to your mobile service using Git.

The repository has the following folder structure:

  • service: Root of the mobile service-specific repository.

    • api: Contains custom API script files (api_name.js) and JSON permission files (api_name.json).

    • extensions: Contains modules that extend the runtime behavior of your mobile service.

    • shared: Contains shared script files, such as the Apple Push Notification Service (APNS) feedback script (feedback.js).

    • scheduler: Contains scheduled job script files (job_name.js).

    • tables: Contains table operation script files (table_name.js) and JSON permission files (table_name.json). Legacy script files are stored in the format tablename.operation.js.

For more information, see the readme files in the repository.