WEBVTT 1 00:00:04.639 --> 00:00:08.119 Hey, everybody, welcome to another episode of the Ruby Rogues podcast. 2 00:00:08.560 --> 00:00:11.640 I am your host today, Valentino Stul and I'm joined 3 00:00:11.679 --> 00:00:12.519 by our. 4 00:00:12.439 --> 00:00:13.359 Co host Ayush. 5 00:00:14.000 --> 00:00:14.199 Hello. 6 00:00:14.279 --> 00:00:19.320 Hello, and we have a very special guest today, Joseph. 7 00:00:20.280 --> 00:00:23.320 Do you want to introduce yourself and tell everybody why 8 00:00:23.359 --> 00:00:24.600 you're Ruby famous here? 9 00:00:24.719 --> 00:00:30.519 Yes? Hello everyone, So I'm Yoseph. I am a freelance 10 00:00:30.519 --> 00:00:36.960 software engineer and apparently now also a book author. I 11 00:00:37.119 --> 00:00:41.240 wrote two books. The first one was called Diploma from 12 00:00:41.280 --> 00:00:46.039 Scratch and the second one is called Kamal Handbook, and 13 00:00:46.119 --> 00:00:48.679 that's probably by VR here today. 14 00:00:52.079 --> 00:00:54.320 Yeah, you know that Kamala is like the one of 15 00:00:54.359 --> 00:00:57.200 the latest crazes with all the new reels announcements that 16 00:00:57.240 --> 00:01:00.000 came out of raals World. So it's kind of exciting 17 00:01:00.079 --> 00:01:04.400 to have an expert here, or at least somebody who 18 00:01:04.480 --> 00:01:08.760 has dove into the trenches and put together all the 19 00:01:08.760 --> 00:01:12.959 details for us to, you know, expose the secrets of 20 00:01:13.040 --> 00:01:14.640 how minimalistic it is. 21 00:01:14.959 --> 00:01:15.959 I hope. 22 00:01:15.439 --> 00:01:18.599 I honestly haven't had a chance to play with Kamal, 23 00:01:18.680 --> 00:01:22.159 so I'm looking forward to hearing your take on how 24 00:01:22.200 --> 00:01:23.120 it all comes together. 25 00:01:24.319 --> 00:01:27.799 Yeah. I did a deployer or two before the show just. 26 00:01:29.439 --> 00:01:29.840 So I know. 27 00:01:32.400 --> 00:01:36.000 So I guess we can start maybe at a high level, 28 00:01:36.159 --> 00:01:41.040 like you know, what does the deployed process like look like? 29 00:01:42.920 --> 00:01:47.959 You know, maybe before Kamal and why Kamal is even here. 30 00:01:50.799 --> 00:01:54.280 Yeah, so maybe it would be interesting to see it 31 00:01:54.319 --> 00:01:58.000 from the point of forty seven Signals, because they are 32 00:01:58.079 --> 00:02:03.040 the company behind Come right was actually started by David 33 00:02:03.079 --> 00:02:07.000 helmer Hanson, so o profrails. He also started coming up 34 00:02:07.680 --> 00:02:13.080 and they were doing the deployment with a capistannel, which 35 00:02:13.120 --> 00:02:18.159 is a simple Ruby deployed tool. You basically have all 36 00:02:18.280 --> 00:02:23.960 your little tasks are predefined in Ruby and then you 37 00:02:24.000 --> 00:02:28.439 simply run them they're under the server and something happens. 38 00:02:28.560 --> 00:02:31.319 You know. Capis Channel at the time didn't do much 39 00:02:31.360 --> 00:02:36.159 assumptions about what you'll be on the server or so on. 40 00:02:36.240 --> 00:02:39.919 You could define your own tasks so you could drive 41 00:02:39.960 --> 00:02:42.560 the deployment the way you wanted. It was simply a 42 00:02:42.599 --> 00:02:48.560 tool given to you and then the jumped as everybody 43 00:02:48.560 --> 00:02:53.319 else on this Kubernetes train, right like a big deployment 44 00:02:54.960 --> 00:02:58.639 that have infinite scale. And to me at the time, 45 00:02:58.719 --> 00:03:01.560 I was I remember I was a little bit sad 46 00:03:01.759 --> 00:03:08.159 because I was like they were the heroes of kind 47 00:03:08.199 --> 00:03:14.159 of marketing this simple way of deployees right, so not 48 00:03:14.280 --> 00:03:20.879 everybody has to be on Kuberneti's And then it was 49 00:03:20.919 --> 00:03:26.919 announced that they are making the leaf from cloud right 50 00:03:27.639 --> 00:03:31.240 the big saving journey of leaving the cloud, and I 51 00:03:31.280 --> 00:03:34.560 know they wanted to make Cournetti's work. They went to 52 00:03:34.639 --> 00:03:38.800 some vendors, you know, from Susan and so on, and 53 00:03:39.080 --> 00:03:43.039 David was talking writing about that. But then he was 54 00:03:43.080 --> 00:03:46.319 fairly thinking, okay, maybe we can do something on our own, 55 00:03:46.719 --> 00:03:50.400 which is not chilly, so unusual for David, I would say, 56 00:03:51.439 --> 00:03:56.159 And so they kind of went back to capistannel routes. 57 00:03:56.439 --> 00:04:03.560 But for the new container, Era is designed around Docker 58 00:04:04.120 --> 00:04:07.240 from the ground up, you know, and because of that, 59 00:04:07.520 --> 00:04:12.240 it also made some assumptions to make something a little 60 00:04:12.240 --> 00:04:16.800 bit easier. So what state is the ssh kit which 61 00:04:16.800 --> 00:04:20.600 is like Ruby library that simply connects over SSH to 62 00:04:20.680 --> 00:04:29.639 your server, but instead of running some just pure best code, 63 00:04:30.279 --> 00:04:34.879 you still run. You still run tasks, but they are 64 00:04:34.959 --> 00:04:40.079 usually around running Docker commands. So kamaka install Docker and 65 00:04:40.120 --> 00:04:47.480 then simply run various Docker commands tasks. The simplest way 66 00:04:47.600 --> 00:04:50.240 how you can think about it at the simplest level 67 00:04:50.319 --> 00:04:55.240 is simply that can will connect and run docor run 68 00:04:56.560 --> 00:05:00.920 name of your application, you know, and it doesn't even 69 00:05:01.199 --> 00:05:07.360 have a specific Docker pull task, for example, because that's 70 00:05:07.439 --> 00:05:11.720 already something that Docker does itself. So comma. Really it 71 00:05:11.839 --> 00:05:16.000 trives to be as minimalistic as possible and as simple 72 00:05:16.040 --> 00:05:20.759 as possible. There are some limitations to that, of course, 73 00:05:21.199 --> 00:05:24.959 and I would say the simplicity may be confused people 74 00:05:25.040 --> 00:05:29.759 sometimes because as you said, so what is the deploy process, right, 75 00:05:30.279 --> 00:05:34.319 And usually I would say before the deploy itself, you 76 00:05:34.439 --> 00:05:38.600 prepare the server beforehand, which we can call provisioning, you know. 77 00:05:39.240 --> 00:05:41.680 Part of that's that can be even spinning up the 78 00:05:41.800 --> 00:05:44.879 virtual machines, for example, is what most people would probably 79 00:05:44.920 --> 00:05:48.839 do unless you have physical servers, and then installing some software, 80 00:05:48.879 --> 00:05:52.800 firewalls and so on. It's just that it's come out. 81 00:05:52.879 --> 00:05:56.000 We don't need anything else for the come out to work. 82 00:05:56.439 --> 00:06:00.720 Then Docker and even Docker can be installed by so 83 00:06:00.759 --> 00:06:03.160 it simplifies it a lot, but it's still like one 84 00:06:03.199 --> 00:06:07.079 piece of a puzzle. Maybe you need other tools you 85 00:06:07.160 --> 00:06:10.519 want to install some monitoring or the cup skips or whatever. 86 00:06:11.439 --> 00:06:15.759 So just one part of the role of the wo process. 87 00:06:16.480 --> 00:06:24.199 Nice, So new questions straight after that, h like I 88 00:06:25.120 --> 00:06:29.079 assume this will all to be maybe a source of 89 00:06:29.120 --> 00:06:31.240 confusion for someone who doesn't know a whole lot about 90 00:06:31.439 --> 00:06:36.279 Docker or just like the modern deployment complexity and stuff. 91 00:06:36.319 --> 00:06:41.120 But can you explain what the difference between Kubernetes and 92 00:06:41.160 --> 00:06:45.079 camale is for people who don't understand either of them. 93 00:06:45.480 --> 00:06:50.639 Yeah, So basically you can split this kind of the 94 00:06:50.720 --> 00:06:59.120 point systems to two categories. One is doing push to 95 00:06:59.199 --> 00:07:03.480 the server, pushing your configuration to the server, your changes 96 00:07:03.519 --> 00:07:06.000 to the server. In terms of come out, that means 97 00:07:06.160 --> 00:07:10.120 from your local computer or the CI server, you will 98 00:07:10.199 --> 00:07:13.199 run came out, deploy, and come out will issue the 99 00:07:13.319 --> 00:07:17.279 concrete commands that have to run on all those servers 100 00:07:17.319 --> 00:07:21.279 that you defined and kuvernatives is the other category, which 101 00:07:21.279 --> 00:07:25.959 we call like a pull systems, where usually you have 102 00:07:26.800 --> 00:07:32.480 one host that runs the main master agent in sort 103 00:07:32.519 --> 00:07:38.199 of way, and the other servers run some lightweight minion 104 00:07:39.079 --> 00:07:45.600 agents and so the central system is that one master 105 00:07:45.720 --> 00:07:49.879 host and then all the systems around it can pull 106 00:07:49.959 --> 00:07:55.839 the information from it. So they constantly fax the new 107 00:07:55.839 --> 00:07:58.720 information and if they see okay, there is a new version, 108 00:07:59.160 --> 00:08:02.079 then they go and pull the information themselves. 109 00:08:02.439 --> 00:08:07.680 Cool. That that makes sense, So like why would say 110 00:08:08.319 --> 00:08:11.519 me as an indie developer who is building very small 111 00:08:11.560 --> 00:08:14.720 apps on very small scale, and I'm thinking do I 112 00:08:14.800 --> 00:08:17.240 even need docer, Like do I even need come out? 113 00:08:17.439 --> 00:08:19.399 Like what what's your opinion on that? 114 00:08:20.439 --> 00:08:23.240 Yeah, in terms of what I was thinking, what I 115 00:08:23.319 --> 00:08:25.800 was speaking about the split between like Kubernetes and the 116 00:08:26.519 --> 00:08:30.319 agent systems. Uh, that's what I think that you don't 117 00:08:30.319 --> 00:08:34.960 really need for small scale, right because you don't need 118 00:08:35.080 --> 00:08:38.200 x RA resources to run the agents. You don't need 119 00:08:38.559 --> 00:08:40.879 the x and master server that maybe also need some 120 00:08:41.000 --> 00:08:45.200 kind of back up to be high available and so on. 121 00:08:46.720 --> 00:08:50.360 But as you say, there's still the question about Docker itself, 122 00:08:50.440 --> 00:08:56.399 like isn't even Docker overhead, right? I saw some people 123 00:08:56.440 --> 00:09:00.799 commenting on Ruby subreddit and they were like kind of 124 00:09:02.120 --> 00:09:07.120 criticizing come out for using Docker when the church wants 125 00:09:07.360 --> 00:09:10.480 re else to be no built, as the no built 126 00:09:10.600 --> 00:09:14.759 right on the front end, but then introducing build process 127 00:09:14.879 --> 00:09:20.679 on the on the on the server side. But dooker 128 00:09:20.720 --> 00:09:26.720 still has several advantages. First of all, we really package 129 00:09:27.519 --> 00:09:31.480 prepackage the application in the container, so we can be 130 00:09:31.600 --> 00:09:37.120 sure of what's really inside and that at this revision 131 00:09:37.440 --> 00:09:41.519 the application was running, which is important when you will 132 00:09:41.559 --> 00:09:44.440 be doing a roll back. You know, when something wrong 133 00:09:44.480 --> 00:09:47.120 happened and you want to roll back, then you know 134 00:09:47.240 --> 00:09:52.879 that the previous version was actually running fine. The problem 135 00:09:52.879 --> 00:09:56.120 with Capistrano way of doing that is that suddenly you 136 00:09:56.159 --> 00:09:59.440 are trying to switch back to a Ruby version that 137 00:09:59.600 --> 00:10:04.519 hopefully is there, but maybe if there is some system changes, 138 00:10:04.799 --> 00:10:07.639 you know, system update, system utilities, and a lot of 139 00:10:08.120 --> 00:10:13.039 application also shell out to call some system system tools. Right, 140 00:10:14.200 --> 00:10:16.720 so suddenly you don't even know what will happen because 141 00:10:16.960 --> 00:10:18.559 it can go all wrong. 142 00:10:20.120 --> 00:10:22.919 Yeah, for those that aren't aware, Cavistrano is all like 143 00:10:23.200 --> 00:10:27.320 local file system and just has like a you know, 144 00:10:27.600 --> 00:10:31.519 simblink cut off to switch whatever production. 145 00:10:31.240 --> 00:10:36.679 Version you're using right behind the scenes teldr of it. 146 00:10:37.240 --> 00:10:38.360 There's other stuff, right. 147 00:10:39.320 --> 00:10:44.000 Yeah, exactly as you say. And of course yes it's 148 00:10:44.000 --> 00:10:47.039 simply a trade off. You can't really say it's so 149 00:10:47.159 --> 00:10:51.000 much better or so much worse. I think for more 150 00:10:51.200 --> 00:10:55.360 deploys it's preferable to do it with something like Docker 151 00:10:55.480 --> 00:11:02.759 or different continued technology. But I do sympathize somehow to 152 00:11:02.840 --> 00:11:07.240 the local criticism because you now need a doctor registry 153 00:11:07.559 --> 00:11:12.799 to save your images, which, by the way, David suggested 154 00:11:13.000 --> 00:11:17.080 that they will get rid off in some future versions 155 00:11:17.279 --> 00:11:20.879 of come out, so hopefully that will go away. But yeah, 156 00:11:20.919 --> 00:11:25.440 it's a new thing to learn basically, so I understand, 157 00:11:26.000 --> 00:11:29.639 especially because when I was writing my first book, Diploma 158 00:11:29.759 --> 00:11:33.080 from Scratch, I also basically it's something like a pistannel, 159 00:11:33.480 --> 00:11:36.960 except I didn't even use Ruby. I simply do it 160 00:11:37.000 --> 00:11:40.720 with Besh only, you know, so you don't have to 161 00:11:40.799 --> 00:11:46.399 learn any other tool, and you can still install and run. 162 00:11:46.559 --> 00:11:50.639 And the biggest advantage there is that the switch the 163 00:11:50.720 --> 00:11:54.399 update can be really fast if you are not even 164 00:11:54.399 --> 00:11:59.240 installing a new version of Ruby GM for example. It's 165 00:11:59.279 --> 00:12:02.679 really it's like and you know, it's it's really super fast. 166 00:12:03.159 --> 00:12:06.600 But I think the other advantages of doctor deployees really, 167 00:12:07.840 --> 00:12:12.960 oh really are better for most people, for majority of people. 168 00:12:13.399 --> 00:12:19.279 And when I saw Kamal as a tool, I was 169 00:12:19.960 --> 00:12:24.759 I told myself, okay, this is it. Because since I 170 00:12:24.840 --> 00:12:29.000 had this Besh script kind of deploy you know, very 171 00:12:29.320 --> 00:12:33.240 very straightforward, I was thinking myself of doing some kind 172 00:12:33.279 --> 00:12:37.559 of small tool, something like comal. At the time, I 173 00:12:37.639 --> 00:12:42.120 was thinking maybe using some components like Caddy for web server, 174 00:12:42.480 --> 00:12:46.919 you know, or maybe Potman instead of Docker. Because my 175 00:12:47.159 --> 00:12:53.159 background is in like federalit knuks and and stuff. But 176 00:12:53.279 --> 00:12:56.279 I know that my little tool again be just for me, 177 00:12:56.600 --> 00:12:59.720 you know, so I thought like Tamil is the closest 178 00:12:59.759 --> 00:13:04.480 to what I want, and so that's how I basically 179 00:13:04.519 --> 00:13:08.039 started to be interested and started to look more into it. 180 00:13:08.840 --> 00:13:12.240 You know, I really liked Kamal's direction to make it 181 00:13:12.360 --> 00:13:16.440 just easier to jump on Docker without having to like 182 00:13:16.720 --> 00:13:19.600 necessarily worry about like how you configure Docker and like 183 00:13:19.639 --> 00:13:22.360 connect all of the services and things like that out 184 00:13:22.399 --> 00:13:25.799 of the box anyway, right, and then because it sets 185 00:13:25.840 --> 00:13:27.840 you up kind of like Okay, if you needed to scale, 186 00:13:27.960 --> 00:13:32.039 you could then move to some other you know, provider 187 00:13:32.200 --> 00:13:35.200 like AWS or something that could scale the notes for 188 00:13:35.240 --> 00:13:38.200 you pretty easily, and you can reuse all the configuration stuff. 189 00:13:39.159 --> 00:13:42.879 So that's a little exciting in that way. Uh, and 190 00:13:42.919 --> 00:13:45.200 it makes it it makes me think though, like like 191 00:13:45.759 --> 00:13:47.919 so how does this compare to like something like you know, 192 00:13:48.000 --> 00:13:51.799 tools like chef or uh, you know, some other configuration 193 00:13:51.919 --> 00:13:57.000 management aspects of like you know, the system deployment process, 194 00:13:57.039 --> 00:13:59.480 Like where where are some advantages that Kamal could lead 195 00:13:59.559 --> 00:14:04.240 us where you you know, maybe I know Chef is 196 00:14:04.279 --> 00:14:07.519 like a it takes some extreme getting used there's onboarding 197 00:14:08.159 --> 00:14:12.559 ramp like pretty steep learning curve, but like where do 198 00:14:12.600 --> 00:14:15.720 you see CAMAL like kind of maybe simplifying that or 199 00:14:15.759 --> 00:14:17.679 how does it compare or does it not. 200 00:14:19.480 --> 00:14:23.679 Yeah, I think there's this confusion among the deploy systems 201 00:14:23.720 --> 00:14:26.960 because then you have exactly, as you say, CHEF or Unstable, 202 00:14:27.639 --> 00:14:32.519 and they may be started as more like configuration tools, 203 00:14:33.720 --> 00:14:37.919 but they also offer you a way to do a deploy, 204 00:14:38.399 --> 00:14:42.440 you know, so they're not completely obsolete. We've come out 205 00:14:42.480 --> 00:14:46.840 because you can still use them provision the servers, and 206 00:14:46.919 --> 00:14:51.840 then you come out for the deploy part. In my case, 207 00:14:52.360 --> 00:14:55.360 I find that I don't need that much of the 208 00:14:55.440 --> 00:14:59.919 configuration I mean come out itself, even builds itself as 209 00:15:00.399 --> 00:15:02.799 almost you don't need anything, but that's not really true, 210 00:15:02.879 --> 00:15:08.200 and then people are disappointed. But for me, I for example, 211 00:15:08.360 --> 00:15:12.799 included a very small Ruby script which is just wrapped 212 00:15:13.320 --> 00:15:16.960 a little bit rapper around some show commands to provision 213 00:15:17.480 --> 00:15:22.039 some very basic things for the server like firewalls, a 214 00:15:22.320 --> 00:15:28.879 different associate user for security reasons, and so on. And 215 00:15:28.960 --> 00:15:31.320 in this way you might find out that you need 216 00:15:31.360 --> 00:15:34.840 so little that you don't really need a proper tool 217 00:15:34.879 --> 00:15:39.480 like CHEF. But at the same time, I wouldn't say 218 00:15:39.519 --> 00:15:42.679 that Kama makes it obsolete because they compliment each other. 219 00:15:43.840 --> 00:15:47.320 I do wonder if David, for example, still have in 220 00:15:47.399 --> 00:15:52.639 his mind to release something complimenting Comal because Kama is 221 00:15:52.679 --> 00:15:55.639 so simple and it started as a multi server tool, 222 00:15:55.679 --> 00:15:58.879 but at the same time it cannot deploy a lot 223 00:15:58.919 --> 00:16:02.840 bal answer like in front of the servers, right, you 224 00:16:02.879 --> 00:16:06.600 have a proxy that does to get plus the poise 225 00:16:06.679 --> 00:16:11.120 on each of hosts, like each server, but you still 226 00:16:11.120 --> 00:16:15.039 need like third party load bal answer. So Kamala is 227 00:16:15.120 --> 00:16:19.159 like really like very specific tool, and I wonder if 228 00:16:19.679 --> 00:16:23.519 simply comeal will maybe get a little bit bigger and 229 00:16:24.240 --> 00:16:27.039 better in this way to handle these things, or there 230 00:16:27.039 --> 00:16:28.000 will be something else. 231 00:16:29.120 --> 00:16:34.720 Maybe would you use Kamal for your like on independent 232 00:16:34.799 --> 00:16:37.240 single sub applications as well, or would you use your 233 00:16:37.639 --> 00:16:40.440 vast script whatever approach you thought in your first book. 234 00:16:42.600 --> 00:16:47.480 So I switched everything to come out for all my projects, 235 00:16:48.440 --> 00:16:52.919 and also I was working with some clients to switch 236 00:16:52.960 --> 00:16:57.240 them to come out for me. The Although I actually 237 00:16:57.240 --> 00:17:01.440 really used the best scripts from the book, they were 238 00:17:01.480 --> 00:17:07.200 developed specifically to be educational. I didn't say don't use tools, 239 00:17:07.279 --> 00:17:11.400 don't use kuberneties, but I rewrited it to pure beash 240 00:17:11.480 --> 00:17:16.079 to simply show people that everything else is an a abstruction. Right. 241 00:17:16.880 --> 00:17:20.759 For example, when you have answerable, it's written in Python, 242 00:17:20.880 --> 00:17:23.640 it's a lot of Python code that in the end 243 00:17:23.799 --> 00:17:29.400 prepares a best code best script that it copies onto 244 00:17:29.839 --> 00:17:33.039 the remote server and then it executes it there. Right. 245 00:17:33.720 --> 00:17:37.160 So I basically skip the part where I have to 246 00:17:37.200 --> 00:17:41.319 teach someone about different tools, because, to be honest, the 247 00:17:41.359 --> 00:17:44.279 tools come and go. So the idea for the first 248 00:17:44.319 --> 00:17:48.400 book was really not being about particular tool, but more 249 00:17:48.519 --> 00:17:53.440 like how this actually works. But since we have come out, 250 00:17:53.480 --> 00:17:56.519 I think it's it's for me. It's like a perfect tool. 251 00:17:57.640 --> 00:18:02.119 There's some alternative you can look into Doku or maybe 252 00:18:02.119 --> 00:18:08.799 even simple docer composed, but personally I think come Out 253 00:18:08.920 --> 00:18:14.000 has advantage to them because they are it's designed for 254 00:18:14.240 --> 00:18:19.960 multi server use from the ground up. Basically the single 255 00:18:20.000 --> 00:18:23.480 server use case was like edit later. Right, we've come 256 00:18:23.519 --> 00:18:29.519 out too, and compared to docul there's also a different philosophy. 257 00:18:29.559 --> 00:18:32.960 It's not like PAS. It's more like really just the 258 00:18:33.000 --> 00:18:37.279 deploy tool. But if I'm deploying my own application that 259 00:18:37.359 --> 00:18:40.279 I also develop, I think come out it's best to 260 00:18:40.319 --> 00:18:44.039 that to that use case. You know, maybe if you 261 00:18:44.119 --> 00:18:51.720 want to deploy some public application, maybe it's easier to 262 00:18:51.920 --> 00:18:56.119 install something like qulify or some other tools that can 263 00:18:56.319 --> 00:18:58.519 one click install them. But I think if you are 264 00:18:58.519 --> 00:19:02.559 the developer of the application, that really feel fits the 265 00:19:02.599 --> 00:19:07.640 films of the best, and for me personally, I really switched. 266 00:19:10.720 --> 00:19:13.119 Yeah to add on and I'm saying there's a there's 267 00:19:13.119 --> 00:19:15.759 a pr open right now to add a cloud native 268 00:19:15.799 --> 00:19:19.279 build text to come on, which would be interesting where 269 00:19:19.279 --> 00:19:22.480 you can basically build the app based off of other 270 00:19:22.519 --> 00:19:23.880 ones pretty easily. 271 00:19:24.960 --> 00:19:28.519 Yeah, So basically that's that's the single I would say 272 00:19:28.599 --> 00:19:31.839 advantage of docu today that it can be a little 273 00:19:31.839 --> 00:19:35.480 bit more magical. Somehow will build it for you and 274 00:19:35.599 --> 00:19:41.319 you don't have to write docer file. But lucky for us, 275 00:19:41.480 --> 00:19:44.480 Rails actually counts of docer file, so there's no extra work. 276 00:19:44.839 --> 00:19:49.200 It's not true for every every framework, but of course, 277 00:19:49.440 --> 00:19:52.799 if you are adopting doctor, I still recommend looking into 278 00:19:54.079 --> 00:19:56.279 how to build doc per file, how to optimize it. 279 00:19:56.519 --> 00:20:03.440 For example, before I was trying to squeeze the Stoker 280 00:20:03.519 --> 00:20:06.359 file for my reels applications, you know, I was removing 281 00:20:06.400 --> 00:20:09.920 all the all the files I don't need them to 282 00:20:09.920 --> 00:20:12.839 to have small footprint since you have to do the 283 00:20:12.880 --> 00:20:15.440 image and pull and push. 284 00:20:16.720 --> 00:20:22.680 So so yeah, so what is like kind of like 285 00:20:22.720 --> 00:20:24.599 the full process, Like let's say we do like a 286 00:20:24.640 --> 00:20:27.559 real's new app and we wanted to like deploy it 287 00:20:27.599 --> 00:20:30.920 with comal to like some Lino or something right or 288 00:20:31.200 --> 00:20:35.440 digital droplet, Like what what is the steps of the 289 00:20:35.480 --> 00:20:36.920 process there, like. 290 00:20:38.880 --> 00:20:40.119 To just like reels new. 291 00:20:40.319 --> 00:20:46.759 Yeah, you know, so let's say you do you did 292 00:20:47.119 --> 00:20:51.279 reels new. You have your doctor file. So that's one 293 00:20:53.480 --> 00:20:58.200 that's one perrequisite you have to have for the dooker 294 00:20:58.240 --> 00:21:01.960 file because maybe you're not rails. So let's just mention 295 00:21:02.119 --> 00:21:06.160 that you do need your server to run on board eighty. 296 00:21:07.000 --> 00:21:09.200 You can change it, but it's like default. If you 297 00:21:09.240 --> 00:21:15.920 want to simply work, that's the that's the main thing 298 00:21:17.160 --> 00:21:21.079 for the doctor file. Then you will need a doctor registry, 299 00:21:21.319 --> 00:21:25.079 so make an account a doctor hub, or maybe your 300 00:21:25.160 --> 00:21:30.079 provider has its own register that you can use. And 301 00:21:30.640 --> 00:21:35.680 you need to create like they call it cose. It's 302 00:21:35.680 --> 00:21:41.960 still registered passport, but you should create a token and 303 00:21:42.200 --> 00:21:46.200 note it down. And then you will need to create 304 00:21:47.119 --> 00:21:50.559 some virtual machine. It can be hadsner, it can be 305 00:21:50.640 --> 00:21:56.559 Digital Ocean, any cloud provider like that would work, and 306 00:21:56.599 --> 00:21:59.759 for that you will need to create as a SAGE 307 00:22:00.079 --> 00:22:05.039 key pairs, so you will create three pair. That means 308 00:22:05.079 --> 00:22:10.119 you have two keys, one private and one one public. 309 00:22:11.160 --> 00:22:15.480 Right to the private obviously you have to protect like 310 00:22:15.519 --> 00:22:22.359 the regiously password. And during the creation of the virtual machine, 311 00:22:23.359 --> 00:22:26.400 when you go like create, you choose some resources you 312 00:22:26.440 --> 00:22:29.039 know how big the VM should be and so on, 313 00:22:29.720 --> 00:22:32.400 and then I will ask you to copy your key there. 314 00:22:32.960 --> 00:22:38.200 So that's how they will provision uh, the VM for 315 00:22:38.359 --> 00:22:46.920 you and you should you should disable the password password 316 00:22:46.960 --> 00:22:51.279 logging value are there just for security, and so that's 317 00:22:51.319 --> 00:22:56.160 the that's that's what you need to That's what you 318 00:22:56.200 --> 00:22:59.039 need to have, you know, at the at the minimum, 319 00:22:59.160 --> 00:23:02.119 at at dominimum like the basic ones. Now maybe you 320 00:23:02.160 --> 00:23:05.599 also want to deploy to a domain name, so then 321 00:23:05.680 --> 00:23:09.119 obviously you have to purchase a domain name and you 322 00:23:09.160 --> 00:23:13.680 will need a DSM record at the very least type 323 00:23:13.759 --> 00:23:18.039 A to point your domain to the IP address, to 324 00:23:18.079 --> 00:23:21.160 the public IP address you will get for the machine 325 00:23:21.200 --> 00:23:26.200 you just provisioned. And if you have that, you can 326 00:23:26.279 --> 00:23:31.279 basically start with come out. We've come out in it. 327 00:23:31.680 --> 00:23:38.359 There's some basic basic configuration file. There are comments in line, 328 00:23:38.759 --> 00:23:42.839 so even when you never saw it, you can usually 329 00:23:43.000 --> 00:23:46.599 I guess a little bit what you will have to 330 00:23:46.640 --> 00:23:53.039 put there, So you will name your application, come out 331 00:23:53.079 --> 00:23:58.160 close it service. Yeah, I would also say be careful 332 00:23:58.200 --> 00:24:02.160 of the name because when you are doing the dooker 333 00:24:03.319 --> 00:24:07.079 a local private networking, it's also like kind of a 334 00:24:07.200 --> 00:24:11.240 name that you are using, so you cannot like put 335 00:24:11.359 --> 00:24:14.359 any characters you want there, you know, just stick to 336 00:24:14.440 --> 00:24:20.240 normal letters and lashes, and then you are fine, so 337 00:24:20.240 --> 00:24:23.160 so you are not surprised later that it doesn't it 338 00:24:23.160 --> 00:24:29.000 doesn't work. Then you specify the image which is your container. 339 00:24:29.079 --> 00:24:33.839 Registries use their name like slash the application name basically, 340 00:24:35.200 --> 00:24:39.839 and then you can put the IP address among servers. 341 00:24:43.680 --> 00:24:48.400 When you do that, you're configuring your application server by 342 00:24:48.960 --> 00:24:54.880 default the role called web and you can return just 343 00:24:54.920 --> 00:24:59.519 after this one how how came I splits the application 344 00:24:59.640 --> 00:25:03.240 server roles and accessories. But for now, if you just 345 00:25:03.279 --> 00:25:07.279 put there the IP address, that's enough, and then you 346 00:25:07.400 --> 00:25:11.920 will configure proxy. You will say okay, I want as 347 00:25:11.920 --> 00:25:14.519 a cell and you will put their holds which is 348 00:25:14.839 --> 00:25:17.240 your domain name or it can be also some domain. 349 00:25:18.799 --> 00:25:21.680 It can be even more hosts if you want so, 350 00:25:21.880 --> 00:25:25.960 very very flexible. This is very nice. Then you finish 351 00:25:26.039 --> 00:25:30.480 up with the registry and then there's a build a 352 00:25:30.480 --> 00:25:34.680 configuration but by default I think there's some reasonable value 353 00:25:35.519 --> 00:25:39.480 and and once you have all this then you only 354 00:25:39.519 --> 00:25:43.839 need to provide the environment, which is the secret spee. 355 00:25:44.720 --> 00:25:47.640 We talk about like IMO registry Passford, but it can 356 00:25:47.680 --> 00:25:56.599 be many more secrets the application have obviously, so you 357 00:25:56.599 --> 00:26:03.039 you list them in two basically want some environment variables 358 00:26:03.279 --> 00:26:07.400 you can list directly, but the secret once you actually 359 00:26:07.599 --> 00:26:12.319 just just put under like nd secret in the AMMO 360 00:26:12.519 --> 00:26:15.000 in the m file and then you only list them, 361 00:26:15.319 --> 00:26:18.759 but they leave somewhere else when you did the come 362 00:26:18.759 --> 00:26:22.559 out in it from before, come also created dot come 363 00:26:22.559 --> 00:26:26.599 out slash secrets file. That's where the secrets are. And 364 00:26:26.720 --> 00:26:29.880 of course then you can also call passform managers and 365 00:26:29.920 --> 00:26:32.720 so on. But at the very basic one you would 366 00:26:32.720 --> 00:26:35.920 just put the secrets there. You will not check it out, 367 00:26:36.440 --> 00:26:40.599 check it in the source control and then your configuration 368 00:26:41.039 --> 00:26:45.680 is done. You run come out set up and come 369 00:26:45.720 --> 00:26:49.319 all does everything for you. It will connect to the server, 370 00:26:49.680 --> 00:26:55.319 it will install do occur, it will install the come 371 00:26:55.319 --> 00:26:59.559 out proxy, and then it will put your application. So 372 00:26:59.599 --> 00:27:04.119 that's the most minimalistic way off the playing with Comal. 373 00:27:05.759 --> 00:27:06.319 Gotcha. 374 00:27:07.240 --> 00:27:10.400 So I'm mugging through the commands like as you're reading 375 00:27:10.400 --> 00:27:14.079 through that. Ah, and just so like we can most 376 00:27:14.079 --> 00:27:18.079 people know Horoku right like Heroku new and then deploy 377 00:27:18.400 --> 00:27:21.119 uh you know yeah, get pushed for Roku. 378 00:27:21.759 --> 00:27:22.480 Uh. 379 00:27:22.599 --> 00:27:25.640 And it seems like there's really like the three uh 380 00:27:25.759 --> 00:27:28.720 you know kmal commands that really run through that well 381 00:27:28.880 --> 00:27:31.559 everything you just said right, which is pretty wild, or. 382 00:27:31.480 --> 00:27:32.720 We have like come all in. 383 00:27:32.839 --> 00:27:35.480 It creates all the configuration files. 384 00:27:36.119 --> 00:27:42.160 Uh, comeal can fig like uh you know, starts to create. 385 00:27:41.920 --> 00:27:45.319 Your initial configuration file to add all the stuff to uh, 386 00:27:45.720 --> 00:27:48.920 and then you have KMAL deployed that just like push 387 00:27:49.000 --> 00:27:53.000 that up and proxy to the new version right of 388 00:27:53.160 --> 00:27:53.480 the app. 389 00:27:53.759 --> 00:27:56.279 Yeah. Yeah, basically as you say, I mean, the comal 390 00:27:56.319 --> 00:27:58.799 confix is already created. If come out in it and 391 00:27:58.839 --> 00:28:05.640 come out CONFIXP rechecks the configuration, it's good. That's actually good. 392 00:28:05.720 --> 00:28:07.960 Good one to run before the deployee. 393 00:28:08.319 --> 00:28:09.720 Yeah, that's awesome. 394 00:28:09.960 --> 00:28:10.480 I mean. 395 00:28:12.039 --> 00:28:14.559 That's uh, that's where we want to head right, Like 396 00:28:16.240 --> 00:28:20.079 it's like it's pretty close. I mean I guess like 397 00:28:20.240 --> 00:28:26.279 uh yeah, I mean so many like so many hosting 398 00:28:26.319 --> 00:28:30.200 providers now have that like one clip process to just 399 00:28:30.240 --> 00:28:34.160 get your VM up that it almost doesn't even make 400 00:28:34.200 --> 00:28:38.160 sense to abstract away that process, right to make it 401 00:28:38.200 --> 00:28:41.839