FAQ
Last updated
Last updated
Unfortunately we don't support applications that don't run in a containerized environment.
No. It can be configured with any environment, cloud or on-premises, Docker or Kubernetes. Read how you can .
Yes. Find the NGINX example .
Short: Generic configuration => Image, specific configuration => Container config, configuration is inherited from Image configuration.
Parameters that are generic and context independent should be defined on the Image level. Other, context dependent information, like an environment variable PUBLIC_URL="https://example.com" should be defined on the Deployment's level. During deployment there is a one-way merge using these configurations with Container configuration having the higher priority.
Unfortunately no, but there are settings you can use to disable Kratos. More details .
Yes.
Unfortunately there's no such capability within the platform now, but creating a similar functionality is in our plans.
Unfortunately routing isn't managed by the platform itself. When you'd like to access your node or a deployed stack through a domain, you'll need to configure routing on your own.
dyrector.io is for anyone who works with containerized applications. That means organizations, or independent developers can gain advantage of the platform's functions.
We needed a solution for self-service release management capabilities for an entirely different project. We couldn't find one that fit exactly our needs, so we made our own platform.
The platform provides , but it doesn't offer CI, as of now. Such capabilities are in our long-term plans.
Self-managed use will stay 100% free and unrestricted. But most of our team works full-time on the platform. While we gain some revenue as a cloud consultancy, we accept to fund the project.
Don’t hesitate, reach out to us at . Also drop us a mail to the same address if you find a bug or any other anomaly you experience. We’ll respond within 24 hours.
Send us an e-mail at or check in on .