New version groups start off as copies of the version group that is currently deployed to the live instance.
New Name:
Recent Deletes:
Deleted version groups are only shown under recent deletes for 7 days.
Warning, deleting a version group clears all staged and unstaged changes by all employees working on that version group.
Only 'Deployment Authenticated' employees may delete version groups.
New Name:
New About:
The hard refresh installs all npm dependencies, whereas the soft refresh skips this. The hard refresh should be run after the list of custom npm dependencies is updated or to use the most recent npm versions.
The advantage of the soft refresh is that it is faster, which makes it better suited for regular refreshes during development.
As a general 'best practice' rule, run the hard refresh for your first refresh of the day and then you can use the soft refresh for the rest of the day.
Each employee has their own virtualised testing environment. In this environment includes staged edits from all employees, but only unstaged edits from the given employee.
Web apps are refreshed individually, so remember to refresh linked web apps to make sure that you are working with the most recent version. E.g. if web app A makes an API call to web app B, refresh both web app A and B even if you are just testing web app A. If you are not testing an integrated feature, this doesn't really matter.
NB. As a general 'best practice' rule, refersh all relevant web apps after each top level deployment, otherwise your testing environment stays on an outdated version.
Web apps can have different version groups. This is a feature that shouldn't be used too often, but it can be useful to push quick changes like security patches concurrently to developing a major new feature.
The global file system can only have one version group at at time to avoid complications.
The test sub-domain is publically accessible. This means that anyone (including members of the public and other employees) can view and interact with your testing instance. This is similar to how the live instance will be publically accessible.
A public sub-domain can be useful for testing how changes appear on various devices (including mobile devices), before deploying these changes.
Tip: Each sub-domain must be manually configured on both DigitalOcean and Cloudflare.
about
Web Apps:
Version Group:
| Name | About | Created (UTC time) |
|---|
Refresh (about)