Sources

Sources are how you tell Askrike where to find your applications, configurations, and assets. Think of them as connectors that link your deployment prompts to actual code and files.

How Sources Work

Sources use the @ command syntax followed by the source type and path:

@SourceType/path/to/resource

For example:

• @GitHub/username/repository - Deploy from a GitHub repository
• @Docker/nginx:latest - Use an nginx container from Docker Hub
• @Files/config.json - Reference an uploaded configuration file

Available Sources

Askrike supports three main source types:

GitHub

Deploy applications directly from your repositories. Supports both public and private repos, with automatic build detection for popular frameworks.

Docker

Deploy containerized applications from Docker Hub. Access thousands of pre-built images with automatic configuration.

Files

Upload and reference static files, configurations, or assets directly through the Askrike interface.

Using Sources in Prompts

Combine multiple sources in a single deployment:

Deploy my @GitHub/username/webapp with @Docker/redis:alpine cache
and use @Files/production.env for environment variables

Source Features

• Automatic detection - Askrike analyzes your sources and configures appropriate infrastructure
• Intelligent linking - Sources are automatically connected based on your deployment context
• Version control - Specify exact versions, branches, or tags for reproducible deployments
• Security - Private repositories and uploaded files are handled securely

Next Steps

Click on any source type in the sidebar to learn about its specific features and usage patterns.