Once you have created the first configuration of your basic Docker stack, it is time to move the Symfony’s files into Docker’s web server service.
This will make us able to run the symfony application from inside the web server container, getting the real benefits of using a system as Docker (same environment on any machine, above all).
Starting to use Docker is not an easy task. Starting to use Symfony on Docker is far more complex.
There are too many things to understand before being able to dockerize a Symfony application.
I studied Docker for more than one month before being able to dockerize our Symfony applications.
How did I reach the goal? By trial and error. A lot of trial and error. And a lot of reading. Really really a lot of reading.
But I can make your journey a lot easier and this series of posts is exactly this: the final summary of my journey trying to dockerize our Symfony applications here at Serendipity HQ.
The main advantage of having a Genestrap-based WordPress theme is the ability to use the tools and the techniques you already use to develop your web apps.
Using a framework like Genesis to develop a WordPress theme takes the management of WordPress to a whole new level of complexity (and fun, too!).
So, once you have created the first version of your Genestrap-based WordPress theme, let’s see how to prepare your environment to manage the updates you will do developing your custom theme.
Building a WordPress theme from scratch can be a really heavy task.
But buying a stock theme may not always be an option.
The result is that you need to develop your theme from scratch.
And if you would like to use Bootstrap, the task may become very complex very fast.
Genestrap is the perfect solution: easy, fast and flexible.
And you can develop seriously, without being a mere WordPress “point-and-clicker”!
The identification of users is the second pillar of behavioural tracking, together with the understanding of events.
Identifying users precisely makes you able to track the complete journey of any user to understand why exactly (s)he signed up or goes away, making you able to uncover hidden causes that you can improve or use to improve your KPIs and your bottom line.
But the identification of users is not so simple as it may seem at a first look.
The easiest way to start using concretely a behavioural analytics tool is to start tracking some events.
This way you will see them registered in the behavioural analytics tool of your choice, and you can start better understanding how they work.
As told, in theory is all simple.
But the problems arise when you have to concretely decide which events to track.
When it comes to tracking the numbers of your SAAS product, Google Analytics is not sufficient anymore. This is the hard truth, believe it or not.
To go one step further, you need to properly implement a behavioural tracking analytics tool and think about your SAAS product differently.
Integrating behavioural tracking thoughts into the ones about your SAAS product can be tricky. Really tricky.
If in theory, the things are really simple, when you arrive at the point of concretely define what to track you may become really confused.
I’m going to explain to you exactly what changes in your thoughts about your SAAS application when you think at behavioural tracking and how to plan and implement it properly.
Any web project has basically 4 kind of places where images reside:
Symfony’s Webpack Encore is great to manage the first two places as it is able to manage the images referenced in the CSSes and to manage fonts (as they are handled as CSSes are).
The third group of images, the ones in the cloud, have not to be managed by Webpack but by another bundle like LiipImagineBundle.
So we are left only with the fourth group: the static images.
Maybe you need to use the Doctrine’s command line while you are developing a Symfony Bundle (or anything else).
This will make you able, for example, to validate the schema or to convert an annotated schema to its XML counterpart.
Here is how to use Doctrine command line outside of a Symfony Application.
The message “SSL certificate problem: unable to get local issuer certificate” shows up when trying to connect to Magento Connect or when, generally, you try to use cURL to connect to a remote web site.
This error happens because cURL cannot find a cacert.pem file from which take the trusted signatures.
Read more
Are we helping you?
You can thank us with a Like!