Fix restricted map controls and release verification
All checks were successful
Deploy MineGeo to Dokploy / deploy (push) Successful in 5m17s
All checks were successful
Deploy MineGeo to Dokploy / deploy (push) Successful in 5m17s
This commit is contained in:
@@ -130,7 +130,12 @@ does not enable shell tracing, disable TLS verification, follow authenticated
|
||||
redirects, or retry source uploads automatically. HTTP `000` means no HTTP
|
||||
response was received; inspect the curl exit code and error immediately above it.
|
||||
The job waits for Dokploy's deployment status and fails if the upload or deployment
|
||||
fails. Build logs remain available in the Dokploy dashboard.
|
||||
fails. Status polling tolerates up to six consecutive transient network/server
|
||||
failures after an upload has been accepted, and retries only the read-only status
|
||||
request. Authentication and certificate verification errors still stop the job.
|
||||
All deployment IDs present before the upload are excluded from completion checks,
|
||||
so an older successful build cannot be mistaken for the new release. Build logs
|
||||
remain available in the Dokploy dashboard.
|
||||
|
||||
`git archive` sends tracked files from that commit only. It does not include
|
||||
`.git` metadata, local environment files, untracked files, or local caches. The
|
||||
|
||||
Reference in New Issue
Block a user