38 lines
1.7 KiB
Markdown
38 lines
1.7 KiB
Markdown
# Custom Portainer Configurations
|
|
|
|
This repository contains my personal Portainer configuration files and templates used to deploy and manage containers and stacks with Portainer.
|
|
|
|
## Purpose
|
|
|
|
This repo holds reusable, opinionated configurations for Portainer including stack templates, compose files, and custom settings I use across projects and environments. It exists to:
|
|
|
|
- Keep Portainer templates and example stacks in a single place
|
|
- Make it easy to reuse, version, and share configurations across machines
|
|
- Provide a reference for how I structure and deploy services via Portainer
|
|
|
|
## What's Included
|
|
|
|
- `stacks/` - Docker Compose stack files and examples for common services
|
|
- `templates/` - Portainer app templates (JSON/YAML) for easy import
|
|
- `README.md` - This document explaining the repo's purpose and usage
|
|
|
|
If any of these folders are not present yet, they may be created over time as I add configurations.
|
|
|
|
## How to Use
|
|
|
|
1. Browse the `templates/` and `stacks/` folders to find a stack or template you want to run.
|
|
2. In Portainer, go to Stacks or App Templates and either paste the Compose file or import the template JSON.
|
|
3. Adjust environment variables and volumes to match your host environment.
|
|
4. Deploy and monitor through the Portainer UI.
|
|
|
|
Notes:
|
|
|
|
- These files are intended as starting points. Always review and adapt them before deploying to production.
|
|
|
|
## Contributing / Customizing
|
|
|
|
- To add a new stack or template, create a new file under `stacks/` or `templates/` and open a pull request.
|
|
|
|
## License
|
|
|
|
These configurations are for personal use. If you want to reuse or adapt them, feel free to do so — consider adding a license file if you plan to share broadly. |