词汇：have
vt. 有；让；从事；允许；拿
相关场景
- The hotel has a very good location.>> 3 checking in
- We have to report it to the lost-and-found office.
我们必须向失物招领处报告。>> 2. Metting the Group- Somebody in the group has lost one piece of luggage.>> 2. Metting the Group
- How many pieces of check-in luggage do you have altogether?
您总共有多少件托运行李？>> 2. Metting the Group- Can I have the name list of the group?>> 1. Making preparations 1-11
- One has just joined our group.>> 1. Making preparations 1-11
- 6:
- Two tourists have cancelled their trip?>> 1. Making preparations 1-11
- T:
- My name is Lily. I'm from China International Travel Agency. Our company has assigned me to be your host here in Wuhan.
我叫莉莉。我来自中国国际旅行社。我们公司派我来武汉做你的东道主。>> 1. Meeting the Guests at the Airport- You have to know your group information well enough.>> 1. Making preparations 1-11
- We're not gonna change that for this little example, but now let's check in that PWA files, and then let's deploy to production one more time. and as you can see, look in the top right corner, when I reload it, we now have that little install icon in Chrome. and if I click that little install icon, I'm gonna get this prompt, and boom! I have a PWA running in production for my Rails application.>> Rails 8.0.1 You are in good company
- And it's gonna refer to an icon, by default,we just have a nice red dot.but you should obviously replace that with your application. And if I hop in and have a look at the service worker, it is sort of already set up for doing we push,just as an example here, having some listeners, you can tweak that as you see fit.
它将指向一个图标，默认情况下，我们只有一个漂亮的红点。但你显然应该用你的应用程序替换它。如果我跳进去看看服务工作者，它已经为我们推送做了准备，就像这里的一个例子，有一些监听器，你可以根据需要进行调整。>> Rails 8.0.1 You are in good company- So, be careful when you create things, that are gonna be created on the server side in your real database.The database, by the way? we haven't talked much about that, and that is because we're using SQLite. So, there is nothing to configure,there's nothing to set up, SQLite is now a suitable database for production with Rails. we have tuned it with all the right pragmas,to run SQLite well in production, you of course still need to set up a way to back that up, but everything else is preconfigured for you.>> Rails 8.0.1 You are in good company
- All right , let's save that and hop back,and see a reload here, now, we have a sign out button, and we can sign out, and that's all it should be. let's deploy this to production, we're gonna just check this thing into Git, deploy it straight to production, go back to our alpha.software...Oops! That didn't work. Why did that not work?>> Rails 8.0.1 You are in good company
- Now, if we hop back onto local host, and we try to log in with first the wrong password. we're actually gonna see something here , when I added the authentication, it added another gem, it added bcrypt, that's what we're using to keep password secure, so we have to hop back in here and restart our development server!>> Rails 8.0.1 You are in good company
- If we hop to the session, you can see it just is very basic Rails active record. Now we're gonna set up a default user that the systems should have as we're working with it to allow us to log in since we don't have that signup flow.>> Rails 8.0.1 You are in good company
- Everything else by default will be behind the authentication lock! There's also a rate limit to make sure that people don't bombard you with attempts to log into users do not have access to.>> Rails 8.0.1 You are in good company
- And then, we are going to hop in here and have a look at what was actually generated. We have the sessions controller, that's probably the most important. You can see here, it allows unauthenticated access to just new and create.>> Rails 8.0.1 You are in good company
- Common system is of course these as well, let's add one of those comments, and now we have the entire application running in production, wasn't that easy?>> Rails 8.0.1 You are in good company
- There was a 404 here! That's because if we go back to out route file, I have not defined route! And in production, you're not gonna get that screen we saw with the Rails version and the Ruby version, that is only for development.>> Rails 8.0.1 You are in good company
- the tree has already claimed a number of victims.>> 58-A Blessing in Disguise?
- 21:28:
- So this server exists on this address, servers web: - demo.exitsoftware.io ; proxy: host: alpha.exitsoftware.io; And I will then fill out the host as a C name to that machine. But we're using Alpha here, if I had deployed another application called Bravo to the same server, Kamal would set it up, so it's like I host two applications or any number of applications on that same server! Now, we will also need to have a look at the secrets here, that is in dockyml/secrets, because the register that I'm using, that is Docker Hub, needs of course a password, it is using my username but also needs a password.>> Rails 8.0.1 You are in good company
- Now I'm gonna deploy this on my own little hoppy server. And that hoppy server is currently wiped. it is completely clean, and Ubuntu 24.04 setup that has nothing on it already, this is part of the magic of Kamal, you can spin up a new VM anywhere in the cloud or use your own hardware and point Kamal straight to it, and you'll be going in no time!>> Rails 8.0.1 You are in good company
- Docker Hub:
- And there's a default configuration file in config/deploy.yml that we can use, it's prefilled a little bit, it has the service name of the name of reaction, but we need to rename, for example, your user,the name of the image to go to my name of where I store this on Docker Hub. You can see we change that down in the registry as well and the name of the container image.>> Rails 8.0.1 You are in good company
- Now, let's set things up to be dynamic, such that when we add a new comment to one of these, it's going to update the other as well. This is how we use web sockets in Rails using action cable, one of the frameworks that we have to create updates that are distributed automatically without folks having to reload their browser.>> Rails 8.0.1 You are in good company
- When it is nested, we get the fact that it's gonna be slash post slash on slash comments, and we have the association is set up nicely. Now, let's reload! Now it works, we have our comments field underneath. we can add the first comment. And as you can see here, this is my first comment a second ago that was the local time doing its time ago conversion.
当它被嵌套时，我们得到的事实是，它将是斜线后斜线对斜线注释，并且我们已经很好地建立了关联。现在，让我们重新加载！现在它工作了，我们在下面有我们的评论字段。我们可以添加第一条评论。正如你在这里看到的，这是我一秒钟前的第一条评论，当时当地时间正在进行时间转换。>> Rails 8.0.1 You are in good company