Section Overview
Projects
Use projects for application-centric deployments from GitHub or Docker images.
Deploy a Docker image
Run a raw container image through the project flow when you already have an image and need runtime configuration, resource sizing, storage, domains, and placement.
Goal
Deploy an image-backed application with the least ceremony.
Expected result
The project is live from a Docker image and manageable through the project pages.
Deploy from GitHub
Use the repository-backed project flow when you want StackShift to detect the app, build from source, and let you override runtime behavior before the first deploy.
Goal
Create a project that follows the GitHub-driven build and deployment path.
Expected result
The project is connected to a GitHub repo and can build and deploy through StackShift.
Builds, deployments, and logs
Understand the project execution lifecycle: build output, deploy state, rollback behavior, and where to inspect logs.
Goal
Know where to look when a project deployment does not behave the way you expect.
Expected result
You can trace a project issue from build to deployment to live runtime logs.
Project environment, domains, and previews
Configure the project surfaces that most often decide whether a deployment works after it builds, including runtime shape, domains, previews, and storage.
Goal
Understand the runtime settings that matter after the app image exists.
Expected result
The project is configured beyond just “it deployed once”.
Configure email providers
Use your own SMTP server or provider account for outbound email on projects and stacks, including BYOS connected-node workloads.
Goal
Set up outbound email correctly without confusing user-owned provider credentials with StackShift platform email.
Expected result
The workload can send outbound email through the user’s own provider account on hosted or connected-node infrastructure.
Project troubleshooting
Common project-side failure modes, especially when the app built successfully but does not come up healthy.
Goal
Shorten the path from “deployment failed” to the actual misconfiguration or runtime issue.
Expected result
You can classify a project failure accurately before retrying or rolling back.