Getting started¶
Get a Stegflow instance running and sign in for the first time.
Prerequisites¶
- Docker installed
Start Stegflow¶
Run the container:
Stegflow is in pre-release, so images are published under the beta tag.
Beta releases: expect to reset your data
While Stegflow is in beta, database migrations are not guaranteed to work from one image to the next. If you have configured persistent storage, plan on wiping the database and starting over after an upgrade. Do not keep data you cannot afford to lose in a beta instance.
Open the console¶
Open http://localhost:8080 in your browser.
Remarks¶
Without any configuration, Stegflow starts with the following limitations:
- Stegflow starts in single-user mode and signs you in automatically as the default administrator (
admin@stegflow.local). - No persistence is configured; all content is lost when the application restarts.
- No SSL/TLS encryption; everything runs over HTTP.
Not for production
Single-user mode has no real authentication: anyone who can reach the instance is signed in as a global administrator. Use it only on a trusted local machine. Before exposing Stegflow, set up real authentication with OIDC and a real administrator.
Next steps¶
- Create a tenant, the first thing to do once the console is open. Everything you build lives in a tenant.
- Configure persistent storage to keep your data safe.
- Set up real authentication with OIDC.
- Review the AWS compatibility reference.