Are you sure that it can find the txt file (did you try a full path for that too) ? PHP's current path can be different than the one on your console. Show
All 6 Repliesrch1231 169 Posting Shark 2 things: 0 0 Share jrhitokiri 0 Newbie Poster 2 things: full path didn't help pasting it into command line, it functions normally and outputs the 2 lines (as mentioned in my orig post) Any other suggestions? 0 0 Share pritaeas 2,130 ¯\_(ツ)_/¯ Moderator Featured Poster Are you sure that it can find the txt file (did you try a full path for that too) ? PHP's current path can be different than the one on your console. 0 0 Share jrhitokiri 0 Newbie Poster Are you sure that it can find the txt file (did you try a full path for that too) ? PHP's current path can be different than the one on your console. Yep, fill path for both the grep command and the text file. 0 0 Share
smantscheff 265 Veteran Poster 11 Years AgoAlso have a look at the preg functions of PHP which might be much easier to handle than the external grep. 0 0 Share
jrhitokiri 0 Newbie Poster 11 Years Ago
The thing is, I'm searching a 1GB file and I fear that the preg is significantly slower than the grep external function. :< You probably heard from the new kid around the block called "Docker"? You are a PHP developer and would like to get into that, but you didn't have the time to look into it, yet? Then this tutorial is for you! By the end of it, you should know: - how to set up Docker "natively" on a Windows 10 machine - how to build and run containers from the command line - how to log into containers and explore them for information - what a Dockerfile is and how to use it - how containers can talk to each other - how Note: I will not only walk on the happy path during this tutorial. That means I'll deep-dive into some things that are not completely related to docker (e.g. how to find out where the configuration files for php-fpm are located), but that are imho important to understand, because they enable you to solve problems later on your own. But if you are short on time, you might also jump directly to . All code samples are publicly available in my Docker PHP Tutorial repository on Github. The branch for this tutorial is part_1_setting-up-php-php-fpm-and-nginx-for-local-development-on-docker. All published parts of the Docker PHP Tutorial are collected under a dedicated page at Docker PHP Tutorial. The following part is Setting up PhpStorm with Xdebug for local development on Docker . If you want to follow along, please subscribe to the RSS feed or to get automatic notifications when the next part comes out :) Table of contents
IntroductionPreconditionsI'm assuming that you have installed Git bash for Windows. If not, please do that before, see . Why use Docker?I won't go into too much detail what Docker is and why you should use it, because others have already talked about this extensively. As for me, my main reasons were - Symlinks in vagrant didn't work the way they should - VMs become bloated and hard to manage over time - Setup in the team involved a lot of work - I wanted to learn Docker for quite some time because you hear a lot about it In general, Docker is kind of like a virtual machine, so it allows us to develop in an OS of our choice (e.g. Windows) but run the code in the same environment as it will in production (e.g. on a linux server). Thanks to its core principles, it makes the separation of services really easy (e.g. having a dedicated server for your database) which - again - is something that should happen on production anyway. Transition from VagrantOn Windows, you can either use the Docker Toolbox (which is essentially a VM with Docker setup on it) or the Hyper-V based Docker for Windows. This tutorial will only look at the latter. A word of caution: Unfortunately, we cannot have other Gods besides Docker (on Windows). The native Docker client requires Hyper-V to be activated which in turn will cause Virtualbox to not work any longer. Thus, we will not be able to use Vagrant and Docker alongside each other. This was actually the main reason it took me so long to start working with Docker. Setup DockerFirst, download Docker for Windows (requires Microsoft Windows 10 Professional or Enterprise 64-bit). The version I am using in this tutorial is  After the installation finishes, we need to log out of Windows and in again. Docker should start automatically. If not, there should be a "Docker for Windows" icon placed on your desktop. If Hyper-V is not activated yet, Docker will automatically urge you to do so now. If you agree, Hyper-V and container features are activated and a reboot is initiated. See Install Hyper-V on Windows 10 to deactivate it again. Caution: VirtualBox will stop working afterwards! Starting one of my previous machines from the VirtualBox interface or via
After rebooting, Docker will start automatically and a welcome screen appears. We can ignore that (close the window). In addition, a new icon is added to your system tray. A right-click reveals the context menu. Open the tab "Shared Devices" and tick the hard drives on your host machine that you want to share with Docker containers. Note: We will still need to define explicit path mappings for the actual containers later on, but the hard drive that the path belongs to must be made available here. After clicking "Apply", you will be prompted for your credentials Next, open tab "Advanced". You don't actually have to change any of the settings but if you (like me) don't have Docker "physically" stores the container images in that location. Congratulations, Docker is now set up on your machine 😊 Setting up the PHP cli containerNow that we have the general stuff out of the way, let's set up our first container. I've created the directory Firstly, lets create a directory for our sourcecode: For the sake of simplicity, we will stick to the official PHP image and run: Which means: The result looks something like this: Since we don't have the image on our machine (see Now let's see if the container is actually running via Weird. For some reason, we don't see our newly created container there. Let's check with the Aha. So the container was created, but immediately stopped (see
This answer explains the difference between CMD and ENTRYPOINT quite well. Since we don't have a Dockerfile defined, we would need to look at the Dockerfile of the base image we're using, but I actually don't wanna go down this rabbit hole for now. Basically, the "problem" is, that the container doesn't have a long running process / service defined, (as the php-fpm or the nginx containers do later on). To keep the container alive, we need to add the But then this happens: Apparently, we cannot use the same name ( and try again afterwards: Sweet, so now that the container is up and running, let's "log in" via You might get the following error message If so, prefixing the command with A quick Remember the path mapping, that we specified? Let's create a simple "hello world" script on the windows 10 host machine at Should look like this on the host machine: And like this from within the container: Let's run the script in the container via Purrfect. We created the file on our host system and it's automatically available in the container. Installing Xdebug in the PHP containerSince we intend to use Docker for our local development setup, the ability to debug is mandatory. So let's extend our image with the xdebug extension. The readme of the official Docker PHP repository does a good job at explaining . For xdebug, we'll use PECL. To install the extension, make sure to be logged into the container and run You should see an output like this: The xdebug extension has been build and saved in That helper command will place the file which enables the extension. Btw. you can locate the additional php ini files folder by running Result: When we check the contents of that folder, we will indeed find the Now we'll log out of the container (type "exit" or hit Now we start the container again via log back in and check if xdebug is still there: And... it is! So the changes we made "survived" a restart of the container. But: They won't survive a "rebuild" of the container. First we stop and remove the container via The Then we rebuild it, log in and check for xdebug: ... which won't be there anymore. Note the new container ID (before: Persisting image changes with a DockerfileSimply put, a Dockerfile describes the changes we make to a base image, so we (and everybody else) can easily recreate the same environment. In our case, we need to define the PHP base image that we used as well as instructions for installing and enabling xdebug. To clearly separate infrastructure from code, we'll create a new directory at and give it the following content: Change to the The If you encounter the following error you probably missed the trailing Note, that the building takes longer than before, because Docker now needs to do the extra work of installing xdebug. Instead of using the base Aaaand we get an error, because we tried to use the same name ("docker-php"), that we used for the previous, still running container. Sigh.. fortunately we already know how to solve that via Retry Yep, all good. Btw. since we "only" want to check if xdebug was installed, we could also simply pass Be aware that this will create a new container every time it's run (, note the first entry with the wonderful name "distracted_mclean"): Before we move on, let's []stop and remove all containers via](https://coderwall.com/p/ewk0mq/stop-remove-all-docker-containers). The Setting up a web stack with php-fpm and nginxSince most people are probably not only working on CLI scripts but rather on web pages, the next step in this tutorial is about setting up an nginx web server and connect it to php-fpm. Setting up nginxWe're gonna use the official nginx image and since we don't know anything about that image yet, let's run and explore it a bit: yields Note that we only used the minimum number of arguments here. Since we did not specify a name, we will simply use the ID instead to log in (so be sure to use the one that your shell returned - don't just copy the line below :P) We would expect that there is an nginx process running, but upon checking with This is common when using docker images, because they are usually kept as minimal as possible. Although this is a good practice in production, it is kind of cumbersome in development. So, let's install and try again: Ah. Much better. Lets dig a little deeper and see how the process is configured via Sweet, so the configuration file is placed in the default location at ... and see Note the line So the server is listening on port 80. Unfortunately, we cannot reach the web server from our windows host machine, as there is currently (2018-05-31) an open bug for accessing container IPs from a windows host (don't worry, we'll fix that with port mappings in a second)). So, in order to verify that the server is actually working, we'll install Looks like this: Looks good! Now let's customize some stuff: - point the root to To make the changes become effective, we need to via Check with curl, et voilá: With all that new information we can set up our nginx image with the following folder structure on the host machine: Clean up the "exploration" nginx container, And then run the "new" container via where Thanks to the port mapping we can now simply open http://127.0.0.1:8080/ in a browser on the host machine and see the content of our If you want some more information about running nginx on Docker, check out this tutorial. Before we move on, let's clean up Setting up php-fpmWe are already familiar with the official docker PHP image but have only used the cli-only version so far. FPM ones can be pulled in by using the The first thing to note is, that the image automatically exposes port 9000 as a When we examine the Dockerfile that was used to build the image (click here and search for the "7.0-fpm" tag that currently (2018-05-31) links here), we can see that it contains an What else we can we figure out... First, will check where the configuration files are located via Hm - a relative path. That looks kinda odd? Let's get a little more context with the Ah - that makes more sense. So we need to resolve php-fpm ist listening on port 9000 on 127.0.0.1 (localhost). So it makes total sense to expose port 9000. Installing xdebugSince we probably also want to debug php-fpm, xdebug needs to be setup as well. The process is pretty much the same as for the cli image: Of course we'll also put that in its own Dockerfile: Clean up the test container and build the new image Connecting nginx and php-fpmNow that we have containers for nginx and php-fpm, we need to connect them. To do so, we have to make sure that both containers are in the same network and can talk to each other (which is a common problem). Docker provides so called allowing automatic service discovery. That basically means, that our nginx container can use the name of the php-fpm container to connect to it. Otherwise we would have to figure out the containers IP address in the default network every time we start the containers. reveals a list of the current networks Now let's add a new one called Start the nginx container and connect it to the new network via Finally, we need to mount the local code folder Note that we specified the network in the run command via the The "Containers" key reveals that the Log into the nginx container and ping the IP .. well, after we make the command available by installing We can ping the container - that's good. But we were also promised we could reach the container by its name And we can - awesome! Now we need to tell nginx to pass all PHP related requests to php-fpm by changing the Note the and open http://127.0.0.1:8080/hello-world.php on a browser on your host machine. Btw. there's also a good tutorial on geekyplatypus.com on how to Dockerise your PHP application with Nginx and PHP7-FPM. But since it's using docker-compose you might want to read the next chapter first :) Putting it all together: Meet docker-composeLets sum up what we have do now to get everything up and running: 1. start php-cli 2. start nginx 3. start php-fpm Hm. That's alright I guess... but it also feels like "a lot". Wouldn't it be much better to have everything neatly defined in one place? I bet so! Let me introduce you to docker-compose
Lets do this step by step, starting with the php-cli container. Create the file Before we get started, we're gonna clean up the old containers: To test the docker-compose.yml we need to run Note that the image is build from scratch when we run Logging in and running works as before Now log out of the container and run to shut the container down again: Add the remaining services to the And up again... Only nginx and php-fpm needed to be built because the php-cli one already existed. Lets check if we can still open http://127.0.0.1:8080/hello-world.php in a browser on the host machine: Yes we can! So instead of needing to run 3 different command with a bunch of parameters we're now down to The tl;drThe whole article is a lot to take in and it is most likely not the most efficient approach when you "just want to get started". So in this section we'll boil it down to only the necessary steps without in depth explanations.
Your application code lives in the Wrapping upCongratulations, you made it! If some things are not completely clear by now, don't hesitate to leave a comment. Apart from that, you should now have a first idea on what docker is and how you can use it. If you want to go deeper, please check out the remaining articles of the Docker PHP Tutorial series. Please subscribe to the RSS feed or to get automatic notifications when this next part comes out :) Wanna stay in touch?Since you ended up on this blog, chances are pretty high that you're into Software Development (probably PHP, Laravel, Docker or Google Big Query) and I'm a big fan of feedback and networking. So - if you'd like to stay in touch, feel free to shoot me an email with a couple of words about yourself and/or connect with me on LinkedIn or Twitter or simply subscribe to my RSS feed or go the crazy route and subscribe via mail and don't forget to leave a comment :) Subscribe to posts via mailEmail Address First Name We use Mailchimp as our newsletter provider. By clicking subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices here. |
Cara menggunakan php exec grep
Pos Terkait
Copyright © 2024 idkuu.com Inc.
