Homer
A lightweight, configurable homepage for self-hosted services
Screenshot from verification · Click to enlarge
Application tests passed; AWS environment evidence comes from the referenced platform verification.
Quick Deploy
Use the recommended configuration, or customize it below.
Recommended configuration
- Version
- v26.08.3
- AWS Regions
- us-east-1
- Instance
- t3.small
- Persistent data volume
- 30 GB
Customize configuration
Change the version, region or resources. Larger resources have not been verified separately.
Deployment steps and post-deploy actions
After you deploy
- The CloudFormation wizard opens with everything prefilled (stack "corenova-homer-v26-08-3") — review and click "Create stack".
- Wait until the stack status reaches CREATE_COMPLETE (about 10 minutes). Outputs are only visible after completion.
- Open the stack's Outputs tab — everything you need is there:
ResolvedLaunchUrlAccess URL — open this in your browserPublicIpThe instance's public IPPublicDnsNameThe instance's public DNS name
- Open the access URL in your browser — the app is ready to use.
Good to know
- Edit /www/assets/config.yml through the instance terminal to organize links. The public dashboard has no built-in sign-in; do not place private information in its configuration.
Next steps
- Your data lives at /www/assets inside the container, on an encrypted EBS volume. Find the instance by its ID in the EC2 console.
- Back up before any changes: Upgrading and backups guide
- To upgrade to a newer verified version: Version history
Deleting the stack terminates the host, but the data volume is retained and continues billing. Snapshot it first, then delete the retained volume manually when you no longer need it.
Versions
View full version history| Versions | Verified At | Verified | Status | AWS Tested |
|---|---|---|---|---|
| v26.08.3 | Sep 16, 2026 | Verified | Initial | AWS · referenced |
Technical information
FAQ
How do I access Homer after deployment?
After the CloudFormation stack reaches CREATE_COMPLETE, open ResolvedLaunchUrl in the stack Outputs.
Where are application data and credentials stored?
Application data is stored at /www/assets inside the container on the retained encrypted EBS data volume. Edit /www/assets/config.yml through the instance terminal to organize links. The public dashboard has no built-in sign-in; do not place private information in its configuration.