-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
gutenberg
The Block Editor project for WordPress and beyond. Plugin is available from the official repository.
It might be worth mentioning that Lokl [0] seems to be from the same author [1] as the "wp2static" plugin [2], my and many others go to for static site generation of WordPress.
I find Lokl and interesting take, although the usual self-serve script is kind of annoying for power users (what I mean is that this bash scripts tried to do everything for you and it's less transparent), I recommend the repo [4] as the source of the actual Dockerfiles, that you could just reference in something like a docker-compose setup.
The Dockerfiles are kind of surprising since they read more like a an ansible-playbook than like a Dockerfile. This one image has it all - php, nginx, mariadb, phpmyadmin and who knows what else [4]. It's an interesting approach to Docker images, certainly against the recommendation but might have some good reasoning for something as special as WordPress.
[0]: https://github.com/leonstafford/lokl-cli
[1]: https://github.com/leonstafford
[2]: https://github.com/leonstafford/wp2static
[3]: https://github.com/leonstafford/lokl
[4]: https://github.com/leonstafford/lokl/blob/master/php8/Docker...
Looks interesting, but Devilbox is my go to environment. Very robust and supports nearly everything you’ll need.
- http://devilbox.org/
The site is not loading for me, but it originates from https://github.com/lokl-dev/lokl-www
It might be worth mentioning that Lokl [0] seems to be from the same author [1] as the "wp2static" plugin [2], my and many others go to for static site generation of WordPress.
I find Lokl and interesting take, although the usual self-serve script is kind of annoying for power users (what I mean is that this bash scripts tried to do everything for you and it's less transparent), I recommend the repo [4] as the source of the actual Dockerfiles, that you could just reference in something like a docker-compose setup.
The Dockerfiles are kind of surprising since they read more like a an ansible-playbook than like a Dockerfile. This one image has it all - php, nginx, mariadb, phpmyadmin and who knows what else [4]. It's an interesting approach to Docker images, certainly against the recommendation but might have some good reasoning for something as special as WordPress.
[0]: https://github.com/leonstafford/lokl-cli
[1]: https://github.com/leonstafford
[2]: https://github.com/leonstafford/wp2static
[3]: https://github.com/leonstafford/lokl
[4]: https://github.com/leonstafford/lokl/blob/master/php8/Docker...
It might be worth mentioning that Lokl [0] seems to be from the same author [1] as the "wp2static" plugin [2], my and many others go to for static site generation of WordPress.
I find Lokl and interesting take, although the usual self-serve script is kind of annoying for power users (what I mean is that this bash scripts tried to do everything for you and it's less transparent), I recommend the repo [4] as the source of the actual Dockerfiles, that you could just reference in something like a docker-compose setup.
The Dockerfiles are kind of surprising since they read more like a an ansible-playbook than like a Dockerfile. This one image has it all - php, nginx, mariadb, phpmyadmin and who knows what else [4]. It's an interesting approach to Docker images, certainly against the recommendation but might have some good reasoning for something as special as WordPress.
[0]: https://github.com/leonstafford/lokl-cli
[1]: https://github.com/leonstafford
[2]: https://github.com/leonstafford/wp2static
[3]: https://github.com/leonstafford/lokl
[4]: https://github.com/leonstafford/lokl/blob/master/php8/Docker...
Another alternative is wp-env, which is a small node wrapper over Docker. It’s meant to be very straightforward to use, though less powerful than other tools. It’s used for a lot of core editor development. You basically just have a JSON file pointing at whatever local source code you’re developing (or alternative options you need), wp-env start, and you’re good to go.
I’ve done a lot of development on the project, and it could always use more contributors: https://github.com/WordPress/gutenberg/tree/trunk/packages/e...