You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've been working for about two years now with the Hypernode image and made several modifications on top of it to make it suit our needs even more. I think everyone can benefit from a few of these modfications.
Are you open to implement some in the base image? I could share the modifications.
Some examples:
We added shortcut scripts to enable/disable xdebug, separate for cli/fpm.
We added environment variables to be used in docker-compose.yml to control starting of MySQL (we use a centralized MySQL container for all Hypernode containers), MailHog, Varnish and ElasticSearch.
Select PHP version using an environment variable
Added environment variable to use another relay host (we use it for staging environments where MailHog is just too basic).
Switch to another NodeJS version using an environment variable.
Install the Magento cron on startup, controllable by environment variable.
Hey @markvds we want to keep this hypernode-docker repo as 'similar to a real hypernode' as possible so turning off things like nginx ratelimiting might go against other people's use cases. The whole idea is that you don't have to find out that things are slightly different in the real environment only once you deploy to your production Hypernode.
Anyway we do encourage people building on top of hypernode-docker for whatever suits their use-case and in whatever way that fits their process. If you have a github project (fork / adaptation / anything that uses the hypernode-docker image) / a blog post about how you do things / or some example docker-compose configs that you use I'm sure it will be helpful for other users to get to see those as well.
Activity
vdloo commentedon Jan 20, 2022
Hey @markvds we want to keep this hypernode-docker repo as 'similar to a real hypernode' as possible so turning off things like nginx ratelimiting might go against other people's use cases. The whole idea is that you don't have to find out that things are slightly different in the real environment only once you deploy to your production Hypernode.
Anyway we do encourage people building on top of hypernode-docker for whatever suits their use-case and in whatever way that fits their process. If you have a github project (fork / adaptation / anything that uses the hypernode-docker image) / a blog post about how you do things / or some example docker-compose configs that you use I'm sure it will be helpful for other users to get to see those as well.
We have seen some cool spin-offs, stuff like that we like to feature in our README.md (see here: https://github.com/ByteInternet/hypernode-docker#inspiration). If you have something that you think might fit that category we'll be happy to add it there as well. We've also had people adding example configurations to this repository: https://github.com/ByteInternet/hypernode-docker/tree/master/examples we'd be happy to accept PRs for something like that as well of course.