Features:
- add
S3_ENABLE_GCS_COMPATIBILITYconfiguration option for thestaticdeployserver to make it fully compatibile with Google Cloud Storage (GCS), for deployments where GCS is used as the S3-compatible blob storage service
Features:
- allow configuring the max request body size accepted by the server, which mainly limits the size of bundles that can be uploaded
Fixes:
- fix sdk regression caused by axios/axios#2781, which broke uploading bundles larger than ~2MB
Fixes:
- correctly handle requests having a trailing dot in their hostname (#31)
- in the Management Console, handle bundle names and tags containing
/and other special characters (#65) - only allow GET and HEAD methods for requesting assets (#66)
Fixes:
- fix OIDC token renewal logic caused by
oidc-clientlibrary bug
Features:
- slight design update of the Management Console
Fixes:
- make the OIDC authentication strategy handle JWKS rollovers
Features:
- inject the base path of the entrypoint at which the html page is being served
as the
BASE_PATHproperty of thewindow.APP_CONFIGobject - when a Content-Security-Policy header is defined for an html asset, patch its value to whitelist (via sha256 source) the configuration script injected in the html
Fixes:
- fix HTTP 400 error when updating an app
- render spinner while auth service is initializing
Features:
- change
app-managerrole target toappNameinstead ofappId - support wildcard roles for matching apps and bundles names
BREAKING CHANGES:
- change
app-managerrole target toappNameinstead ofappId - remove possibility to change an app's name
Features:
- improve the automatic refresh of the OpenID Connect auth token
Features:
- refresh OpenID Connect auth token automatically (when possible)
- improve login error message telling a would-be user that they need to be registered as a user before being able to login
Fixes:
- fix styling of long errors in Management Console operation modals
Features:
- role-based access control for write operations (with the option to disable auth enforcement)
- login with an OpenID Connect Provider
- new logo and other graphic improvements (credits to @Pendulla)
- allow not exposing management endpoints
BREAKING CHANGES:
- remove the possibility to update an entrypoint's
appIdandurlMatcher - remove the possibility to delete an app that has linked entrypoints
- the new method of authenticating users is not compatible with old auth tokens
Fixes:
- disable x-powered-by in all express apps
Fixes:
- fix redirects when serve-static is not mounted at /
Refactors:
- restructure the project to follow the clean architecture principles
- switch to Knex.js (from Sequelize) for sql operations
BREAKING CHANGES:
- the project is now distributed as the single docker image
staticdeploy/staticdeployinstead of the three imagesstaticdeploy/api-server,staticdeploy/static-server, andstaticdeploy/admin-console - the
staticdeploy/staticdeployimage requires a slightly different configuration than the previous three images. Refer to the documentation for details - SQLite is not supported anymore as a databse
- due to the SQL migrations library having changed, a migration of the saved migrations must be done manually on existing PostgreSQL databases. If you're in this situation, open an issue asking for support
Fixes:
- in the admin-console, hide the no-data placeholder of tables
Features:
- implement deleting bundles by name:tag combination
- admin-console:
- show operation logs details
- show bundles details
- optimize bundles retrieval
- client-side paginate long lists
- allow setting an entrypoint's bundle
- in an entrypoint's details, link to urlMatcher and redirectTo
Features:
- publish
staticdeploy/clidocker image with cli pre-installed - add healthchecks to
staticdeploy/api-serverandstaticdeploy/static-serverdocker images
Fixes:
- correctly parse cli
bundlecommandheadersoption (fixes #24)
BREAKING CHANGES:
- renamed cli command
create-bundletobundle
Features:
- allow passing options to the cli via config file
- allow specifying a custom status code for the fallback asset
- allow specifying custom headers for bundle assets
- make staticdeploy.io GDPR compliant
BREAKING CHANGES:
-
bundles must now specify a fallback asset, that will be served to requests not matching any other asset. The fallback asset used to be statically set to
/index.html, even for bundles not having an/index.htmlasset. Now it must be specified at bundle creation time (note: the StaticDeploy cli defaults it to/index.htmlif the asset exists in the bundle being created). For bundles created with StaticDeploy <= 0.7.0, SQL migrations set the fallback asset to/index.html. If those bundles don't contain the asset, requesting it will result in a 500 HTTP error (with StaticDeploy <= 0.7.0 it would have been a 404). The decision to let a 500 slip instead of handling the error and responding with a more correct 404 was made because handling the special case would have complicated the already complex routing algorithm, and because actually we don't expect there to be any such cases deployed -
routing algorithm changes:
- when serving a bundle containing assets
/pathand/path.html, requests for/pathwill get the/pathasset, not the/path.htmlasset (used to be the other way around) - when serving a bundle containing assets
/path.htmland/path/index.html, requests for/pathwill get the/path.htmlasset, not the/path/index.htmlasset (used to be the other way around)
- when serving a bundle containing assets
Features:
- fallback asset for bundles (see breaking change)
- improved routing algorithm (see breaking change)
BREAKING CHANGES:
- using the local filesystem to store static content is no longer supported
Features:
- also support PostgreSQL as SQL database
- use S3 (and API-compatible object storage services) for storing static files
- add
HOSTNAME_HEADERSoption to configure how requests for static content are routed
Fixes:
- increase CLI request body limit (fixes issue #11)
Fixes:
- fix descriptions for CLI commands and options
- fix html title in admin console
Features:
- reduce CLI installation size, speeding up installation
Features:
- add logo
- improve theme for docs website
Fixes:
- fix label in admin-console entrypoint edit / create form
Features:
- allow more characters (dots and slashes) to be used in apps names
Features:
- entrypoint redirects: now an entrypoint can specify either a bundle to serve or an url to redirect (302) to
Features:
- operation logs (for write operations)
Initial release.