Properties are set in application.properties (embedded in the JAR) or in an external file
loaded with --spring.config.additional-location. Environment variables and command-line
arguments override both, in the usual Spring Boot order.
Every property below exists in the current release. If a property you remember is missing
from this page, check the two notes: it may have been removed.
HTTP listening port. Also accepted on the command line — java -jar viglet-shio.jar --server.port=8099
shio.admin.password
(unset)
Sets the admin password on startup, skipping the first-access screen. Environment form SHIO_ADMIN_PASSWORD; minimum six characters. Never overwrites a password already configured and never prevents startup — see Installation § Setting the admin password without the console
shio.url
http://localhost:2710
The instance's own base URL, used wherever an absolute URL is composed
shio.website.javascript.engine and shio.website.nashornno longer exist. Shio
renders pages with Handlebars templates, and there is no server-side script engine to
select or tune (the Nashorn dependency is explicitly excluded from the build). Setting
either property has no effect. See Pages, Layouts & Regions.
Every limit here exists so a caller cannot ask for an unbounded response. A request over the
maximum is clamped, and the response says so.
Property
Default
Description
shio.agent.context.default-budget-tokens
4000
Context-pack size when no budget is given
shio.agent.context.max-budget-tokens
40000
Ceiling for budget=
shio.agent.context.default-depth
3
Folder-tree depth walked
shio.agent.context.max-nodes
1000
Sitemap rows
shio.agent.batch.max-ops
200
Ops in one POST /agent/batch
shio.agent.batch.max-document-ops
2000
Compiled ops in one apply
shio.agent.read.default-limit · .max-limit
25 · 200
find / read rows
shio.agent.verify.default-limit · .max-limit
200 · 2000
Findings per report
shio.agent.verify.max-fetches
50
Requests the delivery check may issue
shio.agent.verify.fetch-budget-millis
15000
Time budget for those fetches
shio.agent.render.allow-fetch
false
Whether /agent/render?url= may fetch a live URL. Off by default: an endpoint that fetches on the server's behalf needs an operator's consent, not a caller's
DATABASE_TO_UPPER=false;CASE_INSENSITIVE_IDENTIFIERS=true must stay. The schema uses
lowercase identifiers (including the tenant discriminator column) and without them H2
folds names to upper case, which surfaces as Column "..." not found at startup.
The dialect is inferred from the URL; set spring.jpa.properties.hibernate.dialect only if
you have a reason to override it. Shio ships no Oracle driver: the schema is verified on
PostgreSQL, MariaDB and H2 by integration tests.
An upgrade is a restart: migrations run on boot, so a rolling restart is a migration.
Never work around a schema problem by setting ddl-auto to update: that produces a
database which no longer matches the changelogs, and the next real migration fails.
Asynchronous failures , webhook deliveries, image transforms, scheduled publishes, 5xx ,
are also readable at GET /api/v2/agent/diagnostics, which is usually faster than grepping
the log.