My mum spends a couple of nights a week volunteering on the phones at the local Youth Drugs Advice Centre.  It's something she enjoys doing. Plus, she likes helping out the kids in the village. I mean, it's only a small place, so she thinks we all need to stick together. She was talking about a request from the police recently to access some of the information about the people who use the advice lines and who email the centre. They don't want to arrest anyone using the centre. They're more interested in trying to find out information about the drug dealers and supply chains in the area. Everyone who works at the centre has a meeting next week to discuss whether to allow the police access to the information and she doesn't know what to do. Should the police be allowed to use surveillance on the telephone calls and online traffic to a young person's drugs advice centre?


We've heard from several partners today. Now let's hear from another customer. We'll see how Bloom AG unites GitLab pipelines in Terraform for a single source of configurations. You know, configuration is important for consistency, security, and speed, but it can be a pain to manage across multiple tools. So Phillip West-Vallen with Bloom had the idea to combine configuration efforts of GitLab and Terraform into one place. They automated everything and used a top-down approach to standardized projects. This innovative idea may not be for you, but it's interesting to see the out-of-the-box thinking. Maybe it will spark others to innovate, like Phillip did, or to engage with GitLab on new ideas that we can incorporate. Remember, you can chat questions at any time throughout the presentation. Welcome everyone. Today I share you our way how we managed our GitLab projects and Cloud Infrastructure with Terraform. My name is Phillip West-Vallen. I am a GitLab hero and hosting the GitLab Meetup here in Hamburg. Part of that, I am a software engineer and work for an online shop, which sells flowers. If you have any questions, feel free to ask in the chat or hit me up on Twitter. So let's start with our background story. We recently started to rebuild our online shop and the technical landscape behind it because we want more speed and start into the public cloud era. So we need for that infrastructure as code because we don't want to figure out everything manually. And yeah, manual steps are really dangerous there. And yes, so we also want to automate everything possible. So what is the idea we have? We want to configure our infrastructure in one place. This means an essential central space anywhere in GitLab or in our GitLab project and a repository. And we thought about that we don't only configure our Cloud Infrastructure. There we also wanted to create or manage our GitLab organization, for example, who is in which team or what are the dependent information for this specific project as a variable, for example, service accounts or the manager of service accounts. Yes, so a part of that, we want to have that our teams have their own space in the infrastructure so they don't have to configure in the one repository. And yeah, so this means that our teams are still have the chance to be flexible so they can fulfill their needs. Yes, and one important thing every time is that we automate everything. So what does it mean for our structure, how we use GitLab and the Cloud? So we had an organization structure like in every other company. We had a top level, which is our department or the general configuration, for example. And then we have our teams. We have multiple teams. And then each team can have multiple services. And we thought about how we can use or how we can utilize GitLab for that. GitLab got groups, subgroups, and repositories. So in a group can be a subgroup or a repository and a subgroup function same as a group. So we thought, OK, we have a group for the organization, whereas one project, for example, for the general structure. And then under the group, we have subgroups for each team. And each team can have multiple repositories, which means this are the specific configuration for the services. And then we have the Google Cloud Platform world, on the other hand. And there are folders. Folders are the equivalent of the equal thing like a group in GitLab. And a folder can be a folder and a project or a project. And a project is the same like a repository for us. Or yeah, there can be a project where is what you need there. We are connecting the dots there, which service you need and connecting everything that you can run your software there. So we built our organization. Our organization is a folder. But we have for each team a single project, private environments, so a dev environment and a product environment. But this is not interesting here. And yes, and this project is for one team. So every service we want to publish there, they are using this project. So it's there. There are no next level for a folder or something. Yes, each team has a project. There's Kubernetes cluster, for example. It's perfect. So what does it mean for affecting things? We had thought about, or I mentioned before, on the organization level. We have a little project where we have general configuration for infrastructure. And then in the team, we also have a project for the team-specific configuration. And each service still has another configuration space for the specific service. So it's like the hierarchy. So we have an organization level. We have a team level and a service level. And each level benefits from the service above. So the organization hierarchy has data which are inherited to the teams, for the team, team, team, team groups in GitLab, for example. So we used or we shared data from top to down. Yes, so we did that automatically, which means, on the other hand, that we don't have a configuration from a lower level that can be lived upwards. Yeah, because it's technically complicated and you could have side effects that you can don't deploy a team or create a new team when you rely in. Yeah, if you have changes and rely on the dependent service, which is not created, or they can do a lot of bad things when you don't use top-down approach or a straightforward approach, yes. So how we share data across the landscape? We have two different approaches. One is the GitLab CI variables approach. This is done when we have to share data between different levels. So when we are on the organization level and want to share something to the teams, like a service account in the Google, we do it over GitLab CI variables. So we can use it everywhere downside there and have a clear cut between one project and the other project. So it does not affect when something change on the other side, only if we rename the key of the variable. And on the other hand, we have tear from outputs. This is when you have multiple tear from scripts and your users the same state. So when you have multiple jobs, for example, and they rely on data from a previous pipeline job, for example. And then we use tear from outputs because it's normally sharing the same state and we just configure a bridge between these two. Yes. And what does it mean when we use the data for the GitLab CI variables? It's really simple. We simply tear from had the ability to use directly environment variables from the host system when it's using the correct naming convention there. So we don't have to do anything. And when we have tear from outputs, we have data pack there where we have to configure, OK, we are importing from another tear from state. So this is the brain or the brain of tear from where any information is stored. Yes, it's configured there. And you simply ask them in the tear from way. They ask in the tear from way for the data and you can use it more easily. And an advantage of the tear from outputs way is that we can use or we have to configure one data lake or data source. And we have a lot of different or everything which is an output from the previous job. And on the other hand, the disadvantage of GitLab CI, we had to configure every single data source or data information as a single GitLab variable. Yes. So how does it look in practice? We have a heart or we have a heart for our configuration. So it's simply a single repository which prepares our cloud project and the GCP and configure our GitLab projects or groups with permissions. So if you see here on the left side, we have a teams JSON file where store a lot of configuration for our different teams. And yes, the configuration heart or the single project configuring all the base stuff which is needed for the organization, the world organization and creating specific service accounts for each team project and creating the project in the GCP. Yes. And they print a lot of GitLab CI variables because they are all shared for each team and then for each environment, for example. Yes. So we have a single point for the world organization and then we come to our team. Our team has also a project named here the project administration. And there we manage our general stuff for the team like creating a Kafka or specific service accounts for each of our services. And yeah, they are doing their team internal stuff. And this project, for example, plays also GitLab variables for the specific service, but not in the service or in the world repository directly. Yes. They are posting the variables in the group because we don't want to place this directly into a project because we had to go in the project and have to change. Or it's a lot of big management to say, OK, we need this project and the variable is there, there, et cetera, et cetera. It's easier when you put it in the group. But how does it feel to use the service? Or how does it look? In the service, he's mostly he's only consuming the variables and building the stuff needed for the software and the cloud. Yes. And this means here, there are a lot of different variables. And this is only a small part of that because the variables are inherited from the group and then from the organization group and then from the team group. Yeah, this is a lot. And it's sometimes hard to figure out if it's a very, well, yeah, it's a very bare or not. Yes. But when we start with the service, we have a template way. And then we're typing only the service name in. And then we don't have to do anything more because the CI jobs automatically pick the correct variables from themself. So another interesting question is where you have to start the Terraform state. Of course, you could easily use the Terraform state in GitLab, which is really great. But we thought, what if, yeah, we thought it would be fun when you start where you need it. For example, if you configure in GitLab variables, we start in GitLab. And when we use Terraform to create our cloud infrastructure, we start in the cloud. But why? When anything happens in the cloud or is destroyed, it's only done in the cloud. And when we configure our GitLab stuff, it doesn't affect the configuration we did for Terraform configuration we did for GitLab. So it's not so combined. Yes. And what other specifics we face daily doing with our pipelines or how the pipelines look, this is a screenshot from our project administration. This is a team internal setup. And we found out that it's smart or it's a good way to do things in a line that then or, yeah. Some configuration in Terraform depends on other configuration or it's possible that this depends on other configuration. So that means the job has to be run or the job could only run afterwards. And this is because, for example, when you're on the Google Cloud, some APIs take some time to activate. But sometimes Terraform is not working correctly and waiting until the API is finished. So you got an error, OK, the API was not ready. And this is not so cool, but we are facing this issue by running each thing in a separate job. And for example, when it's come to the Terraform state, it's better when we can have a different job for Google Cloud jobs, Terraform expressions, and GitLab expressions. And another interesting thing is that we had split our environments into two different jobs. And for us, it makes sense because we don't want to build a logic into Terraform where we have to loop our two configuration or environments. So we just said, OK, we have a variable for the environment we are currently building. And this is set by the GitLab CI job. But in the setup we have, the destroying of the infrastructure could be take some time. It's a little bit tricky because you have to start in the end to destroy everything. This is a little bit complicated. Yes. And we used the template thing for our jobs because we have the logic that we have for each environment a different job. And we are facing it's really simple. So we have a base job where the common things are stored like rules and emerge in the common script. And then we have our jobs for the specific environment, like for the dev environment. And this is extending simply the base template and set the correct variables. For example, the dev environment. Here, for example, is a correct naming pattern for setting, using environment variables for Terraform. Yes. And then we have here an interesting thing. We say we have a state bucket or we have a variable. But in the end we have a variable specific for the dev stage. But the Terraform does not know it, or doesn't know it, that it's a specific variable only for dev. Yeah. So we have less complexity in Terraform. And we have a special step for the Google application credentials. So what do I say in the last 25 minutes? So a little bit of a wrap up. So the key things you have to take with you that is really cool and helpful to automate your infrastructure and go the excess step and use it not only for the infrastructure but additionally also for example, your building tool or something. And yeah, maybe try to map your organization structure into your cloud and GitLab setup. This was really helpful for us. And worked really well at our company and here. And a little tip, it's not so important but you can still save the Terraform state where you use it. So in GitLab, when you use it for GitLab and Google when you're using for the Google configuration. And in the end, don't forget the flexibility for the teams or in general. Yes. And in the end, if you want to connect with me, there are my socials. And if you are interested in further talks, join our GitLab Meetup Group. We are also doing virtual Meetups. So I have to thank you for your attention and it would be really cool if you share some insights how you use it Terraform and how do you think about our story. Yes. Have a good night or a good day or a good morning. Bye-bye.


So, Hogwarts Legacy is under horizon, and new details are dropping on the daily. Today I bring you confirmation on one to customisation, Steam Deck compatibility, house sorting and some major news on the game from Avalanche and Warner Brothers themselves. First up guys, I can confirm Hogwarts Legacy will be compatible with the Steam Deck. A question put forth to Warner Brothers game support over on Twitter asked exactly this question. They replied with, Greetings and thanks for reaching out to us. We can confirm for you that Hogwarts Legacy will be compatible with the Steam Deck. This is absolutely great great news for all you Steam Deck players and fans out there. I got a few pals who love the Steam Deck myself. They are hyped about this. Okay so what about house sorting and how will it work in the game? Well we got confirmation on this too. There will be a ceremony in the game as you would imagine. We've seen this within the trailers too. But if you didn't know, websites I will link below. We have the Wizarding World which if you link to the Warner Brothers game site which is linked to your game attack. Put all three of these together guys on the Wizarding World website. You can actually go through the process of having the sorting hat pick a house for you which is great and fun. This also works with the wand too so you can have a custom wand picked for you. And again guys if these things are linked with your game attack these will transfer into the game when you play and create your wizard or witch.  But if you are unhappy with them and you want to change them in-game yes this is an option. You can change house and you can also pick a different wand via ceremonies that will happen within the Hogwarts Legacy game. So that is absolutely great great news And confirmation this you'll see on screen now firstly the wand some guy asked about the wand and customization to it. They replied with hi Mike thanks for reaching out about the wand customization. Players will be able to change their choice of wand during the wand ceremony later in game if you don't like your choice of the wand from the Harry Potter fan club quiz which is absolutely awesome. Also on screen I see in this about the house sorting. This is taken from the official port keys website. The question put forth is will linking my Harry Potter fan club account carry over profile there such as my custom wand and Hogwarts house sorting. Now we just spoke about the wand where here you can see they confirm about the house. While your sorted Hogwarts house will be your default choice in the game you can choose to modify your selection before the end of the ceremony. So guys in game when that ceremony happens if you're unhappy being in half or puff I want to change to Slytherin or Ravenclaw as you would you can pretty cool because that's exactly what I'm doing. Okay so finally guys and the final bit of news we have comes from a tweet from Warner Brothers games France they tweeted out in French which I can't read luckily there is a translator there it states hashtag Hogwarts legacy the Hogwarts legacy has some good surprises in store for you more information coming very soon indeed now there's a lot of speculation on this tweet and what it could mean it could mean a new gameplay trailer it could mean a new gameplay review I love gonna lie if that's gonna happen though I'm not sure it's a little close to release now with probably what two three weeks ago so yes but when this news does drop people I'll be sure to have your coverage right here on my channel whatever that news may be but guys if you did enjoy the video leaving a like really helps out if you like what you see want to see more Hogwarts be sure to subscribe and hopefully guys I will see you on that next one


Hi, I'm Beth King and I'm Michelle Zeiters. We are two of the instructors who teach problem solving with GIS. We have two tracks in our program. We have an experienced professionals track for folks who have a lot of experience with GIS and we have a traditional track for students who don't have a lot of experience with GIS and this class is in that track. In the course we do projects that are based on real-world scenarios. We often hear from our students that they are able to apply what they learn in the course immediately to their current position. And it helps other students to break into the field. We look forward to seeing you in class.


A lot of really, really big plans come from men who often get together.  A woman is a release. Orgasm is a release. In French, literally, orgasm is le petit mort, the little death. So for men to be with a woman is an opportunity for them to basically surrender into this bliss of no longer having to perform. And this is one of the reasons why a lot of guys have stayed in their depolarization. Because a man who has a failure to launch, we see tons of boys like this today. It's because it's much better to have maybe mommy or somebody take care of him to just, well, I mean, he doesn't feel good about this, but part of him embraces the death that is this distorted feminine energy that's on top of them.


Yeah, that's what happens when you put liquid detergent in a dishwasher. I think we got ourselves a little mess on our hands. Now I guess we can put the foam down in there and get rid of all that foam. That's a mess. This stuff, it don't take a whole lot. It'll squirt a little. Let that circulate through there, it'll kill all that foam. I gotta get somebody here to clean this mess up. It's going away and now it's turning back into water. Yeah, what happens is the liquid detergent, it just turns into suds and when it connects with that water, the water dissipates, turns into foam and then it just bombs out your dishwasher. And the only way to get rid of it is to get you a deep foaming agent. You know, you go to the pool and spa place or you pick it up at any home improvement store, the big box stores, and just have it out of the counter waiting for when somebody makes a mistake like this. Let's take a look at it. Foam is gone.


Have you already invested in some cryptocurrency? No, not yet. No, I have not. No, but I have some friends who have. Have you invested already in some cryptocurrency? Nope, we're building them. Oh, okay. Could you introduce yourself to our audience, please? My name's Gino. Gino, you. I'm from Hong Kong, Hong Kong Polytechnic University. I teach there. And then we're doing projects. I do research in consciousness, phenomenology and neurophysiology. And we're exploring cryptocurrencies in relation to consciousness. And so is it constant as a technology? Well, consciousness, well, it's all things in ideas, whether it's money, God, religion, all of these things are in the realm of thought. And so how do these things in the realm of thought now play out in how we play, how we engage in space and time? And so how is the public consciousness changing recently? The strongest, ultimately, it's about emotional attachment. And arguably the strongest emotional attachment that people have today for most people in the population is money, right? But arguably the strongest attachment in the early days that you have is to your relationship to who you are, why you're here, and what this is. And so religions are just like the different languages in Davos about communicating inner experience. So if I say this is a microphone, this is a white jacket, you know what I mean because we have a shared experience. But if I say, I love you, what does that mean? How do I know that my understanding of love is the same as your understanding of love? So all of this is in the realm of thought and the mind. So the value of cryptocurrencies, the value of religion, the value of value is in thought. And so what are the relationships between that, the physical body in relation to the development of the individual? So kids growing up, etc. So there are certain stages people kind of get obsessed with money and everything and that's a stage of development. But then what are the stages beyond all of that? And do you think that at one moment Bitcoin cryptocurrency will become something as this jacket and with some understandable consciousness of an object? Well it all depends on what we decide upon, right? Because its value is only dependent upon like why are the Beatles, why is the Beatles catalog so valuable? Why? Because everybody knows what it is, right? I just say let it be and everyone knows. But if I take a treatment physician off of here and play his song, how valuable is that? The only person that knows it is probably him and the people that walk by every day, right? And so how all of this is in the realm of the mind. And so the fun thing, you ready for this? Physically you're here and physically I'm here but in this conversation, where is this? So if I point at this, what's this? Go in telegraph. Okay, so I'm pointing at this, right? And you know what? If I mention now, and so that's in space and time and you see that. Now if I mention the statue that France gave to the United States that's sitting outside of New York Harbor, what's that? A statue that France gave to the United States that's sitting outside of New York Harbor. Of course. And so here I'm pointing at something in this mental realm, right? And so just as I'm pointing at something here or I'm making you be aware of the beeping that's happening here when I mention the statue, I'm pointing at something as well and you saw it as the Statue of Liberty. So this conversation and back to your viewers that are listening to this, where is this? Where are we right now? Where is this space that this conversation is happening? So I understand that as soon as we go back in time and make Beatles sing a song about cryptocurrency and blockchain it becomes really valuable. Thank you so much. What should happen in order to this market be less volatile, in your opinion? Well, I think there's going to be some regulation put on cryptocurrencies and I think that'll reduce the volatility but also reduce the price. But do you think that it will happen soon? Regulation? Yes. Why do you feel so? Because I think that it's going to be very difficult for governments to allow entities or enterprises to transfer large amounts of money without it being tracked by those governments. So in the US, for example, if you take more than $10,000 out of the bank you get notified about that or they notify the government about that. If you can transfer a million dollars and no one knows it I think the governments are not going to allow that to happen. Do you think that the fact that digital economy is the first subject to be discussed this year and Davos shows that actually cryptocurrencies and blockchain is going mainstream now? Well, I think absolutely it is. I mean, I think cryptocurrencies will continue to survive and I think the frictionless ability to move funds between people I think is a great idea and gets rid of the middle man so I think there's huge advantages to it. I just think there's going to be some regulatory oversight. Blockchain can be used much more broadly than just cryptocurrencies. I think it can be used in genomics, it can be used in tracking title insurance and so I think the whole concept of blockchain is an explosive idea. Really, very crucial to the economy going forward. Could you please tell us, what do you think that digital economy is here this first subject to be discussed? Do you think that blockchain and cryptocurrencies are really going mainstream this year? Well, I definitely think they're going mainstream. I know at least one in five people that have purchased various cryptocurrencies and have it both my husband and I actually started purchasing cryptocurrencies back in 2013 and I think it's unclear at this time whether cryptocurrencies are here to stay or not. However, I do believe that blockchain will be the future as far as ledgers go and how things are recorded and how properties purchased and how we hold ownership to various assets. Digital economy is here the first subject to be discussed. What do you think about cryptocurrencies and blockchain going mainstream? I think that these offer great opportunity but also raise question that needs to be answered. So IDRC is an organization from Canadian government that provide research support in order to fill those gaps. So in terms of access to health services, blockchain technology can do miracle. In terms of control and establishing agenda for this development I think it's a conversation where the developing region of the world needs to be part of and I think here at Davos there's a great openness towards having these type of dialogue. Have you personally invested into some cryptocurrencies? That's a personal question. I don't answer personal question. No, I haven't. And are you planning to? No, I'm not planning to. But why? Tell us. I don't have enough money for that. Thank you.