Whether the environment has Scheduled Tasks enabled.Whether the task exists in the version used by this environment.If you’ve added a Scheduled Task and it’s not running in your desired environment, check: (This may differ from the tasks specified in the version you’re currently editing!) Therefore, the app version chosen for this environment specifies which tasks will run. Scheduled Tasks are specified as part of your app’s source code. You might not want to run Scheduled Tasks in every environment, however – for example, your development environment might not need to send “weekly digest” emails to all users. Your application can define Scheduled Tasks, which execute at specified intervals. The tables in this database will be available via _tables in this environment. You can choose which database each environment uses. You might want different environments to use different databases for your data tables – for example, so you can test your app without affecting production data.
This is useful, for example, to access production Uplink functions when you click Run in the Editor (ie from the debug environment).
Anvil docs code#
In this case, your Uplink code can be called from any environment. However, you can choose to Share uplinks with other environments. When Uplink code registers a server function with that function can normally only be called from code running in the same environment. Allowing other environments to call Uplink code You can configure, reset and remove uplink keys for each environment here. If you’re using the Uplink, you have to connect your Uplink code to a particular environment. You can choose a branch, or a specific commit – see Version Control for more details. To enable this, each environment can choose a version of the app. For example, your main site might be running well-tested code, while a “staging” URL allows you to test a new release, and individual developers can set up their own temporary environments running new code. You might want to make different versions of your app available at the same time. No URL at all – this means this environment cannot be accessed from a web browser, although it may still be accessed via the Uplink, or run Scheduled Tasks, if those are configured. A custom domain URL looks like this:Ĭustom domains are available on the Personal Plan and above. For information on using your own domain name with an Anvil app, click here. A public URL looks like this:Ī Custom Domain – this allows an application to appear on your own domain name. (For more robust authentication, you can use user authentication).Ī Public URL – this URL is easy to remember and type, so anyone can open your app. If the URL does get out accidentally, you can click Reset secret link, which will generate a new token, and invalidate the old URL – so anyone with the old URL can no longer access your app. This is useful for applications you don’t want to share widely. An environment can have:Ī Private URL – this URL contains a hard-to-guess token, so that it is only accessible by users to whom you have given the URL. Let’s look at each option in turn: Choosing a URL
0 kommentar(er)
