Skip to content

Add full-stack Hostinger deploy shortcut (provider-untested) - #92

Draft
maxffarrell wants to merge 3 commits into
mainfrom
fix/hostinger-full-stack
Draft

maxffarrell wants to merge 3 commits into
mainfrom
fix/hostinger-full-stack

Conversation

@maxffarrell

@maxffarrell maxffarrell commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Adds the Hostinger README button using the documented compose_url parameter, labeled untested on the provider with setup instructions. Per user direction, provider testing is not a prerequisite to creating this candidate.

Standalone stack: pinned remote Git app build, PostgreSQL with persistent volume and health gate, existing migration-before-server startup, Caddy automatic HTTPS, and Tredaro uploads where applicable. Requires a paid/existing Docker VPS, public DNS hostname and persistent secrets. Button targets main and becomes usable after merge; review testing should use the branch raw file URL.

Validation: 3 tests per repo pass using real Compose 2.40.3 (button target, config contracts, missing-setting failures). New tests run in CI. No live Hostinger deployment or Docker engine available, so provider import/build/interpolation, HTTPS/login and persistence runtime behavior are untested. No resources purchased or deployed. Remains draft; not merged.

@maxffarrell maxffarrell changed the title Prepare full-stack Hostinger deployment Add full-stack Hostinger deploy shortcut (provider-untested) Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant