Sometimes we make mistakes. When first learning docker we probably make many mistakes and end up with tons of unused docker images.
If you are on Linux like me, you won’t have a desktop dashboard like Mac and Windows get, so things are harder. To see a list of what images you have created you use the following command
docker ps -a
That command will output something like this.
It will show the CONTAINER ID, IMAGE, COMMAND etc. as you can see. To delete an image you use the container id with docker rm like this.
docker rm b5f8fae52bce
I’ve seen older internet posts using the IMAGE value but I had no success with that method. I am guessing something changed. I didn’t even see an example of this I just tried it. I don’t see any mention of this in the docs either. But it works. This part in the getting started intro actually explains it. I think something did change.
First what I wanted to do was create a cookie in a Controller and display a template at the same time. Sort of like when a user visits a page you set a page count or something. The documentation doesn’t really show an example, you are expected to know it via “common sense” apparently according to one smartass.
There is more than one way I have discovered over time. Apparently you can use render the same way I show using renderView.
Below is the Symfony Cookie class create method comment/documentation. This is all of the values you can supply when creating a cookie.
/** * @param string $name The name of the cookie * @param string|null $value The value of the cookie * @param int|string|\DateTimeInterface $expire The time the cookie expires * @param string $path The path on the server in which the cookie will be available on * @param string|null $domain The domain that the cookie is available to * @param bool|null $secure Whether the client should send back the cookie only over HTTPS or null to auto-enable this when the request is already using HTTPS * @param bool $httpOnly Whether the cookie will be made accessible only through the HTTP protocol * @param bool $raw Whether the cookie value should be sent with no url encoding * @param string|null $sameSite Whether the cookie will be available for cross-site requests * * @throws \InvalidArgumentException */
If you create a cookie like this :
Then the cookie will only live/exist until the user closes their browser(unless your browser restores from your last session). You must supply an expires time to make it persist beyond closing the browser. Providing an expires time gives you better control over when the cookie expires due to the above mentioned browser restore issue which will restore cookies that should have died on browser close.
You can also create the cookie then pass it to setCookie() like this.
$response = new Response(); $expires = time() + 36000; $cookie = Cookie::create($cookieName, $cookieValue, $expires); //$cookie = $response->headers->setCookie(Cookie::create('foo', 'bar')); $response->headers->setCookie($cookie); $content = "<html><body><h1>Learning symfony cookie creation techniques?</h1></body></html>"; $response->setContent($content); $response->headers->set('Content-Type', 'text/html'); return $response;
Here I set the expires to a number, time() returns a linux/unix timestamp and I added 36000 seconds or 10 hours to it. This cookie will exist until the user refreshes their page or clicks a link in 10 hours from creation. However long you want it to live you add that many seconds. Or you could create a date using PHP DateTime as you can pass a DateTime object to the expires position. You then use the methods of DateTime to increase the time to a period in the future and pass the DateTime object after calling the methods to do so.
Side Note : in the above code, you can create a cookie without the $response->setContent() call. I do that with the body tag so that the profiler will show up at the bottom of the page for debugging.
That code goes inside a controller method for the requested route by the way. Usually you use the render() method inside a controller to send a response, which renders the template and sends it in a response. You can also use renderView to do the same thing and capture the value in a variable then use setContent or just make the renderView call right in setContent. I know that works. You can also store the returned value from render the same way. But no matter how you do it, you must return the response object, the very last line. You can find all the methods of the Response class here in the source code.
If you wanted to render a view which requires variables to be sent you do it like this and capture the output of renderView().
$content = $this->renderView('blog/display_article.html.twig', [ 'title' => $title, 'article' => $article, 'tags' => implode(', ', $tags), 'tagLinks' => $links, 'edit' => $editLink, 'affiliateUrl' => $affiliateUrl, 'backButton' => $backButton ]);
Note : do not just use php setcookie or setrawcookie. The reason is they start sending output headers to the browser, which may interfere with how symfony works. You probably won’t notice in a browser, but you may get errors when testing your controllers with functional tests etc.
Personally I created a huge class which extends DateTime which has all kinds of methods for adding days, hours, removing them and doing other math. I’d share it on github but it has bugs since I wrote it way back in version 5 of php in 2012. Some changes were made to DateTime and I haven’t had time to review them all and hunt down the changes that need to be made yet. I’ll probably do it and add it to github eventually. But for now I use time() + seconds. It’s not the best solution but it works and I only need this one cookie.
And another person found me more hidden docs about cookies, I wish I had this days ago.
As another note. Any values you put in a cookie you must sanitize before trying to use them in any way since users can access and change regular cookie values.
I can never ever remember where I see anything ever I read entirely too much about entirely too many subjects. I mostly use this site as my own personal google.
To clear all caches
php bin/console cache:pool:clear cache.global_clearer
I have trouble navigating the Symfony documentation so I create lists of links here so I can just easily find what I need again later.
MigrationsBundle link and info -> shows how to run migrations and all of the doctrine migration related commands
Doctrine Symfony overview -> more information about doctrine and migrations.
Most documentation sucks. It seems most authors have this idiotic idea that whatever is in their head, all their knowledge etc. magically transfers to the user as they read it. These are the same kind of idiots you meet in society that drone on about shit they understand to the totally uninitiated like they are talking to a pro. These are the kind of idiots that while talking don’t even have the ability to notice their true live audiences eyes glazing over and heads shaking in confusion. Nope these idiots are comfortable being idiots and we have to suffer. I don’t get it.
Ever been reading along documentation and the author just keeps throwing out concepts/terms left and right without even giving a link, leaving you in the dark like WTF? Isn’t it fun?
Here is a tip to anyone who writes documentation. No matter how stupid simple a concept seems to you, there will be people, many people who have never come across the concept. Instead of being a snobby dickhead with an attitude like “Well you have to have a minimum idea of how blah blah blah works because I do”. You should provide information, links etc. to any concept that anyone may not have encountered. It is not that damn hard and doesn’t take much time and it makes you look much smarter and much less conceited and narcissistic.
This is the exact reason I started this website. So much of the documentation for everything sucks ass. Most documentation I come across these days leaves me saying WTF. Look at openssl or openssh or example so many WTF’s in those docs.
And what is worse is the assholes who write blogs who just copy other blog posts. So you get entire search pages full of shit articles all repeating the same wrong shit that doesn’t work. Then that shit information ends up on stackxxxx.com sites from idiot kids who copy and paste shit for points and don’t care if the answer is right, they just want popular points. I often just avoid stack sites these days. Those sites are only handy if you are doing the most basic simple shit. Once you go into complex issues those sites are wrong answer land 100% of the time.
I use so many languages and tools I can never even remember the most simple shit about anything anymore . This is how you start symfony encore webpack.
yarn run encore dev --watch
Symfony docs how to start encore
The idea is to have a way for an admins to SSH into a server without having to use passwords. This adds a level of security to your server setup. Without private keys you have to enter your user name and password. This can be less secure than generating SSH keys and adding your public key to SSH, plus with keys you don’t have to remember passwords.
First you need to generate the SSH keys. I prefer the ed25519 algorithm which is a newer one. You can get more info here.
The code to create an ed25519 ssh key in the current users .ssh directory will look like this.
ssh-keygen -f ~/.ssh/key-name -t ed25519
The -f flag tells ssh-keygen the name of the files you want to create. The above command would create key-name(private key) and key-name.pub(public) key, in the current users .ssh directory. The ~ is a Linux shortcut meaning /home/current_user/ so you don’t have to type all that.
The -t flag tells ssh-keygen what type of algorithm to use. If you don’t specify the -f flag and give the file a name, then both files are output in the current users .ssh directory as ed25519 and ed25519.pub
Here I won’t be doing much explaining, just listing links so people can read about this befuddling issue.
It often boggles my mind how differently you must write shell scripts vs the command line commands. It is often very inconsistent, I hate inconsistencies.
Basically Aliases within Linux shell are not recognized without some fancy hacky code, WOOHOO. So you will lose your mind if you are trying to set and use aliases in shell scripts.
You can set aliases all day long, but your scripts wont use them.
Yes you read that correctly. You can set aliases in your script, even right before you want to use it and Linux is like GTFO, I have no idea what that is. It even fails without a notice/error most times. What you can do is set a normal variable and use it in place of an alias though.
Say you had a script named do-this-thing.sh and it was located deep in a directory like /etc/directory/directory/directory/directory/do-echo “$yarnBin” > /etc/profile.d/server-alias.shthis-thing.sh
You could do the following in BASH
not_alias=/etc/directory/directory/directory/directory/do-this-thing.shalias not working inside bash shell script bash not_alias
The above would execute the do-this-thing.sh file. You can also permanently set aliases in your Shell script. This is handy even if you can’t use the aliases in your script directly, you can use them in the terminal command line later.
To permanently set aliases alias when not working inside bash shell script place them in your .bashrc file for the user you are logged in This is usually located in /home/username/.bashrc or you can put it in the user profile .profile file or other places.
How you do this varies by Linux shell.