prequel | Interactive MySQL query editor for the terminal | Command Line Interface library

in your template update to

There's some ambiguity regarding the term nodes (see XPath difference between child::* and child::node()) and the term contains (see How to use XPath contains() for specific text?) when being less than perfectly precise, but one of the following XPaths will likely meet your needs:

1. All nodes whose string value contains the substring, "John":

Here is how you can use re:

At the end of the conclusion list, it tells you it wants to install php-tmdb/api: 2.1.x-dev.

If you go to that project's repo, you'll notice there's a v3 available.

v2 of php-tmdb/api wants "symfony/event-dispatcher": ">=2.4,<5" - that collides with laravel's constraint.

Solution: require php-tmdb/api: 3.0

https://github.com/php-tmdb/api/releases

As Islingre noted, there are dangers to this approach due to cyclic dependencies or multiple prequels. However, the basic idea is to use a recursive CTE:

Prequel isn't a database itself. It's a tool to manage databases. You still need to run MySQL and your database configuration values need to be the same as before (before you installed Prequel).

The database configuration values you see in the Prequel config is meant to tell Prequel where your (existing) database is.

Please, latter on let us know the actual use you had to this solution :-)

It's been a very interesting and enjoyable challenge.

Here's the solution:

Only difference I am seeing here is http:// in your Playground and https:// in your Postman.

So just replace http:// with https:// in your Playground.

You talk about communication between your server and the web server but there isn't any; the web server is serving a page to the browser that includes references to resources on your server, so the browser is communicating with your server, and it is the browser which distrusts your self-signed cert.

HTTPS on the communication between the browser and your server is beneficial if the network between the browser and your server is either actually insecure (e.g. includes a DMZ or other untrusted zone or insecure link) or must be treated as insecure (e.g. handling payment-card data under PCI DSS). It's impossible to evaluate that from the information you've given, and your company almost certainly shouldn't permit you to publish the information that would make it possible -- plus it wouldn't be useful to anyone else, which is against the StackExchange philosophy. You should be consulting with the people in charge of security on your company's network as to whether HTTPS is required, and probably what options are possible and what they might support or assist with.

It's true you can't get a publicly-trusted cert for localhost, but that doesn't matter because you aren't using localhost. You are using a private (rfc1918) aka 'intranet' address, which is quite different, but you can't get a publicly-trusted cert for those either.

The apparent technical options are:

• use a self-signed cert (for the address) and configure every browser that will use this application to trust that cert. This may vary depending on what your users will be like, and how many they are. If they are all on domain-joined Windows and using IE/Edge or Chrome but not Firefox, the central admins might just create a GPO that 'pushes' the cert and you're done. If there are thousands on a dozen platforms and located around the world, you may need to spend months of effort to train and assist all of them to import the cert, possibly including getting people to translate into foreign languages.

  In case you aren't already aware, if any of your users use Chrome, the cert must have the authority-name, here the address, in Subject Alternative Name (SAN) as well as Subject CommonName. Other browsers don't currently require this, but may in the future because it's been CABforum policy for quite a while. Many tools commonly used to create selfsigned certs, like OpenSSL commandline and Java keytool, don't do this automatically. (Public CAs do.) There's lots of Qs on this already, you can search for them if applicable.

  Also for this approach, unless you already know, you should verify the address assigned will remain stable. Some company networks need to rearrange their address assignments from time to time, for reasons like offices were opened or expanded or closed, major projects were moved, etc. If thousands of people have to repeat the unfamiliar and arcane cert import several times every year, you will become pretty unpopular.

• get a (sub)domain name for your system under the company's domain that resolves on the company's internal network only to your machine's address -- that resolution doesn't need to be, and shouldn't be, public. Then get a publicly-trusted cert for that subdomain name. LetsEncrypt using DNS-01 can issue you a cert for a domainname even though no system using that domainname is reachable from the public Internet, as long as you control the DNS for it. OTOH if your company already has a web presence and certs, it should already have a process established for obtaining them; the network security people I mentioned above should know about that.