shinsenter/phpixie🔋 (PHP / PHPixie) Production-ready Docker images with automatic PHPixie installer.
The Docker images are available for both Debian and Alpine versions.
ℹ️ Note: These Docker images won’t be updated anymore since it looks like the framework hasn't been active in a long time. You can still use the old Docker images. If you hear about any updates to the framework, please let us know.
Our PHP Docker images, available on Docker Hub, are designed for easy configuration of PHP and PHP-FPM settings via environment variables. This approach eliminates the need to rebuild images when making configuration changes.
These images also come with the latest version of Composer, enabling you to start projects quickly without additional installations.
![shinsenter/php]([***]
Check out our documentation to learn how to customize these Docker images for your projects.
When you mount an empty directory into the container, it will automatically download the entire source code for the framework, allowing you to bootstrap a new project quickly.
shellmkdir myproject
shelldocker run -p 80:80 -p 443:443 -p 443:443/udp \ -v ./myproject:/var/www/html \ shinsenter/phpixie:latest
The container will detect the empty directory mounted to /var/www/html and clone the framework source code into it.
You can mount your application code from your host machine to the /var/www/html directory inside the container.
Because the source code is mounted as a volume, any changes made on the host machine will be reflected inside the container. This setup allows you to run builds, tests, and other tasks within the container while keeping your code on the host.
The Docker images come with pre-generated SSL certificate files for testing HTTPS locally:
To use valid HTTPS certificates for your production website, replace these files with your own valid SSL certificates. You can do this by copying or mounting your certificates from the host machine into the container. Simply overwrite the default certificate files with your valid certificate and key files to enable true HTTPS for your production website.
DockerfileFROM shinsenter/phpixie:latest # Copy your own certs into the container COPY my_domain.crt /etc/ssl/site/server.crt COPY my_domain.key /etc/ssl/site/server.key # Add your instructions here # For example: # ADD --chown=$APP_USER:$APP_GROUP ./myproject/ /var/www/html/
shelldocker run -p 80:80 -p 443:443 -p 443:443/udp \ -v ./myproject:/var/www/html \ -v ./my_domain.crt:/etc/ssl/site/server.crt \ -v ./my_domain.key:/etc/ssl/site/server.key \ shinsenter/phpixie:latest
ymlservices: web: image: shinsenter/phpixie:latest volumes: - ./myproject:/var/www/html - ./my_domain.crt:/etc/ssl/site/server.crt - ./my_domain.key:/etc/ssl/site/server.key
The release versions on this GitHub repository don't guarantee that Docker images built from the same source code will always be identical.
We build new Docker images daily to ensure they stay up-to-date with the latest upstream updates for PHP, base OS, Composer, etc. The images in this repo are regularly updated under the same tag names.
But you can pull the image from shinsenter/phpixie:latest,
and tag it with a name that indicates its stability,
such as your-repo/phpixie:stable using the below commands:
shelldocker pull shinsenter/phpixie:latest docker tag shinsenter/phpixie:latest your-repo/phpixie:stable docker push your-repo/phpixie:stable
Then use the image your-repo/phpixie:stable as a base image to build containers for production.
If you find these images useful, *** donating via *** or opening an issue on GitHub.
Your support helps maintain and improve these images for the community.
This project is licensed under the terms of the GNU General Public License v3.0.
I appreciate you respecting my intellectual efforts in creating them. If you intend to copy or use ideas from this project, please give proper credit.
From Vietnam 🇻🇳 with love.
探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务