b9206b1844
This change allows you to host the vuetify app on <x>.example.com where the main app is hosted on example.com. A configuration is added to specify an exact subdomain for cookies. For example, if my production app is hosted on us1.storj.io and my vuetify app is hosted on vuetify.us1.storj.io, the cookie domain should be set to ".us1.storj.io" so that any authentication cookie is accessible to lower-level subdomains. Since the vuetify app does not currently support login/signup on its own, it is still required to first login to the main satellite UI, then navigate to the Vuetify app after the session cookie is set. If the "vuetifypoc" prefix is not desirable when using subdomain hosting for vuetify, the VITE_VUETIFY_PREFIX variable can be modified in web/satellite/.env before running `npm run build-vuetify`. For now, we should keep this prefix because it makes developing on the vuetify app significantly easier if subdomains are not being used. Issue: https://github.com/storj/storj/issues/6144 Change-Id: Iba1a5737892c8ee8f38148a17b94e3222f8798e6 |
||
---|---|---|
.. | ||
deploy | ||
testdata | ||
tests | ||
waitlist | ||
build-wasm.sh | ||
cert-gating.sh | ||
changelog.py | ||
check-package-lock.sh | ||
deploy-storagenode.sh | ||
deploy-watchtower.sh | ||
draft-release.sh | ||
gerrit-cla.py | ||
gerrit-status.sh | ||
lint.go | ||
pg-to-crdb.go | ||
release.sh | ||
tag-release.sh | ||
test-certificates.sh | ||
test-network-stalls.go | ||
test-wasm-size.sh | ||
test-wasm.sh | ||
update-access.go | ||
utils.sh | ||
validate-jenkinsfile.sh |