i think for the start, we could create an Ansible role which can be used for local and production deployments
it’s helpful to keep things apart from each other. so basically i see a setup like:
webserver-container (nginx or apache)
db-container (mariadb)
wordpress-container (themosis)
a big plus is that you can run all three on the same machine or split them apart on 3 cloud server instances. provisioning can be done with ansible too.
webserver-container (nginx or apache)
db-container (mariadb)
wordpress-container (themosis)
a big plus is that you can run all three on the same machine or split them apart on 3 cloud server instances. provisioning can be done with ansible too.
@jlambe are there already plans for official provisioning scripts/repos?
@Dave3o3 At this moment no plans. I’ve personnaly worked with homestead (which is provided now by default on version 2.0) and docker. It’s hard to provide a formula that works for everyone. I’m also a big fan of Ansible and one project that might interest people is Ansistrano: https://ansistrano.com/
Also, for local development, I would love an easy script for using Docker as my hard drive is filled with too much vms :laughing:
yeah, i know what you mean
therefore a official docker repo makes sense imho
you can have one vm with all the docker containers you need ;)
if one would like to create a Dockerfile, which base OS should one use?
besides that one could use ubuntu as base image ofc
It’s been sometimes now but perhaps for local development, a good start point would be to generate a docker compose file with everything needed. Last I’ve done this, my only complain is that the requests were very slow on docker for Mac. Nowadays, don’t know if the issues regarding the filesystem layer are fixed.
so in the end you have your local docker-vm setup with
vagrant up
and for those who don’t want the VM, they can use the plain docker-compose
but i like to try it
short question regarding the needed extensions: the intl extension is already bundled with php, right?
This extension is bundled with PHP as of PHP version 5.3.0. Alternatively, the PECL version of this extension may be used with all PHP versions greater than 5.2.0 (5.2.4+ recommended).
On a Homestead environment it is enabled and normally most host providers compile it.
@JaspervanV_gitlab The custom fields interface is built only with javascript. When you define a custom field for a metabox, its UI is handled by a js component built with ReactJs. This is only available when working with metabox and custom fields. Custom fields for settings page or regular forms, are html only.
@marcwieland95 Basically controller dependencies are handled automatically wherever you use it. Auto-injection does not work if called from an
Action::add method because it’s not handled by the service container, it is handled by call_user_func functions which cannot resolve dependencies. I’ve tried to find a way to make use of the service container for hook classes but without luck.
@jlambe When I call something like that:
$controller = new BlockController();
$controller->map($block, $content, $is_preview);I should be able to resolve models inside the controller, right? public function map(Post $post, $post_new) {
This is not the case. I get an error: Argument 1 passed to Theme\Controllers\BlockController::map() must be an instance of Theme\Models\Post, array given
When calling a method directly, you have to pass expected objects. Personnaly I’ve never had to call a controller this way. So if your
map method signature is expecting as the first argument a Post model, your $block variable must be an instance of such model. The controller will not try to convert it if this is something you were expected.
Do you already have any further ideas about using blocks inside Themosis?