Welcome to the Crypto Minute! I can sum this whole week up in one word. AHHHHHH! Library lost its case against the SEC. CPI numbers are slightly lower than expected in the markets, go wild! D-Ribbit hacker has started moving the stolen eats to the tornado cash. Betta Mask introduced a tool to help with tokens from one blockchain to another. Department of Justice sees $3.4 billion in Bitcoin. Betta had massive layoffs this week. A rough week for Solana. USDT briefly d-peg. Vitalik revealed a theorem's next round about milestone. Called the scourge. Okay guys, it's time to talk about FTX. I mean, this story has more layers than my outfit. But started as a Twitter spot between billionaires quickly spiraled out of control. So CZ confirmed they were selling a large chunk of FTT. Retail Investor started to panic and some even called it a bank run on FTX. CZ said they're not against anyone, but they won't support people that lobby against other industry players behind their backs. Turns out FTX lent billions of dollars to customer funds to Alameda. In the span of 24 hours, SPF lost about 94% of his net worth and his billionaire status. And CZ did float the idea of buying us, purchasing FTX after some due diligence. Which, after a quick look at the books, was off the table. But we'll see if anyone wants to get entangled in this disaster. He said, commencing that FTX bankrupts, he was very likely without a cash injection. So he needed about $8 billion to emergency fund a billion. Wait, someone should check on Tom Brady. That's nice. There goes Block 5. Then FTX has filed for bankruptcy. And just like that, we all aged about 50 years this week. Oh dear. Keep stacking and best of luck till next week.


It's been a thought for about four years now between Circo and the Department about how we can get more engagement with clients in organic gardening and projects which will keep them engaged, give them important skills but also allow them to have a really meaningful activity that contributes back to our environment as well as beautifying the places where we operate. What we have here is a small hobby size aquaponics setup where we grow a number of barramundi up to plate size. We then have a series of plants which take the wastewater from the fish, convert the waste into nitrates which feed the plants and we return the fresh and water back to the fish tank. So it's an entirely organic process. We're also recycling a hundred percent of our food waste from the kitchen into composting. We're using that compost to enrich the soil and further develop some fruit trees, herbs and other plants for use in the centre and this allows the clients to engage in organic farming techniques and to complement that we're using guinea fowl in place of pesticides to maintain pest control. Yeah the guinea fowl don't damage the surface unlike chickens and other animals which come in and of course they produce their own waste which is beneficial to the soil as well. Yeah we've broadly got a couple of plans for the food. One is that there are charitable organisations within Derby. There's a breakfast program for children who may not be fed during the course of the day. There's also a women's shelter supporting women who are subject to domestic violence and we're looking to support both those organisations who would otherwise need to beg for public monies. We also have snack foods and other things inside the centre and we'd like to filter some of those out in place of healthier options for the clients and encourage them to grow healthier foods. The whole thing's been really fantastic and we've got strong client engagement. We're growing a number of plants very successfully. We're introducing them to techniques which are really exciting and also we've gleaned some learning from them and techniques they've used in Afghanistan to combat some of the hot environments that they come from. So it has been a really healthy exchange of learning.


Good morning. Good afternoon. Good evening. Wherever you're hailing from, welcome to another edition of the developer experience office hours here on OpenShift TV. I am Chris Short, executive producer of OpenShift TV. And I'm joined today by a regular face, Ryan Jarvenin, but also two new faces, Mark Nury and Rohan Kumar. Mark, do you want to go ahead and introduce yourself to the audience? Hello, I'm Mark. I work as a software engineer for Red Hat and I'm currently maintaining the Fabricate Covenants client and the Eclipse JQ project which we will be showing today. Awesome. Rohan, go next please. Hi guys, I'm Rohan and I'm also working together with Mark on Eclipse JQ and Fabricate Covenants client and I'm really excited to be here. Awesome. We're happy to have you here. So, you know, this is new to me. I'll be honest with y'all. So, Ryan, would you like to introduce yourself first? Sorry, I totally forgot. No problem. Yeah, yeah. And I'm a regular on the channel. So hopefully, say hello in chat. You've seen me before. I'm Ryan Jay from the developer advocate team, OpenShift developer advocate team. I have had the chance to use Fabricate a couple times in the past. So I'm really excited to see how things have evolved with this JQ project. Yeah, as am I. Are folks in chat familiar with Fabricate? Hopefully, we get some responses in there from the past, especially if you're using doing kind of automation around Java projects, Fabricate hopefully is familiar for some of you folks and then pull up the chat and jump in there with you folks. If you have any questions along the way, feel free to throw them at us and we'll do our best to answer as usual. Code Walla Walla says Fabricate is great. JP did says he has no experience with Fabricate. So this is a good audience already. Cool. Mark, you want to kind of show us? Okay, I just want to start with a little note. Fabricate was a huge ecosystem, which consisted of several projects. So this is also important to highlight JQ. For those who were familiar with Fabricate, JQ is the successor for the Fabricate Maven plugin, just this part. Okay, so most of the Fabricate ecosystem is deprecated. The other project that is still alive is the Kubernetes client, which we also, Rohan and I maintain. And yeah, these are, well, there are a few other projects that are still alive, but these are the two that we handle. So what we are going to show today is more the part or the new version of what the Fabricate Maven plugin used to be. So in case you were a Java developer, you might be familiar with this, with this plugin, which is something that you would add to your project in order to make it compatible with the with the with the cloud, right? To be able to deploy your application to a Kubernetes cluster. So yeah, I'm, I'm familiar with Fabricate, but JQ is all new to me. So I'm super excited about the show because I get to learn something. So what is JQ? What is its goal? Yeah, okay, so for those of you who don't know what Fabricate Maven plugin was, or in case you've forgotten, JQ is this successor for this. And what it's basically is a set of tools and plugins that will allow you to deploy your Java applications into Kubernetes or OpenShift. Okay, so it consists of three components. The main decor logic is implemented in something that we call KIT, and this exposes a Java API that you can use to generate your container images or your cluster confirmation manifest. So on top of this core KIT, what we have developed are two Maven plugins. The first one, the Kubernetes Maven plugin is the one that you will be using if you are using a vanilla Kubernetes cluster or you are targeting on a Kubernetes cluster. And you can use this to generate container images, and then to generate the cluster configurations, the original files, and to apply them to the cluster. It will also offer other things like generating home charts and so on. But just to, for the overview, it's not that necessary. Then on top of this Kubernetes Maven plugin, we have the OpenShift Maven plugin, which is more specific if you are targeting an OpenShift cluster. So in this case, the default build strategy will be S2I binary builds. So this is what the builds will be performing in the cluster. And then it will generate more OpenShift specific configurations. So for example, it will use deployment configs, or it will generate routes, and so on. So it will produce general configurations, which are more specific for OpenShift. Okay, so basically, just in a nutshell, it's just a Maven plugin that you will be able to add to your project, and it will automatically allow your application to move into the cloud. So the way this works, if you are familiar with other tools, such as dev files or scaffolding or so on, in those, you usually configure the way in which you want your images to be built, and how you want them to be deployed. You provide something, right? In the case of JQ or the Kubernetes Maven plugin or the OpenShift Maven plugin, it's a little bit different. So JQ is smarter in a way. And in this case, the first step that will do the project whenever you invoke any of our goals is analyze your project. It will check the dependencies, the properties, the configurations, and so on. And it will do this to detect which frameworks or which technologies your Java project is based on. According to these inferred configurations or input variables, it will generate some opinionated defaults, and it will generate your images and your configurations according to these defaults that we consider are the best for that application, considering the framework and so on. So for very simple applications, just by adding your, the plugin to your Maven POM XML, it would be enough to deploy that application into the cloud. So of course, there are applications which have higher complexity and we all want to configure more specific stuff and so on. And then we have options to configure the way the JQ behaves. So you can provide some excellent configuration in order to override the defaults that we inferred for you, or you can provide even small fragments of your cluster configuration. You can provide partial files that JQ will read and it will merge with the ones it generates for you. So yeah, I think it's a very powerful tool and in case you're working with Java Project, it's something that it's definitely worth a try. Awesome. So in case you're watching the stream chat, there is a developer experience feedback survey. Let us know what you think about this episode. Let us know what you want to see in the future as well. So feel free to hit that while we're going on here. So Mark, go ahead, Ryan, sorry. Shout out to Natali Vinto, Bluzeman84 in chat. He's not here quite yet today. He might drop in a little bit later, depending what we'll see. But thanks again to Natali Vinto for helping invite our guests today and bring this topic to the show. So thanks again. Let us know via that survey link if you have topics you'd like to see. Nice. All right. So want to show this thing off here, Mark? Yeah. Okay, so let me start by sharing the screen. So not sure how this is going to work. Just let me know. You can do it. I believe. Yeah, no problem. Take your time. Yeah, it looks like folks from the audience seem to be vaguely the folks that are chatting at least sound like they're somewhat familiar with Fabric8 and definitely with Java. Okay, so I'm not sure if my screen is already. Yeah, I think. Yeah, you're good. Yeah, looks good. So we are usually when we are demoing or in other conferences, talks, and so on, we are usually showing the inner loop. So how a developer interacts with OpenShift or Kubernetes by using jcube. And today we wanted to show something different, because in most cases, jcube is something that you want to use in the outer loop too. So to define your pipelines and maybe your continuous delivery strategies. And the plan for today is to bootstrap a Quarkus application, add jcube, push an image into Quay, into Quay registry, and then deploy this image into into the developer sandbox cluster that Red Hat provides for developers. All of this using a GitHub actions workflow. So, yeah, I don't know if it's clear. So far. Okay. So, okay. Question in chat. What is the integration with CI CD tools such as Jenkins or Tecton? Like, okay, so you will see today with GitHub actions with with a GitHub workflow, it will be more or less the same with Jenkins. Basically, you I mean, when we finish the pipeline, you will see that it's something really, really straightforward and easily portable to any other platform like CircleCI, Tecton, Jenkins, whatever. Okay, so I'm going to start with this repository, which is now empty. Okay. And the only things that I have are for secrets that will be used in the pipeline in order to be able to both deploy into Quay. These are some credentials for Quay. And this is the token for the for the sandbox. Okay. Got it. So, first step.  In this case, I'm going to add rest easy. And you click on download the zip. There you go. You have a bootstrap application for you. So this is my idea. I'm going to unzip this here. Second because And by the way, audience, if you cannot read something on screen, please let us know. We can always tweak things. Yeah. Okay. Okay, so now it's taking a little while but anyway. Well, you've got your camera and everything else on zip something compression, you know, that kind of thing. Okay, so now we recognize the project. I don't know why it's not showing up here. Yeah, I always struggle to do demos and type at the same time. And especially try following along with chat at the same time as well. Another level of Yeah. Exactly. Okay, anyway, the project structure has has updated. Okay, so well, when you when you would start the project, the first thing that you might notice is that it creates this Docker directory with some Docker files, lots of stuff here, both for native and for JVM mode. So the good thing with JQ is that we can go ahead and remove this. Not needed. Okay, let me check my notes. I don't want to miss anything. Okay. So also, the bootstrap project contains a test which tests the endpoint. I'm going to remove this because I'm going to change the endpoint a little bit. So in order to speed things up, I'm going to remove the tests. But please never, never remove your tests. In fact, you should be adding tests for everything that you implement. Okay. So, okay, so this is the endpoint that's provided for you when you watch the project and chase. Hello, rest easy. Let's modify this to open shift. Okay. And now, basically, we lose you. Might have lost him. I don't know. Yeah, he said he was having power issues. The screen share is still going now. Yeah, but it's not moving. Yeah. Wow. Rahan, are you the backup? Are you second fiddle here? Or congratulations, you made it to the front row. Yeah. Okay. So the plan was that if in case his power goes down, I'll showcase the inner loop perspective. Okay. So I was kind of joking that you'd have to jump on right now, to be honest. But if you have something ready to go, that's super cool. Yeah, I don't know if you lost mark for good or not. So yeah, hopefully rejoin. Yeah, I think I'll go with the inner loop for now. And I hope that he comes back while we are demoing that. Sounds good. Okay. So I'll go with starting to share my screen first. Yeah, you should be able to call out. And if not, let me enter a screen. All right. Can you see my screen? I can see me. Okay. All right. Okay. So I already have that caucus project bootstrap that was bootstrapping. So I'll just try to open it up with my IntelliJ. And it's going to take some time to load up. Okay. Is this a different IDE than we had that? No, I think it's the same one. Yeah, both our IntelliJ or demo iterations. So I think it's the same. Maybe he has dark mode on or something. Yeah. Yeah, he has dark mode on. I usually keep the mode to light mode for presentations. Yeah, since it's a bit easier to see. Anyway, so this is a standard caucus application. So as you can see, Mark would strap the project and it would strap the standard caucus project with all the standard dependencies. So very basic. And it has this simple endpoint of hello, and where we are simply running OpenShift, hello OpenShift.tv. So let's just try to run it from our locally caucus.mvn. So in order to run it, I'll just package it first and just compile it so that the job builds up and everything is fine. Is this like a test pass to make sure that it'll Yeah, I have built it earlier as well, but it's just a test pass. So it should be finished now. OK, so in order to run, I would run it just like any other caucus application. So so I'll just run it in caucus.mvn. And I think we should be able to see it on, access it through a browser. Oh, it's accessible now. Oh, it looks like Mark's back. OK. Yeah. Yeah. Yes, let's just keep rolling with Rohan's deal and. OK, sure. All right, so I just launched having been caucused there and I was able to see the application running locally and our end point should also be doing just fine. Hello OpenShift.tv. So there you go. So we have the application running locally and as a job developer, this is the thing that we are all familiar with. We are all familiar with reaching our code and deploying it locally onto our local machines. But now we want to deploy this same application to Kubernetes. And here for Kubernetes, usually our developers have, when they are testing the applications on top of Kubernetes, they usually have some local Kubernetes clusters running where they can play with the application. And right now I'm using Minicube for that and my Minicube seems to be running. So first, I'll start with containerizing this Java application into a into a container image and pushing it to some container registry. So if I would have been not using JQ, I would have to write a Dockerfile first and then run the Docker commands like Docker build, Docker push to do that. But when I'm using JQ, I only need to add this plugin. So I have already added it just to save time. So in order to use JQ, you just have to install a simple plugin in your Pongot XML. So just like any other Mewen plugin, you are just adding another Mewen plugin to your project, which deals with the Kubernetes operations. So once this plugin is added, we can go ahead and start using it. So I'll first start with containerizing the application into a Docker image. So first for that, it's just easiest running this code and we get this build. And since the plugin is in profile, Kubernetes Mewen profile, so I'll just specify the profile here and it's going to start building the container image for our application. Cool.  Yeah, yeah, it's because of the equivalent. JQ generates them, so JQ generates them automatically. And you see that JQ took this image as the base image for our application. And I'll show them. So JQ, I'll talk your Docker. All right, so JQ generated a default open-unit Docker file for you and it submitted it to the DockerDemon that was running. And it used that to build your Docker image. So I'll try to run this image locally from here. Docker run, okay, it seems to be running just fine. And just like running it locally. So now we want to push this application. So generally, this is the standard workflow when you're working with Kubernetes, you have to containerize your application, you have to push it to some registry, external or internal public registry. So I'll start with pushing it to my Quay. And for that, I'll... So right earlier, we saw JQ built the image. Let me check the images. So JQ built the image with some default name because we didn't provide any kind of configuration of what kind of name we want to have. So we can easily change, we'll first try to change it and we would need to change this to align it with standard Docker image names like registry, username, and then name of the repo, tag, et cetera. So in order to do that, I'll just do MNK just built and I'll provide that parameter to JQ that JQ use this as the name of the image. So the history will be Quay.io. I'm just going to append it to the name and my username. And the quote Quarkus, what was the name? Quote with Quarkus, okay. And the MNK just built Quarkus and latest. So this would configure JQ to generate the image but with this name which would allow us to push the image. Oh, sorry, I forgot to specify the profile. And it's in the Kubernetes profile. So one thing that's really nice with JQ is that you can use it like any other main plugin and we are used to use different kind of profiles when we are building projects. So you can have, you are building your application in standard mode, you just build it as a jar when you can have a Kubernetes profile or Docker profile too. So to have your image, have your application packaged as a jar or as a Docker image. So, okay, so the build finished and seems like JQ created the image for us with the standard with the name we provided. So I'll just try to push it. I would need to specify the property again. Okay, so then I have, so JQ allows you to configure the registry credentials either through Docker login or through your Maven settings.xml or through the plugin.xml configuration. So you can configure the... So I'm pushing to some registry and we need to provide credentials for that. So I have them in my M2.xml, settings.xml. Just like any Maven repository, you provide credentials for your Docker registry, container registry here, and it's gonna work fine. So it's pushing now. Yeah, the good thing from with JQ is that it reads the credentials. So let's check whether the image is there or not. So I'll go to that way and code with Quarkus is there. Tags, and yeah, looks like it was pushed a few seconds ago. So we looked at how we containerized the application to a Docker image and pushed it to some registry without even having to take a look at Docker or Docker files anything. Just plain old Java way of doing things. So now we will try to generate the Kubernetes manifest. If you are not using JQ, you would need to use write the manuals, but JQ has a goal for that, which is to communicate this resource. And it's going to generate opinionated manifest for you. And I would need to specify. So, okay, I think I can just add it here in my POM.xml, the property for the image name. JQ to generate. While you're working on this next step, you might have to pause it a little quick for questions. This can easily configure through properties, but for now I'm just hard coding it here. I'm not sure. Okay, so I'll just try to include this resource and the Kubernetes profile, and it should generate the resources for us. So it's okay. So as you can see, it generated a service, and let me show you the project folder. So as you can see, it generated the target classes. It generated the Kubernetes manifest. It generated an opinionated deployment for us with some additional things, additional labels, which can easily be configured. And it generated a default service for us. So all this without even knowing how to write YAML or anything, so which is really a good point when you're getting started with Kubernetes. So, awesome. And the image name also seems to be correct. So we built the image. We pushed it to some registry. We generated manifests as well. So we just have to apply it to Kubernetes cluster. So we can go ahead and do that as well. So just like Qubectl, due to Qubectl apply, we have this code called ambient keta supply, which would just pick these manifests and apply it onto the Kubernetes cluster. So I think it's hilarious that you and I have the same problem spelling Kubernetes at times. Always the R and the anti-reverse. Okay, so it looks like it deployed the application and Pod is running as well. So I'll just shoot it again. Okay, I think it's from the previous one when I was testing the demo. And I'll check the services. And it's a cluster IP service. So which means the application is accessible from within the cluster. We'll change it later. And okay, an application seems to be working fine. And I'll just exit it from here and I'll generate the resources again. So by default, JQ generates the service with a type cluster IP, which means it's only accessible from within the cluster. But let's change it for the demo purpose. I'm in Kubernetes resource, keep the supply, and I'll just provide a property in JQ.invichir, JQ server type, and I'll just specify the profile here. And it should update this service type to our node port. So. Well, this should let us curl that particular service from outside the cluster. All right, so it looks like it's a node port now, so we can access it from outside cluster as well. Just check what's the node port. So our node port service can be accessed as at a static port on the node's IP. So we should be able to access it like this. And yeah, now our application is running inside Kubernetes and I'll just try to check the hello, and it also seems to work just fine. So this pretty much sums this demo for, I mean, the first part of the demo, I'm not sure where the mark wants to take over from here or not. Yeah, Mark's back. He seems stable for now. Welcome back. Yeah, sorry for before. I'm having trouble with electricity this afternoon. It's really bad timing, sorry for that. You should have gone into the office. You're so funny. Yeah. Okay, anyway, I'm not sure if my connection is fine or my videos are fine. It's fine. Thank you. Oh yeah, I'm going to share again my screen. I think we were just around the spot. You had just deleted the Docker's bits and they moved maybe a little bit past that. Yeah, I think it's good that Rohan also showed his part because we actually got to see what I'm going to describe in the pipeline. So any questions for Rohan before we jump into this next bit? Yeah, good point, Ryan, right? Like there was golf claps, people were hyped in chat, but any questions? Was that not clear? It seemed pretty clear to me. One of the first steps that you did, Rohan, was a maven build locally. That build is actually going to happen in the cluster normally, right, when you're running that? So whenever you are packaging your application, you would be packaging it as a container image. So you would put the jar inside that container image. So I don't think it would be... Oh, so you would be doing a local build. It performs a local build, but if you are using the OpenShift Maven plugin and it uses the S2I build strategy, the build will happen in the cluster. So it depends a little bit. Configurable. Okay, all right. I just wanted to make sure I understood the workflow, how things were going. And especially when you're doing local, you want to do those builds locally and get that local test feedback before you make your commits or promote your changes. So yeah, nice job on the local loop. Definitely. Okay, so yeah, from my side, so I'm not sure why part of this... The wrapper, I deleted the wrapper. Anyway, I would use the Maven normal. So basically when Java 11, okay, sorry, my flow stopped before. So now it's hard. Okay, but basically the application we bootstrapped should build normally. We remove the tests. Yeah, so now we can configure the POM. There's one small change in the new... In the new Quarkus version. And by default, it's now using fastjar packaging. But JQP still doesn't recognize this. So we are going to configure the application to use the Uberjar instead. So basically when we package the application, we should see here the runner jar. Yeah, so we generate this runner. Okay, and next thing I'm going to do is I'm going to create a profile specifically for the CI environment. So for the build, I'm going to add the OpenShift Maven plugin. Okay, I have a few properties that I'm going to describe now. So as you saw before, Rohan configured the name of the image. This is important because we are going to publish this into the Quarkus registry. So it requires that these matches with my registry information. Also, since I'm going to use the OpenShift Maven plugin and I want the build to be produced locally because I want to push it. We still don't support pushing from the OpenShift Maven plugin. So I'm going to use the GIP strategy, which does support it. So what J-Cube will actually use GIP in order to build the container image. And then, since we are going to deploy to the Dev Sandbox, usually J-Cube generates a deployment config, but the Sandbox is based on OpenShift 4.5 or 6 or 7, I don't know. We still don't support. Sorry, my bad. Okay, so anyway, what we want is to generate a deployment. Also, because in order to pull the image from GIP, it will work better. So basically, this setting what generates is a deployment instead of the default deployment config. Since we are working with a snapshot and we are not providing versioning, so the image is always in the latest. What we are telling J-Cube to do here is that whenever we apply the resources, that it should recreate them. So it will tear down whatever it created before and then it will create new resources for that. And again, for the deployment pull policy, we are going to use always. Again, because we are using this latest stack and we are going to overwrite it. This could be like maybe the continuous delivery pipeline for a Dev environment. So we are using this latest stack and we want it to be refreshed. So even if the image exists in the cluster registry, we want it to be pulled again. So this is the other setting that we are going to add. Okay, so this is my query register, which is empty. And now I'm going to start by creating the GitHub pipeline. So, okay, so this usually goes, this goes in the GitHub workflows directory. And I'm going to create pipeline. Okay, so I have some settings already. Okay, so the name of the pipeline, demo pipeline. And we want this workflow to trigger whenever we push to the main branch. The first steps would be, I'm going to remove this because I didn't add the wrapper. Okay, but what we want is, this is what probably all of you are familiar with. So basically what you want is to build the project and check that everything works and so on. So some of the files that were added with the Quarkus bootstrap, I deleted them by accident. And now... Oh, boy. Anyway, I'm going to just use this feature from... Okay, anyway, let's see. Is there the advantages of using an IDE? I'd never be able to undelete things with my command with my Vim editor. I know, right? Okay, so lots of stuff got added here by accident. Yeah, anyway, this is the important thing. And commit files. So this was the empty repo. It should contain some files now. And a new GitHub Action workflow should have been started. Okay, so this is usual stuff, right? Check out the repository, set up Java 11, and start the build process for Quarkus. Hopefully this will complete once it allows the dependency. The project is not that complex, so it should take like 30 seconds. But basically this is what we all know. Okay, let's wait for it to complete. So build success, and yeah, it completed successfully. So the next step that I want to add is the push-to-quay. So what Rohan did manually, we can add this to the pipeline. So again... Where was that build running? That last one he showed? Yeah. In the GitHub virtual machine. So the workflow working on a virtual machine. So you define... Well, yeah, you define here the base image where this job is going to run. So this is running in Anubuntu virtual machine on GitHub. Okay, so my laptop is not... Right now it's free. As we were saying before, for the credentials, when pushing, JQP is really smart and it will try to infer them from your laptop. So if you have settings in your M2 directory or if you have your... You logged in through Docker or whatever, it will take them from your laptop. But since we are running this in a GitHub action, we need to provide these credentials. One of the ways that we can provide them are by using these variables, okay, these properties, these minimum properties. And when I was showing you the repository, I also showed you that I had these two secrets defined. So these basically are defined here. I will show you again, but very quickly. So quit username, quit password. And this match with my robot account. So I have a robot account, which has credentials for this specific repository. And these credentials are the ones that I stored in my GitHub repository. Okay, so just by adding this, we should be able to push to Quay. We should see another action being triggered now. Same steps as before. The first thing, it will build a project in the virtual machine that's put stuff here. And then you can see the new step that's already here, push image. So whenever the build completes, again, 30 seconds or so. So Quark was downloads lots of dependencies. So now my repository is empty. And once the action completes, we should be able to see the push image here. Pretty fast for a Java build. I was about to say, yeah, like... And free resources, you know. Usually with free hosting, I'm like, oh, this build's going to take an hour or, you know. Right. No, but it works quite well. So now it's in the push step. So you can see it's running here. And then once it downloads the JQ dependencies, you should see that the JIP build is starting. And then that the push step is also. So it completed successfully. We now move here. You can see that the image was pushed. And just a moment ago. So if we check the image content, we should see that the JIP core base layer and then the layers that we added on top of it. Okay, so next step, we want to deploy it into the developer sandbox. So probably you've seen this a lot of times in these OpenShift TV shows. We've mentioned it once or twice. Yeah, I'm going to mention it again. Just for good measure again. Yeah. Okay, so it's really cool because we can get to try OpenShift as developers. And this is my cluster. Right now it's clean. And one other tool I wanted to show today because it fits really well with what we are showing is the OpenShift, the OC login action to login into an OpenShift cluster that it's provided by Red Hat. So this is a Github action. And I'm going to add it and I will describe it. So basically, next step, authenticate with OpenShift. We need to provide these input variables, the server. This is provided as a secret, the token. So this is the one that you would get when you go here and copy login command. You would see that there is a token there and the server. So you would get those values and you can set them in the Github repository as secrets as we saw before with the Quake credentials. And I'm also going to set the name space because by default, whenever you login into OpenShift, it uses the code. I'm not sure why, but anyway, I'm going to set the name space too. And finally, I'm going to add the invocation to GQ. So what we saw before that Rohan did locally and in this case, generate the cluster manifest and apply them. And you can see it's a very, very simple pipeline, but it's kind of powerful because it's doing a lot of stuff. Again, push. If everything works, we should be able to see a new action invocation. New action, new build, new deploy, queued. So same as before. All right, we did the steps all of the times, but I think it's clearer, right? Does any of these build results get streamed back to your IDE? Or is there any back flow of communication? Well, that's more just a push. That's more up to if you might be able to configure more stuff with GitHub actions. I mean, the integration of GitHub with IntelliJ is pretty cool. But I mean, there are tons of things that you can do. I'm just showcasing how, like a very, very simple pipeline, but it's actually kind of powerful because with other tools, in order to do this, you would require a lot of I don't know, lots of configuration, lots of stuff. And you can see that this is working really out of the box for a recently bootstrapped Quarkus project. So again, now when you see the deployment, you will, I mean, it's kind of, for me, it's mind blowing. Okay, so now it's the authenticate step. So if everything goes well, this should succeed. And now the part where we are deploying to the dev sandbox. So if we go, if we go to the query repository, this should update to a few seconds. And here we are already seeing that we have the deployment. Okay, so if we open here, we will be able to see low, low open shift TV, just like we configured in the project. That's awesome. So yeah, the next step can be like very easily. I'm going to change the resource and, okay. So continuous delivery, right? So fifth, change the reading, let me tap push. Again, we should be able to see a new invocation of the pipeline. And when this completes, the result here should obviously change to the new value, right? I'm not sure if there are any questions that we can answer while this builds, but... Looking through chat. Yeah, same. I haven't seen any. I saw one earlier that's asking about the differences between the open shift plug-in and the Kubernetes plug-in. Right. Rohan kind of answered that in chat, but let's talk about it on there. Okay, so yes, I think I said this when we were introducing the project, but again, Kubernetes, maybe I'm plugging is the one you want to use if you are targeting any Kubernetes cluster, even if you want to target open shift. But if you want to use the more fine grained configurations or specifics for open shift, you should be using the open shift made on plug-in. So it, especially for the inner loop where you want to debug and do all of this stuff, it kind of makes more sense because the builds will run in the open shift cluster and lots of things that are more specific to open shift. However, if you prefer to use the Kubernetes made on plug-in to target an open shift cluster, there's no problem either. You will stick to the vanilla resources that Kubernetes offers. So this completed again and basically this should, yeah, so if I refresh and we can see the new message. I'm not sure if we have time, but we can also show if this doing this for native, but it will take like five minutes for the build. So I'm not sure if we have time for that, but basically adding another flag will enable this to create a native build and produce a native image. So Natali is asking in chat about the inner loop. What's the state of podman support for jcube? Okay, so podman with the new versions should be supported because basically if you, well, if you want to use it with this, you should install the podman docker tools. So it will basically be transparent. If not, we support podman by configuring the docker host environment variable, but this takes more work. So you need to actually start the podman in a given mode and then configure the host. So depending a little bit on how you want to, the complexity you want, if you just installed the docker, I'm not sure how the package is called, but if you install this docker toolset, it should work for you. Question in chat. Does native require corkis? Like is corkis a dependency? I don't think it is, right? That's a native? I'm not sure. I don't understand. I don't know what code Walla Walla defined native a little bit better, but is there any dependency on corkis at this point? No, no, no, this is basically, I'm using corkis to showcase how this works, but you can use spring, you can use even micron out now, so you can use whatever. Okay. I'm just going to set this just in case we have time. But yeah, there is no need to add to have corkis. JQ works with many different frameworks, spring boot, wide fly, I don't know, you name it. Even if you, even a standard Java application, which has nothing else, you can configure it and it will work. So no dependencies. Also, I would like to highlight that we don't depend on any CLI tools. So usually when you are using other tools, I don't know, any other alternatives to JQ that are not for Java, you need to install something, right? So for scaffold, you need to install their CLI or things like that. The nice thing with JQ and Java projects is that you can add it seamlessly to your project, like another Maven plugin, and you don't need to install any other dependencies. So that's kind of a great advantage in order to add. You can see that the pipeline here was really simple. We didn't need to set up any other things. Yeah, I really like this. If you have a shared release pipeline and you want things, different kind of core components hosted, this gives you a great way to showcase that and have certain shared assets beyond, in this case, hosted on Play. You could also swap in Docker Hub if you wanted to. We had two credentials to get into the Play environment, but there could be probably Docker Hub credentials if you wanted to go that route, right? Yeah, exactly. Is this tied? I guess so this is pretty tightly integrated with... No one else has GitHub Actions. That's a GitHub thing, I guess, right? Yeah, yeah, yeah. That's pretty... If there's an equivalent to other CI systems or something, but this is specifically a... GitHub Actions are the big plugins for the GitHub workflow execution. So it's the way that you can add functionality to these workflows. But if we review the pipeline here, I mean, this can be a big step in any other CI environment, Jenkins, Travis, Circle, anything, and it's very easily ported. So you just need to run a few maven commands. This is not, but obviously you could use OC login or whatever, or you could configure the OpenShell credentials using our plugin. I use this because I wanted to showcase this other tool and how well it integrates. But the pipeline is really simple. Also, if we check what we configured for JQ, as we said before, JQ impairs almost anything. The things we configured were more related to this being able to reload the latest tag in the cluster and things like that, but nothing specific for the application. So you can see that it's really, really easily configurable. So, okay. So I triggered a native build just in case we might have time to see how this pans out. But basically, to make it native, I just added a profile and a flag for JQ, and that's it. And it will switch to native. So that's kind of cool too. Nice. This is very nice. I like this. Any questions from the audience at this point? Just out of curiosity, get them in now before you have to jump to another show here in two minutes. Yeah, we got a wrap up.  I like seeing how this is progressing and the growth around GitHub actions. That action support gives it something kind of uniquely different from what I've have been seeing with the Odo command line tool and that kind of development pattern. One of the things I like from doing a Odo push is the build results are streamed back to your command line. Or you can tail a log of the build. And I know it's totally available in GitHub, which is even nicer because then, in a way, if I had a team of folks that I wanted to share those results with, this is maybe a more centralized kind of hosted approach for raising visibility on some kind of shared assets that you want to make sure everyone has access to. So for more advanced pipelines, this is really, really cool. Really cool. Really, yeah. Awesome. Cool. Well, I think we ought to move it on to the next show. Yeah. Thank you very much to all of our guests today.  Yeah, thank you to our guests. Thank you, audience, for watching. We're going to be talking about a brand new project called SigStore up next on the Upshift Commons Hour with Karina. So look forward to that. SigStore is going to make signing images and signing things in general. A lot easier in life. So this will be a great show coming up. So thank you, Mark. Thank you, Rohan. I really appreciate you both coming on and seamlessly accounting for your power issues as well. Good stuff. Okay. Thank you very much for having us. Thanks. See you all next time.


Gold contract up $2.40, trading at $16.78 an ounce. We have Silver up 8 cents, $20.87 an ounce, LightSuite crew down $0.67, $91.94 a barrel, notes and bonds, a 10-year note down $126, trading $109, $20, 30-year off $28 at $118, $18, $18 in Kingdala. Kingdala is down $762, trading $110, $114, the euro is at $1 to 1, the yen is at $146, and the British pound is at $115 to $1 U.S. We can open and take a look at the S&P, this is going to give you the, we got divergence here man, it's going to be interesting. So you have the dollar bottom up, it's given the market breathing room. That being said, the contraction and volume on the S&Ps today is quite incredible. You know we did $103 million on Friday, we're at $43 right now. So you hold in price, I mean anything over $3.78, $5.87 says you can still go higher, so but this contraction is pretty intense. NDX 100, we take a look at the NDX, what do you have with the NDX, set this baby up and what do you have inside the NDX, the three Q's, same setup, 35 million shares, you did 78 million. So I suspect that when you look at this, this is telling me that okay, it's just not going to go right to the top of this range right now, you know you're going to get some other quirk and we're going to come back down to this and test again. Now the good news is that the Friday, the volume was so big in the Friday, let's say if you went higher to yesterday, come back down and test the highs of that Friday bar. You know if we get over to the doll or the bottom line, this was the ultimate Bud Rolfe setup folks, God bless Bud. I mean the bottom line is that when you look at this, okay, it is absolutely incredible. It goes right to the, under the trend line and gives it up with conviction. You give it up with conviction, bottom line we're going to 104 and here's the divergence, the bottom line is that dollar down, markets up, metal up, everything up.  If the bonds are going up, the dollar will continue down, the market will go up and metals will go up, but there's divergence in the middle of it because of the fact that the contraction is so large inside the NDX and the S&P. Larry there folks come right back.


Hello and welcome to Newsclick. Vice President of India, Jagdeep Singh Dhankar, recently issued a notice to CPIM Rajesh Sabha MP, John Brita's, over an article in the Indian Express. The article suggested that Union Home Minister Amit Shah should desist from making disparaging remarks against any state. Following this, a complaint was lodged with Dhankar by BJP Kerala official and Dhankar acknowledged. To talk on this, we have John Brita's with us. John, sir, thank you for talking to Newsclick. My first question would be that we saw former Vice President Venkaya Naidu praising your work in Rajesh Sabha. Then this complaint and its acknowledgement by current Vice President Dhankar. How do you see the transition and your comments on the complaint? Ask me, ask questions on any constitutional positions. I am glad that you referred to the compliment passed on by the former Vice President. And I have a good work in relationship with the President Rajesh Sabha German also. But now, as it has been widely reported, I had been called for a meeting with regard to a complaint lodged by a media functional charging me of sedition because I wrote an article in Indian Express regarding the comments of the wonderful Home Minister of this country wherein he had passed certain cryptic remarks against Kerala. So I feel that BJP is dragging constitutional offices into parochial politics. That is how I intend to see these whole gamut of issues. You have been a journalist and as well as an MP. So the complaint brings us to the fact that tradition has been increasingly used against journalists to silence them. After this complaint, how do you see the colonial law and I mean what would be your case for discarding it? I am amused or rather baffled that at a time when the Supreme Court is seized on its matter, when this charges of sedition or rather this archaic colonial rule or law is being misused ramblerly in this country to silence political opponents. And this is a danger where a BJP functionary is referring to this sedition and lodging a complaint with the constitutional office of this country. Interestingly, the other day the union government had filed an affidavit saying that they are at the advanced stage of reviewing the sedition provision. So I don't know, I mean what is the intent of this saying that they are trying to review the sedition provision whereby their own political functionaries are trying to implicate political opponents by bringing this very anachronistic at the same time draconian provision. That is where I mean I am at a loss to understand what is the real intent of this government. I am asking you because this law was used during the independence movement against the journalists who wrote against British government. So that's why I asked you why should we have a law of this kind right now in democracy? We should certainly take it away from our rules and regulations and laws. That's why the wonderful Supreme Court is hearing various petitions and naturally the Supreme Court itself has passed the structures on the government wherein it has castigated the government saying that this provision is being misused rambly. As a journalist, as a lawmaker, I am of the firm opinion that see this is detrimental to the constitutional provision, detrimental to the spiritual democracy, detrimental to the freedom of speech and expression and this is detrimental to the very process of democracy itself. So it is high time that we take it out of our bench of rules and regulations. I have no second opinion on that. Yeah, so I was going through your article I mean which has been cited in the complaint. In your article you argued the case of Kerala being a multi-religious society, it's celebrating its diversity and then there are attacks on it. So we have a new film called The Kerala Story and there's a concealed attack on it. How would you explain this phenomenon? His remark of the honorable Home Minister against Kerala while he was campaigning in Karnataka, he made a comment that it was absolutely unbecoming of a Home Minister. He said that Biber, Kerala is near you, doesn't mean that Kerala is an enemy country, doesn't mean that Kerala is part of Pakistan. He should have relied on the indices of the Central Government itself saying that it should leave that Kerala is your neighbor because Kerala is ahead of many states including Karnataka won't many of the socializes instead of comforting, instead of telling Karnataka that we should be happy that your neighbors like Kerala, he is making cryptic comments against Kerala and even this Kerala story which has been brought up is of course part of the agenda to discredit Kerala. I have been always arguing in parliament and outside saying that if a state doesn't caves into the diabolic game of the ruling party, you either disrupt it or defame it. So the very purpose of RSS ideology is to make sure that the opponents are defamed and disrupted. In the case just because Kerala is steadfast against its position with regard to the BTP policies or we have not given an inch of land for the BTP in this state, just because of that we have been discredited left and right by the rulers in Delhi.  The first teaser said that 32,000 girls have been reported to IS and have been taken to Afghanistan. Ridiculous. Now they have amended the teaser by saying that this 32,000 has come down to three and with regard to the I would say the IS menace, I would say that India is insulated from the terrorist menace. It is obviously we have to take care of that but we are a better state compared to states like UP or any other state like that. If you look at the people who have gone to IS or joint IS, I would say that there would be many more people who would have gone from states like Uttar Pradesh rather than Kerala. At the same time, BJP is trying to create a campaign where in my Kerala has been depicted as the format of terrorism, ridiculous humbug. I would earnestly urge the people to see this diabolic game and ensure that the agenda of BJP is defeated at any cost. So this is my last question. I mean we are seeing, I mean ministers like Kiran Rizu referring to judiciary and I mean the essence of it could be understood that he is referring to it in a threatening manner. So and I was going through your article which basically said that the secretariat positions in Rajasabha and Lok Sabha both are being filled by central IS corridor. So is it after judiciary, is it a new attack on opposition through executive? Yeah, I feel that the tentacles of executive is everywhere. And while the media is concentrating on the inverted comma disruption of both the House of Parliament, none of the journalists have looked at the tweaking that has happened to the Rajasabha and Lok Sabha secretariat. That's why I wrote an article. He said that the executive has virtually taken over the independent secretariat of Rajasabha and Lok Sabha. Even during the British period, the assembly, it was called assembly like that. The chairman of the assembly at that time, I think it was brother of Sardar Patel, that is Viterbhai Patel. He fought with the British to ensure that the secretariat of the council or the assembly is independent. It has got independence to ensure that it's a different pillar and not being integrated to the executive. Now what has happened that in a democracy where the parliament has to ensure that executive is accountable to it? Representatives of executive, those officers who are at the helm of the executive positions in the government secretariat are being brought in to preside over Rajasabha and Lok Sabha secretariat. I have nothing against any individual officer. But the culture of independence of both the secretariat is being corporate. And this would have, I would say, far reached the consequences with regard to the functioning of the parliament. Thank you, John sir. Thank you for talking to Newsclick. For rest of the news, stay connected with Newsclick.


Stories and content in Weird Darkness can be disturbing for some listeners and is intended for mature audiences only. Parental discretion is strongly advised. The lobby of Hollywood's Biltmore Hotel is crowded on a warm and sunny afternoon and early spring. A man crosses the room and taps on the call key for an elevator. As the door opens, he steps inside and presses the number 8 button for his floor. He glances down as he does so and he sees that the number 6 is already illuminated. With a quick glance to his left, he realizes he is not alone in the elevator. A dark-haired young woman stands in the corner and as he looks at her, she offers a faint smile. The man smiles back at her and then looks up as the numerals above the door light up with a passage of each floor. He glances at the reflection of the woman and the polished steel of the doors. Even in this blurred view, she is stunning. Her dark, nearly black hair is swept back and up in the outdated style of the 1940s, although it is very becoming on her. Her skin is pale, perhaps looking even more so against her jet-black dress. The shiny material clings to her every curve. She makes no sound other than the soft rustle of her dress. Finally, the elevator reaches the sixth floor and with a soft chime, the doors slide open. The man steps aside to let her pass and notices that she is not moving. She continues to stand in the corner, seemingly unaware that the lift has reached her floor. He finally speaks up and his voice seems to startle the girl. He says this is the sixth floor. She steps forward and moves past him off the elevator. As she does, the man trembles involuntarily, a wave of chilled, ice-cold air seems to brush past him as the girl departs. Goose flash appears on his arms as he watches the shapely young woman walk past the doors. Then, just as she steps out onto the sixth floor, she turns back to look at the man inside the elevator. She does not speak, but there is no mistaking the look of urgency in her eyes. She is begging him for help, the man realizes, but it is almost too late. The elevator doors have started to close, cutting off the young woman as she tries to re-enter the elevator. The man frantically pushes the button that will open the door again and just before they close completely, they slowly start to slide open again. But the girl in black is gone. Confused, he leans out into the lobby of the sixth floor. He looks quickly in both directions, but the small lobby and the hallways in either direction are empty and deserted. Where could she have gone so quickly? He calls out, but his voice echoes in the stillness of the corridor. The young woman had vanished, as if she had never existed at all. Two days later, the man is browsing in a local bookshop and happens to pick up a book about true unsolved mysteries. As he flips through it, he is startled by a face that he recognizes. It is the girl from the elevator. He looks at the photograph and is convinced it is the same young woman in black, and that he realizes such a thing is impossible. Scanning through the text, he sees that the girl died years before. How could she have been at the Biltmore Hotel just two days ago? How indeed could this young woman, who was killed in 1947, still be lingering at the last place that she was seen alive? Is she still looking for help from the other side? The face that the young man and many others just like him recognized once belonged to a beautiful young woman named Elizabeth Short. In death, she would come to be known by a more colorful nickname, the Black Dahlia. Her tragic murder would forever leave a mark on Tinseltown. She came in search of stardom but only found it in death, becoming lost in another world that is the dark side of Hollywood. I am Darren Marlar and this is Weird Darkness. Welcome, Weirdos. This is Weird Darkness. Here, you will find stories of the paranormal, supernatural, legends, lore, crime, conspiracy, mysterious, macabre, unsolved and unexplained. Coming up in this episode of Weird Darkness, Elizabeth Short was brutally murdered in Los Angeles in 1947. Her body cut in half and severely mutilated. Her killer has never been found, leaving one of the most infamous deaths in Hollywood history. While you are listening, you might want to check out the Weird Darkness website. At WeirdDarkness.com you can find paranormal and horror audiobooks I have narrated, 24-7 streaming video of horror hosts and classic horror movies. You can find my other podcast, Church of the Undead. Plus, you can visit the Hope in the Darkness page if you are struggling with depression, anxiety or thoughts of suicide. And you can also shop the Weird Darkness store where all profits go to support depression awareness and relief. You can find all of that and more at WeirdDarkness.com.  On January 15, 1947, a housewife named Betty Bursinger left her home on North Avenue in the Leemirk Park section of Los Angeles bound for a shoe repair shop. She took her three-year-old daughter with her and as they walked along the street, coming up on the corner of Norton and 39th, they passed several vacant lots that were overgrown with weeds. Bursinger couldn't help but feel a little depressed as she looked out over the deserted area. Development had been halted here, thanks to the war, and the empty lots had been left looking abandoned and eerie. Betty felt slightly disconcerted but then shrugged it off, blaming her emotional state on the grey skies and the cold dreary morning. As she walked a little farther along, she caught a glimpse of something white over in the weeds. She was not surprised. It wasn't uncommon for people to toss their garbage into the vacant lot and this time it looked as though someone had left a broken department store mannequin there. The dummy had been shattered and the two halves lay separated from one another, with the bottom half lying twisted into a macabre pose. Who would throw such a thing into an empty lot? Betty shook her head and walked on but then found her glance pulled back to the ghostly white mannequin. She looked again and then realized that this was no department store dummy at all. It was the severed body of a woman. With a sharp intake of breath and a stifled scream, she took her daughter away from the gruesome site and ran to a nearby house. Sobbing, she telephoned the police. The call was answered by officers Frank Perkins and Wilfits Gerald who arrived within minutes. When they found the naked body of a woman who had been cut in half, they immediately called for assistance. The dead woman it was noted seemed to have been posed. She was lying on her back, with her arms raised over her shoulders and her legs spread in an obscene imitation of seductiveness. Cuts and abrasions covered her body and her mouth had been slashed so savagely that her smile extended grotesquely from ear to ear. There were rope marks on her wrists, ankles and neck and investigators later surmised that she had been tied down and tortured for several days. Worst of all was the fact that she had been sliced cleanly in two, just above the waist. It was clear that she had been killed somewhere else and then dumped in the vacant lot overnight. There was no blood on her body and none on the ground where she had been left. The killer had washed her off before bringing her to the dump site. The horrible nature of the case made it a top priority for the LAPD. Captain John Donahue assigned his senior detectives to the case, Detective Sergeant Harry Hansen and his partner Finis Brown. He also added Herman Willis, a bright young cop from the Metro Division, to help follow up on the leads that were sure to come in. By the time the detectives were contacted and could get to the scene, it was swarming with reporters, photographers and a crowd of curiosity seekers. Hansen was furious that bystanders and even careless police personnel were trampling the crime scene. Evidence was being destroyed, he knew, and he immediately cleared the scene. Then, while he and his partners examined the scene, the body of the woman was taken to the Los Angeles County morgue. Her fingerprints were lifted, and with the help of the assistant managing editor of the Los Angeles Examiner, the prints were sent to the FBI in Washington using the newspaper's sound photo equipment. The newspaper man had of course asked for information in exchange for the use of the equipment. Meanwhile, an examination of the corpse was started at the coroner's office. It began to detail an incredible and horrifying variety of wounds to the young woman's body, although the official cause of death was hemorrhage and shock due to concussion of the brain and lacerations of the face. An autopsy revealed multiple lacerations to the face and head, along with the severing of the victim's body.  There was no sperm present on the body and most of the damage appeared to have been done after she was dead. The coroner also noted that her stomach contents contained human feces. Even the hardened doctors and detectives were shocked at the state of the girl's corpse. The doctor also revealed to detectives Hanson, Brown and Willis an important piece of evidence and one that would have a huge bearing on the case as more of the victim's past was later revealed. He told the detectives, it's impossible to tell you if she was raped because traces of spermatozoa are negative and she did not have fully developed genitals. The area is shallow indicating that she did not have a complicated vaginal canal. According to the coroner, the young woman's vagina was almost childlike and normal sex for her would have been impossible. This information would have an important impact on what they would learn about the victim and Hanson immediately decided not to make this information public. In fact, only a few detectives working the case would know about it. Hanson's decision was the right one and he must have known how much newspaper coverage such a bizarre murder would get. Soon, tips, calls and false confessions would come pouring into police headquarters. More than 50 people would eventually confess to the killing. Shortly after receiving the fingerprints, the FBI had a match for the Los Angeles detectives. The victim of the brutal murder was Elizabeth Short, 22, who originally came from Massachusetts. During World War II, she had been a clerk at Camp Cook in California, which explained why her fingerprints were on file. Once the detectives had this information, they went to work finding out who knew Elizabeth Short, believing that this would lead them to her killer. What they discovered was a complex maze that led them into the shadowy side of the city in search of a woman called the Black Dahlia. Are you a member of the Darkness Syndicate? The Darkness Syndicate is a private membership where you receive commercial-free episodes of the Weird Darkness podcast and radio show. Behind the scenes, video updates about future projects and events I'm working on. You can share your own opinions on ideas to help me decide upon Weird Darkness Contests and events. You can hear audiobooks I'm narrating before even the publishers or authors get to hear them. You also receive bonus audio of other projects I'm working on outside of Weird Darkness. You get all of these benefits and more, starting at only $5 per month. Join the Weird Darkness Syndicate at weirddarkness.com slash syndicate. That's weirddarkness.com slash syndicate. Like all the other pretty girls before and since, Elizabeth Short, who preferred the name Beth, came to Hollywood hoping to make it big in the movie business. She was smart enough to know that looks weren't everything and that to break into films, she had to know the right people. So she spent most of her time trying to make new acquaintances that she could use to her advantage and to make sure that she was in the right night spots and clubs. Here she was convinced she would come to the attention of the important people in the business. Beth's pretty face got her noticed. She had done some modeling before coming to Hollywood and men couldn't keep their eyes off her. She created a character for herself, dressing completely in black which emphasized her pale beauty. In Hollywood, Beth roomed with a hopeful dancer who introduced her to Barbara Lee, a well-connected actress for Paramount. Lee took Beth to all of the right places, including the famous Hollywood canteen where Beth always hoped she'd be discovered. Beth loved to socialize, loved the Hollywood nightlife and loved to meet men. Despite the rumors, Beth was never promiscuous and she did not work as a prostitute. Considering the findings of the coroner, it isn't likely that sex with men involved normal penetration. Beautiful, lively and seductive, Beth was sometimes referred to as a tease, as her boyfriends never had any idea that romance could only go so far. One of the men who befriended Beth was Mark Hansen, a nightclub and theater owner who knew many important show business people. He eventually moved her into his house, along with a number of other young actresses who roomed there and who entertained guests at Hansen's clubs. On any given day, a visitor to Hansen's house could find a number of beautiful actresses and models setting themselves by the swimming pool. Beth soon became a part of this group, although her prospects for film work remained nonexistent. She didn't have much of an income and only seemed to eat and drink when others, usually her dates, were buying. She shared rooms with other people and borrowed money from her friends constantly, never paying it back. She never seemed to appreciate the hospitality given to her by others either, rarely contributing to where she was living and staying out most of the night and sleeping all day. She became known as a beautiful freeloader. Around the same time, the film The Blue Dahlia, starring Veronica Lake and Alan Ladd was released. Some of Beth's friends started calling her the Black Dahlia thanks to her dark hair and black lacy clothing, and the nickname stuck. It fit well with the mysterious and glamorous persona that Beth had already created. Tragically, it may have also led to her death. Although she is remembered today as the Black Dahlia, Elizabeth Short did not start out as a sexy vamp who haunted the nightclubs of Hollywood. She was born on July 29, 1924 in Hyde Park, Massachusetts. Her parents, Clio and Phoebe Short, moved the family to Medford, a few miles outside of Boston shortly after Elizabeth was born. Clio Short was a man ahead of his time, making a prosperous living designing and building miniature golf courses. Unfortunately, the depression caught up with him in 1929 and he fell on hard times. Without a second thought, he abandoned his wife and five daughters and faked his suicide. His empty car was discovered near a bridge, and the authorities believed that he had jumped into the river below. Phoebe was left to file for bankruptcy and to raise the girls by herself. She worked several jobs, including as a bookkeeper and a clerk in a bakery shop, but most of the money came from public assistance. One day she received a letter from Clio who was now living in California. He apologized for deserting his family and asked to come home. Phoebe refused his apology and would not allow him to come back. Beth, known as Betty to her family and friends, grew up to be a very pretty girl, looking older and acting more sophisticated than she really was. Everyone who knew her liked her and although she had serious problems with asthma, she was considered very bright and lively. She was also fascinated by the movies, which were her family's main source of affordable entertainment. She found an escape at the theater that she couldn't find in the day-to-day drudgery of ordinary life. While she was growing up, Beth remained in touch with her father once she knew he was actually alive. They wrote letters back and forth and when she was older, he offered to have her come out to California and stay with him until she was able to find a job. Beth had worked in restaurants and movie houses in the past but she knew that if she went to California, she wanted to be a star. She packed up and headed out west to her father. At that time, Clio was living in Vallejo and working at the Mayor Island Naval Base. Beth hadn't been staying with her father long before the relationship between them became strained. Clio began to launch into tirades about her laziness, poor housekeeping and dating habits. Eventually he threw her out and Beth was left to fend for herself. Undaunted, she went to Camp Cook and applied for a job as a cashier at the post exchange. It didn't take long for the service men to notice the new cashier and she won the title of Camp Cutie of Camp Cook in a beauty contest. They didn't realize that the sweet romantic girl was emotionally vulnerable though and desperate to marry a handsome service man, preferably a pilot. She made no secret of wanting a permanent relationship with one of the men with whom she constantly flirted. The word soon got around that Beth was not an easy girl and pressure for more than just handholding kept Beth at home most nights. Several encounters made her uncomfortable at Camp Cook and she left to stay with a girlfriend who lived near Santa Barbara. During this time, Beth had her only run in with the law. A group of friends that she was with got rowdy in a restaurant and the owners called the police. Since Beth was under age, she was booked and fingerprinted but never charged. A kind policewoman felt sorry for her and arranged for a trip back to Massachusetts. After spending some time at home, she came back to California, this time to Hollywood. At the Hollywood canteen, Beth met and fell in love with a pilot named Lieutenant Gordon Fickling. He was exactly what she was looking for and she began making plans to ensnare him in matrimony. Unfortunately though, her plans were cut short when Fickling was shipped out to Europe. Beth took a few modeling jobs but became discouraged and went back east. She spent the holidays in Medford and then went to Miami where she had relatives with whom she could live for a while. Beth began dating service men always with marriage as her goal. She fell in love again on New Year's Eve 1945 with a pilot, Major Matt Gordon. A commitment was apparently made between them after he was sent to India. Beth wrote to him constantly and Gordon remained in touch with her. As a pre-engagement gift, he gave Beth a gold wrist watch that was set with diamonds and spoke about her and their engagement to family and friends. Best of all, as far as Beth was concerned, he respected her wishes about waiting until their honeymoon to consummate their love. They get married and have a proper honeymoon, he promised her after he returned from overseas. What has to wonder how Beth planned to deal with the physical problems that they would encounter once the relationship turned sexual? But perhaps she was too caught up in the moment to worry about it at that time. Beth went back home to Massachusetts and got a job, dreaming of her October wedding. Her friends often commented on how happy she was and after the war ended in Europe, she became ecstatic about Gordon returning home. A short time later, she received a telegram from Gordon's mother. As soon as it arrived, Beth tore the message open, believing it was about plans for the upcoming wedding. Instead, Mrs. Gordon had written received word War Department. Matt killed in plane crash on way home from India. Our deepest sympathy is with you. Pray it isn't true. Tragically, it was true, and Gordon's death left Beth a little unbalanced. After a period of mourning during which Beth had told people that she and Matt had been married and that their baby had died at birth, she began to pick up the pieces of her old life and started contacting her Hollywood friends. One of those friends was former boyfriend Gordon Fickling, whom Beth saw as a possible replacement for her dead fiance. They began to write to one another and then got together briefly in Chicago when Fickling was in town for a couple of days. Soon, Beth was in love with him again. She agreed to come to Long Beach and be with him, happy and excited once again. A short time later, Beth was back in California. Her excitement over the new relationship didn't last long. She had to stay in a hotel that was miles from the base where Fickling was stationed and he constantly pressured Beth for sex. She had no intention of giving herself to a man except in marriage, she told a friend, and Fickling had no intention of making such a commitment. She began dating other men and when Fickling found out, he ended their relationship. In December 1946, Beth took up temporary residence in San Diego with a young woman named Dorothy French. She was a countergirl at the Aztec Theater, which stayed open all night and after an evening show, she found Beth asleep in one of the seats. Beth told her that she'd left Hollywood because work was hard to find due to the actor's strikes that were going on. Dorothy felt sorry for her and offered her a place to stay at her mother's home. The invitation was intended to last for only a few days, but Beth ended up sleeping on the French's couch for more than a month. As usual, she did nothing to contribute to the household and she continued her late night partying and dating. One of the men she dated was Robert Red Manley, a salesman from Los Angeles with a pregnant young wife at home. He admitted being attracted to Beth but later claimed that he never slept with her. They saw each other on and off for a few weeks and then Beth asked him for a ride back to Hollywood. He agreed and on January 8th picked her up from the French house and paid for a motel room for her that night. They went out together to a couple of different night spots and returned back to the hotel. He slept on the bed while Beth, complaining that she didn't feel well, slept in a chair. Red had a morning appointment but came back to pick her up around noon. She told him that she was going back home to Boston, but first she was going to meet her married sister at the Biltmore Hotel in Hollywood. Manley drove her back to Los Angeles. He had an appointment at the home of his employer that evening so he didn't wait around for Beth's sister to arrive. Manley said Beth was making phone calls in the hotel lobby when he saw her last, becoming, along with the hotel employees, the last person to see her alive. As far as the police could discover, only her killer ever saw her after that. She vanished for six days from the Biltmore before her body was found in the empty lot. Well, hello there. It's Santa and my big night is getting closer by the day. You know, I love milk and cookies when I visit your home each year. Well, the milk can get warm while waiting for me to arrive and a warm toddy is not the best thing to drink if you plan on staying alert and flying around the world. So this year, I'm asking that you instead leave me a plate of cookies at a nice hot thermos or mug of weird dark roast coffee. It actually tastes like Christmas. It has a hint of cocoa and caramel, and I've been drinking a lot of it recently to wake me up early in the morning to work on toys and take care of the reindeer. So this year, leave Santa a mug or thermos of weird dark roast coffee. Tell your parents they can find it right now at weirddarkness.com slash coffee. That's weirddarkness.com slash coffee. The investigation into the Black Dahlia's murder was the highest-profile crime in Hollywood of the 1940s. The police were constantly harassed by the newspapers and the public for results. Hundreds of suspects were questioned. Because it was considered a sex crime, the usual suspects and perverts were rounded up and interrogated. Beth's friends and acquaintances were questioned as the detectives tried to reconstruct her final days and hours. Every lead that seemed hopeful ended up leading nowhere and the cops were further hampered by the lunatics whose crazed confessions were still pouring in. As the investigators traced Beth's activities, they discovered their strongest suspect, Robert Manley. He became the chief target of the investigation. The LAPD put him through grueling interrogations and even administered two different polygraph tests, both of which he passed. He was released a couple of days later, but the strain on him was so great that he later suffered a nervous breakdown. While the police worked frantically, Beth's mother made the trip to Los Angeles to claim her daughter's body. Her father, who had not seen her since 1943, refused to identify her. Sadly, Phoebe Short had learned of her daughter's death from a newspaper reporter who had called her, using the pretext that Beth had won a beauty contest and the paper wanted some background information about her. Once he had gleaned as much information as he could, he informed her that Beth had actually been murdered. A few days after Beth's body was found, a mysterious package appeared at the offices of the Los Angeles Examiner. An envelope contained a note that had been cut and pasted from newspaper letters. It read, Here is the Dahlia's belongings, letter to follow. Inside the small package was Beth's Social Security card, birth certificate, photographs of Beth with various service men, business cards and claim checks for suitcases that she'd left at the bus depot. Another item was an address book that belonged to club owner Mark Hansen. The address book had several pages torn out. The police attempted to lift fingerprints off the items but found that all of them had been washed in gasoline to remove any trace of evidence. The detectives then began the overwhelming task of tracking down everyone in the address book and while Mark Hansen and a few others were singled out for interrogation, nothing ever came of it. In addition, the promised letter to follow never arrived. All of the leads in the Black Dahlia case came to dead ends and the investigation fizzled and then came to a halt. The murder remains unsolved today, although it is possible that the killer may have actually been identified by one investigator in the case. The possible killer first came to the attention of John St. John, a respected investigator for the LAPD who eventually took over the Dahlia case. St. John had worked many of the city's most notorious murders and was the basis of the book and television series Jigsaw John. He'd been in charge of the Dahlia case for about a year when a confidential informant came to him with a tape recording that implicated a suspect in the murder. The suspect had also shown the informant some photos and personal items that he'd claimed had belonged to the Black Dahlia. The suspect turned out to be a tall, thin man with a pronounced limp who went by the name of Arnold Smith. On the recording, Smith claimed that a character named Al Morrison was the violent sexual deviant who had killed and mutilated Beth Short. St. John suspected that Arnold Smith and Al Morrison were actually the same person. The tape was a chilling and detailed account of how Beth had come to Al Morrison's Hollywood hotel room because she didn't have anywhere else to stay.  Here he assaulted her and prevented her from escaping by beating her into submission. Even though Beth fought back, he was able to overwhelm her with his superior strength. While she was on the floor, Morrison stated that he planned to sodomize her and Beth began struggling once again. This time he hit her so hard that she passed out. The tape then went on to describe how Morrison had gotten a paring knife, a large butcher knife and some rope and had returned to the room to find Beth conscious again.  While she was naked and bound, he began jabbing her over and over again with the knives, cutting and slashing her.  By this time, the girl was dead. Morrison then laid boards across the bathtub and cut Beth in half with a butcher knife, letting the blood drain into the tub. He wrapped the two pieces of the body in a tablecloth and shower curtains and put it into the trunk of his car. From there, he drove to the vacant lot and left the body to be found later that morning. St. John discovered that this same suspect, Al Morrison, had also come to the attention of Detective Joel Lesnick of the Sheriff's Department for another brutal murder. Lesnick had learned that both Al Morrison and Arnold Smith were aliases of a man named Jack Anderson Wilson, a tall and lanky alcoholic with a crippled leg and a record for sex offenses and robbery. Lesnick guessed that, as the years went on, Smith's ego drew him closer, not to confessing but wanting to tell someone in a roundabout way what he got away with, primarily through luck. After hearing the record of events on the tape recordings, St. John became determined to track down Arnold Smith. He checked into the story of Al Morrison, the alleged violent pervert, and could find no proof that he existed, thus confirming the idea that Smith, Jack Wilson, was actually the killer. St. John began to leave no stone unturned in his pursuit to link Jack Wilson to Elizabeth Short. In the midst of the investigation, word came that the press had gotten wind of the fact that a new suspect had emerged in the Dahlia case. Even after all of the years, at this point the mid-1980s that had passed, interest in the case was still strong. At this point St. John realized that it was imperative that he moved quickly before Wilson, Smith, became spooked. The informant did not know where Smith lived but he left messages for him in a café. Several messages were left but Smith never returned to them, possibly because he found out about the police surveillance of the restaurant. Finally, the informant received a reply and a meeting was set with Smith. The police made plans to pick him up for questioning. Unfortunately, just before the meeting took place, Smith passed out while smoking in bed at the Holland Hotel where he was staying. He was burned to death and the flames destroyed the photos and belongings that supposedly belonged to Beth Short and possibly all hope that her murder would ever be solved. A short time after Wilson's body was released to the county for cremation, the Los Angeles District Attorney's Office was present with a file on the matter. The prosecutor's office summed up the case by saying, The case cannot be officially closed due to the death of the individual considered a suspect. While the documentation appears to link this individual with the homicide of Elizabeth Short, his death however precludes the opportunity of an interview to obtain from him the corroboration. Therefore, any conclusion as to his criminal involvement is circumstantial and unfortunately the suspect cannot be charged or tried due to his demise. However, despite this inconclusiveness, the circumstantial evidence is of such a nature that were this suspect alive, an intense inquiry would be recommended. And depending upon the outcome of such an inquiry, it is conceivable that Jack Wilson might have been charged as a suspect in the murder of Elizabeth Short, also known as the Black Dahlia. Since the time of her death in 1947, many books have been written and many theories have been expressed about who killed Elizabeth Short. But no matter the number of theories, books, and documentaries on the case, to this date it remains unsolved. No one has ever been charged with her murder, and as far as we know, her death has never been avenged. She remains an elusive mystery from the dark side of Hollywood and the even darker side of the American landscape. Perhaps this is why her ghost still walks at the Biltmore Hotel and her specter still looms over these shadowy streets of Hollywood. Even today, an occasional man who stays at the Biltmore encounters the spectral image of a woman in a black dress, sometimes in the lobby, waiting in the corridors or even riding to the sixth floor on the elevator. What is she trying to tell us? Are there still clues to the identity of her killer that have never been found? Or does the Black Dahlia simply wish to continue the mystery that was created more than 60 years ago? Or sadly, Beth found the fame and death that she never managed to achieve in life. Thanks for listening. If you liked the podcast, please share a link to this episode and recommend Weird Darkness to your friends, family and co-workers who love the paranormal, horror stories or true crime like you do. Every time you share a link to the podcast, it helps spread the word about it, growing our Weirdo family and also helps get the word out about resources available for those who suffer from depression, so please share the podcast with others. Do you have a dark tale to tell of your own? Factor fiction, click on Tell Your Story at WeirdDarkness.com and I might use it in a future episode. Who Killed the Black Dahlia was written by Troy Taylor from his book Bloody Hollywood, which I have linked to in the show notes if you would like to see the rest of the book. Weird Darkness theme by Alibi Music. Weird Darkness is a registered trademark. And now that we are coming out of the dark, I will leave you with a little light. First John 4, verses 18 and 19, there is no fear in love, but perfect love drives out fear because fear has to do with punishment. The one who fears is not made perfect in love. We love because he first loved us. And a final thought, I began learning long ago that those who are happiest are those who do the most for others. Booker T. Washington. I am Darren Marlar. Thanks for joining me in the Weird Darkness.