Repository navigation
v0.1.0-beta.13
Pre-release-
No container-log stream before the first deploy. The Logs tab of a never-deployed app no longer opens a
docker logs --followon a container that does not exist yet (it used to print "No such container" on every
reconnect). The card says that container logs appear after the first deploy;GET /apps/{id}/logs/streamand
/logs/downloadanswer 409 for an app in the NEW state. -
Cleanup options when deleting an app. The delete dialog can also remove the app's custom Docker networks
and prune dangling build cache. Networks are removed only if Tugra created them (they now carry a
tugra.managed=truelabel), no other app on the server lists them and nothing is still attached;tugra-proxy,
tugra-net,tugra-appsand networks you made by hand are never touched. Networks created before this release
have no label (Docker cannot add one to an existing network) and are left in place. The build cache is
host-wide, so it is pruned on the build server (or the app's server) and may make another app's next build
slower. The API takespruneNetworks=1andpruneBuildCache=1onDELETE /apps/{id}, and all four delete
query parameters are now documented as optional. -
More resource limits for Image and Git apps. Memory plus swap, a maximum process count, shared-memory
size, CPU weight and CPU pinning, next to the existing memory and CPU limits. They aredocker runflags, so
Compose and Swarm apps refuse to set them (clearing is always allowed); the Resources card shows them for
single-server apps. Unset, the run line is unchanged. A flag you also set in Docker options takes precedence.
A rollback re-renders from the current settings, so it applies today's limits, not the ones from the deploy
being restored. -
Honest app status. The app header, list and Overview now read from the container-health poll: Running,
Running (unhealthy), Running (no healthcheck) or Starting, instead of the lifecycle status alone. A
crash-looping container shows as unhealthy; missing or stale data never raises an alarm. HTTP and auto health
checks still gate deploys only, so an app that relies on one reads plain Running. The app API gains
containerHealth. -
Per-app container operations and networking. Set a graceful stop window (
--stop-timeout, also used by
deploy swaps, Stop and Restart), a drain pause for zero-downtime deploys (both versions keep serving for N
seconds before the old one stops), a cap onon-failurerestart retries, a stable container name that
resolves on every network the app joins, and extra Docker networks per app. The app page shows the internal
address other containers can reach it on. Unset, nothing about a deploy changes. -
Behaviour change: apps without a domain now join the shared
tugra-appsnetwork. A classic Image/Git app
with no domain, no managed-database link and no--networkin its Docker options is created on a per-server
tugra-appsbridge on its next deploy instead of Docker's default bridge, so apps on the server can reach
each other by container name. Anything that relied on default-bridge addressing (thedocker0gateway, a
fixed bridge IP) must be adjusted; add--networkin the app's Docker options to keep full control. -
Git and build settings per app. Git submodules, Git LFS, shallow clone, disabling the build cache, passing
env vars as build arguments, and a source commit mode (SOURCE_COMMIToff / runtime / build and runtime). Two
behaviour changes for existing Git apps on their next deploy: the container now gets a runtimeSOURCE_COMMIT
env (aSOURCE_COMMITyou set yourself wins; Build settings, Source commit, Off opts out), and the clone
exportsGIT_LFS_SKIP_SMUDGE=1unless Git LFS is enabled, so LFS files stay pointer stubs (the build log
warns when.gitattributesuses LFS). Submodules and LFS authenticate with the app's token for any repository
on the same git host; previews never clone submodules or pull LFS. The agent image now shipsgit-lfs. -
Breadcrumb shows the environment. App and database pages now read Projects, project, environment, then the
resource, and the environment crumb jumps straight to that environment's card on the project page. -
Clone an app into another environment. The clone dialog now has an Environment picker (this team's
environments, defaulting to the app's own) and shows what was not carried over once the clone is created. The
hub also checks the caller's access to the destination project when moving or cloning an app to another
environment. -
Link a Git provider from the app's Source card. Pick a connected provider (GitHub App, Gitea, Forgejo,
Codeberg) for a Git or Git-compose app, or unlink it, without leaving the app. Only this team's providers for
the repository's host are offered, and a linked provider takes precedence over a stored personal access token.
GET /git-sourcesnow also returns each source'scloneHost. -
"Links" menu in the app header. Apps with more than one address (alias domains, per-service domains on a
compose app, published compose ports) get a "Links (n)" menu that opens each one in a new tab, visible to every
viewer; the Overview's Live URL row lists them all. Apps andGET /appsresponses gain alinksarray (primary
first); per-service domains are included onGET /appsandGET /apps/:idonly. -
Analytics tab on every app. The same visitor analytics as the Traffic page (requests, status classes,
bandwidth, latency, unique visitors, countries, paths, browsers), scoped to the app's own primary, alias and
per-service domains, with a domain picker and clear empty states (no domain, analytics off on the server, no data
yet).GET /traffic/*gains anappIdfilter that needs access to that app and can only narrow, never widen,
what a caller sees. A clustered app shows traffic recorded on its own server only.