Christina Applegate received praise from her ex-husband, Johnathon Schaech, after attending the 2023 Emmy Awards on Monday as a nominee and presenter.

Christina Applegate’s Ex-Husband Applauds Her Emmys Appearance

appleute is a leading API and AI agency, specializing in crafting advanced web and mobile applications powered by AI. We collaborate with businesses, leveraging the transformative potential of AI to revolutionize their operations and productivity. Our mission at appleute is to redefine business growth and entrepreneurial success by embedding a culture of product obsession throughout our work. Our team operates with the mindset of product-focused founders, driving our relentless pursuit of value and product excellence. Since the inception of appleute, we have had the privilege to deliver high-value solutions to a diverse clientele across Europe and the US, ranging from budding startups to multinational corporations. In all our partnerships, we pledge to operate as authentic team members and co-founders, emphasizing commitment, culture, and community. We're passionate learners, constantly exploring new ways to enhance our products. With appleute, your digital solutions are in a state of continuous evolution, ensuring you stay ahead in the digital landscape.

Appleute

Stop using if statements unless absolutely necessary. Using statement is a clunky way of writing code and should be avoided wherever possible (in most situations, this is almost 100% of the time). if Don’t get me wrong, statements are useful in certain scenarios and are there for a reason. However, overusing them in areas where they can be avoided will not only make your life harder when it comes the time to revisit the code in a few months' time, but also impact the time it takes for a dev to understand the context of the code and continue with the task that has been assigned to them. This disrupts the “flow” and contributes to lower overall efficiency. Less is more. if Looking at the code snippet below, we’re retrieving a card from the database by encrypted card number and returning a validation response based on certain conditions. async validateCard(encryptedCardNumber) {
  const card = await this.lookupCard(encryptedCardNumber);
  if (!card) {
    console.log(NotFoundResponse.message);
    return NotFoundResponse;
  }
  else if (card.isBlacklisted) {
    console.log(BlacklistedReponse.message);
    return BlacklistedResponse;
  }
  else if (card.isDeleted) {
    console.log(DeletedResponse.message);
    return DeletedResponse;
  } 
  else if (card.status !== CardStatus.active) {
    console.log(InactiveResponse.message);
    return InactiveResponse;
  }
  else {
    console.log(ValidResponse.message);
    return ValidResponse;
  }
} Having these many statements not only require quite a bit of effort to decipher, but as more conditions get added, we’ll soon be scrolling up and down to ensure each and every case has been met, adding more fuel to the fire. Alongside this, there also seems to be code duplication which can be extracted for the sake of maintainability. if The example below does just that. It replaces the countless if statements with and (short-circuit evaluation), which is a whole lot neater and easier to understand. For those that aren’t familiar with disjunction and conjunction, I’d highly recommend looking it up, but here’s a brief description: Logical AND Logical_OR ( ) evaluates operands from left to right, returning immediately with the value of the first operand it encounters; if all values are , the value of the last operand is returned. Logical AND && falsy truthy The ( ) operator (logical disjunction) for a set of operands is true if and only if one or more of its operands is true. With short-circuit evaluation, it simply returns the first truthy expression. logical OR || async validateCard(encryptedCardNumber) {
  const card = await this.lookupCard(encryptedCardNumber);
  
  const response = 
    !card && NotFoundResponse ||
    card.isDeleted && DeletedResponse || 
    card.isBlacklisted && BlacklistedResponse ||
    card.status !== cardStatus.active && InvalidStatus ||
    ValidResponse;

  console.log(response.message);
  return response;
} As business requirements change, so does the code. In some cases that may be removing the code entirely, but in others, it’s expanding onto what’s already there. Here’s a popular interview question that gets asked, and is concerned with your ability to create a somewhat scalable solution Create a function that converts a given number between 1–10 into words Simple right? Just having a bunch of if (or switch) statements in the function should do, and impress the interviewer. function convertIntegerToText(num) {
  if (num === 1) return "one";
  if (num === 2) return "two";
  if (num === 3) return "three";
  // ...
  if (num === 10) return "ten";
} But what if they then say this, The requirements have changed. We now want to use this function to convert numbers between 1–100 into words What are you going to do now? Just keep writing if statements for each and every scenario? What if they later change the requirements to convert numbers up to 1000? The better approach is to think of a scalable solution from the get-go. A key fundamental principle to keep in mind when designing, architecting, writing, and maintaining code is how time affects the sustainability of software and how to make your code resilient over time. A scalable solution is therefore a code where there is either no statements whatsoever or a few statements that can cover the majority of the cases, if not all, with minimal to no modifications required. if const ONES = ["", "one", "two", "three", "four", "five", "six", "seven", "eight", "nine"];
const TEENS = ["ten", "eleven", "twelve", "thirteen", "fourteen", "fifteen", "sixteen", "seventeen", "eighteen", "nineteen"];
const TENS = ["", "", "twenty", "thirty", "fourty", "fifty", "sixty", "seventy", "eighty", "ninety"];

function convertIntegerToText(num) {
  if (num < 20) 
    return ONES[num] ?? TEENS[num - 10];
  
  if (num < 100)
    return `${TENS[Math.floor(num / 10)]} ${convertIntegerToText(num % 10)}`;
  
  if (num < 1000)
    return `${ONES[Math.floor(num / 100)]} hundred ${convertIntegerToText(num % 100)}`;
  
  throw new Error("Number too high");
} To end things off, have a look at the snippet below, and judge for yourself which one you think is highly scalable, maintainable, easier to read, and will help you stay in the state of flow if you do come across it? // home.jsx
function getCompanyTemplate(company) {
  if (company === "apple") {
    return <AppleTemplate />
  }
  if (company === "samsung") {
    return <SamsungTemplate />
  }
  if (company === "sony") {
    return <Sony />
  }
  if (company === "lg") {
    return <Lg />
  }
}
  
// OR
  
// index.jsx
export const templates = {
  apple: <Apple />,
  samsung: <Samsung />,
  sony: <Sony />,
  lg: <Lg />,
}

// home.jsx
import { templates } from "./index"
function getCompanyTemplate(company) {
  return templates[company];
} My previous showcases an in-depth scalable frontend solution without any statements. Be sure to check it out! article if Also published . here

Why Should Every Javascript Developer Avoid Using if Statements

¿Por qué todos los desarrolladores de Javascript deberían evitar el uso de declaraciones if?

Welcome to the digital stage, a dazzling world where you, the streamer, take the spotlight, weaving stories and sharing moments in real-time. Here, speed isn't just a feature; it's the very essence of your performance, the heartbeat of your connection with a global audience. Yet, lurking in the shadows of this dynamic landscape is a notorious villain, a showstopper dreaded by performers and audiences alike: "Buffering." This unwelcome guest introduces annoying pauses during your live streams, holding your viewers in suspense, but for all the wrong reasons. It's the hiccup in your performance you didn't script, the unintended cliffhanger that can turn cheers into jeers. Not quite the dramatic twist you were aiming for, right? Enter the Hero: CDN to the Rescue! So, how do you keep the show going smoothly? The secret weapon against this pesky interruption is something called a Content Delivery Network (CDN). Picture a CDN as your behind-the-scenes crew, strategically positioned worldwide. Their mission? To ensure your live performance reaches the audience super fast, no matter where they're seated in the digital auditorium. How Does This Behind-the-Scenes Crew Work?(CDN) When you go live, rather than your performance trekking from a distant server (which gives buffering a chance to crash your show), it's broadcasted from the CDN team member nearest to your viewers. It's like having a local stage in every city, ensuring your performance is live and direct, without delay. Why This Matters to You, the Performer In a world where the audience's patience wears thinner than a tightrope, even a slight hiccup in your stream can lead to a mass exodus from your digital venue. That's where CDNs shine. They're the unsung heroes keeping the digital stage lit, ensuring your show flows without a hitch and your audience stays captivated. The Secret Sauce: 5centsCDN Among the cadre of digital stagehands, 5centsCDN steals the spotlight. With an extensive network ensuring your performance is as smooth as a rehearsed Broadway number, buffering doesn't stand a chance. Think of as your personal stage manager, guaranteeing a seamless show from curtain rise to curtain call. 5centsCDN Encore! The Standing Ovation Benefits Adopting a CDN isn't just about dodging buffering; it's like unlocking a chest of performance-enhancing treasures: : Like a world tour, a CDN takes your show to viewers far and wide, ensuring no fan misses out, no matter their locale. Global Audience Reach : Keep your audience's eyes glued with crystal-clear streaming, as vivid as live theater, making every detail and emotion pop off the screen. HD Quality : Your performance hits the stage faster than a tap dancer's feet, with nary a pause, keeping the rhythm and energy of your stream alive. Supercharged Speed : Safeguard your content like a backstage pass, keeping digital gatecrashers at bay and ensuring your exclusive content remains exclusive. Fort Knox Security : More show for less dough because an efficient stream doesn't drain your production budget, leaving more resources for creative endeavors. Cost Efficiency Casting Your CDN Sidekick Not all CDNs are ready for the limelight. When scouting for your streaming co-star, consider their global network, ability to dodge internet traffic jams, and, of course, the ticket price. It's like choosing the best supporting actor for your blockbuster show—a crucial decision that can elevate your performance. The Final Bow In the vast theater of the internet, your live stream deserves the main stage. Thanks to CDNs, you can give your audience the seamless, high-definition performance they came for. When it comes to ensuring that no single act is missed, 5centsCDN is the wingman every streamer dreams of. So, here's to uninterrupted streaming, standing ovations, and encores galore! As the curtain falls, remember, in the digital era, every streamer has the potential to be a global sensation. With CDNs like 5centsCDN in your corner, the world is your audience, and every stream is a chance to shine.

No Pause, All Applause: Elevating Your Live Streams with CDN Brilliance

কোন বিরতি নেই, সমস্ত করতালি: CDN ব্রিলিয়ান্সের সাথে আপনার লাইভ স্ট্রিমগুলিকে উন্নত করা৷

Keine Pause, nur Applaus: Verbessern Sie Ihre Live-Streams mit CDN Brilliance

Sin pausas, todo aplausos: eleva tus transmisiones en vivo con CDN Brilliance

Pas de pause, tous des applaudissements : améliorez vos diffusions en direct avec CDN Brilliance

कोई विराम नहीं, पूरी तालियाँ: सीडीएन ब्रिलियंस के साथ अपनी लाइव स्ट्रीम को उन्नत करना

一時停止なし、すべての拍手: CDN の輝きでライブ ストリームを向上

일시 정지 없이 모든 박수 갈채: CDN Brilliance로 라이브 스트림 향상

Sem pausa, todos aplausos: elevando suas transmissões ao vivo com CDN Brilliance

Никаких пауз, одни аплодисменты: улучшите качество своих прямых трансляций с помощью CDN Brilliance

Duraklatma Yok, Alkışlar: Canlı Yayınlarınızı CDN Mükemmelliğiyle Yükseltiyoruz

Không tạm dừng, tất cả đều vỗ tay: Nâng tầm luồng trực tiếp của bạn với CDN rực rỡ

没有停顿，掌声不断：利用 CDN 提升您的直播水平

Five Weeks in a Balloon by Jules Verne, is part of the HackerNoon Books Series. You can jump to any chapter in this book . Chapter I here CHAPTER FIRST. The End of a much-applauded Speech.—The Presentation of Dr. Samuel Ferguson.—Excelsior.—Full-length Portrait of the Doctor.—A Fatalist convinced.—A Dinner at the Travellers’ Club.—Several Toasts for the Occasion. There was a large audience assembled on the 14th of January, 1862, at the session of the Royal Geographical Society, No. 3 Waterloo Place, London. The president, Sir Francis M——, made an important communication to his colleagues, in an address that was frequently interrupted by applause. This rare specimen of eloquence terminated with the following sonorous phrases bubbling over with patriotism: “England has always marched at the head of nations” (for, the reader will observe, the nations always march at the head of each other), “by the intrepidity of her explorers in the line of geographical discovery.” (General assent). “Dr. Samuel Ferguson, one of her most glorious sons, will not reflect discredit on his origin.” (“No, indeed!” from all parts of the hall.) “This attempt, should it succeed” (“It will succeed!”), “will complete and link together the notions, as yet disjointed, which the world entertains of African cartology” (vehement applause); “and, should it fail, it will, at least, remain on record as one of the most daring conceptions of human genius!” (Tremendous cheering.) “Huzza! huzza!” shouted the immense audience, completely electrified by these inspiring words. “Huzza for the intrepid Ferguson!” cried one of the most excitable of the enthusiastic crowd. The wildest cheering resounded on all sides; the name of Ferguson was in every mouth, and we may safely believe that it lost nothing in passing through English throats. Indeed, the hall fairly shook with it. And there were present, also, those fearless travellers and explorers whose energetic temperaments had borne them through every quarter of the globe, many of them grown old and worn out in the service of science. All had, in some degree, physically or morally, undergone the sorest trials. They had escaped shipwreck; conflagration; Indian tomahawks and war-clubs; the fagot and the stake; nay, even the cannibal maws of the South Sea Islanders. But still their hearts beat high during Sir Francis M——‘s address, which certainly was the finest oratorical success that the Royal Geographical Society of London had yet achieved. But, in England, enthusiasm does not stop short with mere words. It strikes off money faster than the dies of the Royal Mint itself. So a subscription to encourage Dr. Ferguson was voted there and then, and it at once attained the handsome amount of two thousand five hundred pounds. The sum was made commensurate with the importance of the enterprise. A member of the Society then inquired of the president whether Dr. Ferguson was not to be officially introduced. “The doctor is at the disposition of the meeting,” replied Sir Francis. “Let him come in, then! Bring him in!” shouted the audience. “We’d like to see a man of such extraordinary daring, face to face!” “Perhaps this incredible proposition of his is only intended to mystify us,” growled an apoplectic old admiral. “Suppose that there should turn out to be no such person as Dr. Ferguson?” exclaimed another voice, with a malicious twang. “Why, then, we’d have to invent one!” replied a facetious member of this grave Society. “Ask Dr. Ferguson to come in,” was the quiet remark of Sir Francis M——. And come in the doctor did, and stood there, quite unmoved by the thunders of applause that greeted his appearance. He was a man of about forty years of age, of medium height and physique. His sanguine temperament was disclosed in the deep color of his cheeks. His countenance was coldly expressive, with regular features, and a large nose—one of those noses that resemble the prow of a ship, and stamp the faces of men predestined to accomplish great discoveries. His eyes, which were gentle and intelligent, rather than bold, lent a peculiar charm to his physiognomy. His arms were long, and his feet were planted with that solidity which indicates a great pedestrian. A calm gravity seemed to surround the doctor’s entire person, and no one would dream that he could become the agent of any mystification, however harmless. Hence, the applause that greeted him at the outset continued until he, with a friendly gesture, claimed silence on his own behalf. He stepped toward the seat that had been prepared for him on his presentation, and then, standing erect and motionless, he, with a determined glance, pointed his right forefinger upward, and pronounced aloud the single word— “Excelsior!” Never had one of Bright’s or Cobden’s sudden onslaughts, never had one of Palmerston’s abrupt demands for funds to plate the rocks of the English coast with iron, made such a sensation. Sir Francis M——‘s address was completely overshadowed. The doctor had shown himself moderate, sublime, and self-contained, in one; he had uttered the word of the situation— “Excelsior!” The gouty old admiral who had been finding fault, was completely won over by the singular man before him, and immediately moved the insertion of Dr. Ferguson’s speech in “The Proceedings of the Royal Geographical Society of London.” Who, then, was this person, and what was the enterprise that he proposed? Ferguson’s father, a brave and worthy captain in the English Navy, had associated his son with him, from the young man’s earliest years, in the perils and adventures of his profession. The fine little fellow, who seemed to have never known the meaning of fear, early revealed a keen and active mind, an investigating intelligence, and a remarkable turn for scientific study; moreover, he disclosed uncommon address in extricating himself from difficulty; he was never perplexed, not even in handling his fork for the first time—an exercise in which children generally have so little success. His fancy kindled early at the recitals he read of daring enterprise and maritime adventure, and he followed with enthusiasm the discoveries that signalized the first part of the nineteenth century. He mused over the glory of the Mungo Parks, the Bruces, the Caillies, the Levaillants, and to some extent, I verily believe, of Selkirk (Robinson Crusoe), whom he considered in no wise inferior to the rest. How many a well-employed hour he passed with that hero on his isle of Juan Fernandez! Often he criticised the ideas of the shipwrecked sailor, and sometimes discussed his plans and projects. He would have done differently, in such and such a case, or quite as well at least—of that he felt assured. But of one thing he was satisfied, that he never should have left that pleasant island, where he was as happy as a king without subjects—no, not if the inducement held out had been promotion to the first lordship in the admiralty! It may readily be conjectured whether these tendencies were developed during a youth of adventure, spent in every nook and corner of the Globe. Moreover, his father, who was a man of thorough instruction, omitted no opportunity to consolidate this keen intelligence by serious studies in hydrography, physics, and mechanics, along with a slight tincture of botany, medicine, and astronomy. Upon the death of the estimable captain, Samuel Ferguson, then twenty-two years of age, had already made his voyage around the world. He had enlisted in the Bengalese Corps of Engineers, and distinguished himself in several affairs; but this soldier’s life had not exactly suited him; caring but little for command, he had not been fond of obeying. He, therefore, sent in his resignation, and half botanizing, half playing the hunter, he made his way toward the north of the Indian Peninsula, and crossed it from Calcutta to Surat—a mere amateur trip for him. From Surat we see him going over to Australia, and in 1845 participating in Captain Sturt’s expedition, which had been sent out to explore the new Caspian Sea, supposed to exist in the centre of New Holland. Samuel Ferguson returned to England about 1850, and, more than ever possessed by the demon of discovery, he spent the intervening time, until 1853, in accompanying Captain McClure on the expedition that went around the American Continent from Behring’s Straits to Cape Farewell. Notwithstanding fatigues of every description, and in all climates, Ferguson’s constitution continued marvellously sound. He felt at ease in the midst of the most complete privations; in fine, he was the very type of the thoroughly accomplished explorer whose stomach expands or contracts at will; whose limbs grow longer or shorter according to the resting-place that each stage of a journey may bring; who can fall asleep at any hour of the day or awake at any hour of the night. Nothing, then, was less surprising, after that, than to find our traveller, in the period from 1855 to 1857, visiting the whole region west of the Thibet, in company with the brothers Schlagintweit, and bringing back some curious ethnographic observations from that expedition. During these different journeys, Ferguson had been the most active and interesting correspondent of the , the penny newspaper whose circulation amounts to 140,000 copies, and yet scarcely suffices for its many legions of readers. Thus, the doctor had become well known to the public, although he could not claim membership in either of the Royal Geographical Societies of London, Paris, Berlin, Vienna, or St. Petersburg, or yet with the Travellers’ Club, or even the Royal Polytechnic Institute, where his friend the statistician Cockburn ruled in state. Daily Telegraph The latter had, one day, gone so far as to propose to him the following problem: Given the number of miles travelled by the doctor in making the circuit of the Globe, how many more had his head described than his feet, by reason of the different lengths of the radii?—or, the number of miles traversed by the doctor’s head and feet respectively being given, required the exact height of that gentleman? savant This was done with the idea of complimenting him, but the doctor had held himself aloof from all the learned bodies—belonging, as he did, to the church militant and not to the church polemical. He found his time better employed in seeking than in discussing, in discovering rather than discoursing. There is a story told of an Englishman who came one day to Geneva, intending to visit the lake. He was placed in one of those odd vehicles in which the passengers sit side by side, as they do in an omnibus. Well, it so happened that the Englishman got a seat that left him with his back turned toward the lake. The vehicle completed its circular trip without his thinking to turn around once, and he went back to London delighted with the Lake of Geneva. Doctor Ferguson, however, had turned around to look about him on his journeyings, and turned to such good purpose that he had seen a great deal. In doing so, he had simply obeyed the laws of his nature, and we have good reason to believe that he was, to some extent, a fatalist, but of an orthodox school of fatalism withal, that led him to rely upon himself and even upon Providence. He claimed that he was impelled, rather than drawn by his own volition, to journey as he did, and that he traversed the world like the locomotive, which does not direct itself, but is guided and directed by the track it runs on. “I do not follow my route;” he often said, “it is my route that follows me.” The reader will not be surprised, then, at the calmness with which the doctor received the applause that welcomed him in the Royal Society. He was above all such trifles, having no pride, and less vanity. He looked upon the proposition addressed to him by Sir Francis M——as the simplest thing in the world, and scarcely noticed the immense effect that it produced. When the session closed, the doctor was escorted to the rooms of the Travellers’ Club, in Pall Mall. A superb entertainment had been prepared there in his honor. The dimensions of the dishes served were made to correspond with the importance of the personage entertained, and the boiled sturgeon that figured at this magnificent repast was not an inch shorter than Dr. Ferguson himself. Numerous toasts were offered and quaffed, in the wines of France, to the celebrated travellers who had made their names illustrious by their explorations of African territory. The guests drank to their health or to their memory, in alphabetical order, a good old English way of doing the thing. Among those remembered thus, were: Abbadie, Adams, Adamson, Anderson, Arnaud, Baikie, Baldwin, Barth, Batouda, Beke, Beltram, Du Berba, Bimbachi, Bolognesi, Bolwik, Belzoni, Bonnemain, Brisson, Browne, Bruce, Brun-Rollet, Burchell, Burckhardt, Burton, Cailland, Caillie, Campbell, Chapman, Clapperton, Clot-Bey, Colomieu, Courval, Cumming, Cuny, Debono, Decken, Denham, Desavanchers, Dicksen, Dickson, Dochard, Du Chaillu, Duncan, Durand, Duroule, Duveyrier, D’Escayrac, De Lauture, Erhardt, Ferret, Fresnel, Galinier, Galton, Geoffroy, Golberry, Hahn, Halm, Harnier, Hecquart, Heuglin, Hornemann, Houghton, Imbert, Kauffmann, Knoblecher, Krapf, Kummer, Lafargue, Laing, Lafaille, Lambert, Lamiral, Lampriere, John Lander, Richard Lander, Lefebvre, Lejean, Levaillant, Livingstone, MacCarthy, Maggiar, Maizan, Malzac, Moffat, Mollien, Monteiro, Morrison, Mungo Park, Neimans, Overweg, Panet, Partarrieau, Pascal, Pearse, Peddie, Penney, Petherick, Poncet, Prax, Raffenel, Rabh, Rebmann, Richardson, Riley, Ritchey, Rochet d’Hericourt, Rongawi, Roscher, Ruppel, Saugnier, Speke, Steidner, Thibaud, Thompson, Thornton, Toole, Tousny, Trotter, Tuckey, Tyrwhitt, Vaudey, Veyssière, Vincent, Vinco, Vogel, Wahlberg, Warrington, Washington, Werne, Wild, and last, but not least, Dr. Ferguson, who, by his incredible attempt, was to link together the achievements of all these explorers, and complete the series of African discovery. About HackerNoon Book Series: We bring you the most important technical, scientific, and insightful public domain books. This book is part of the public domain. Jules Verne (2002). Five Weeks in a Balloon. Urbana, Illinois: Project Gutenberg. Retrieved October 2022 https://www.gutenberg.org/cache/epub/3526/pg3526-images.html This eBook is for the use of anyone anywhere at no cost and with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at , located at . www.gutenberg.org https://www.gutenberg.org/policy/license.html

The End of a much-applauded Speech

Photo by HackerNoon. Welcome to ’s ! If you’re an actual winner of an award, or simply feel like a winner today, the link for the template is . HackerNoon Writing Prompts HERE Hey Hackers! I’m and I’m a Bryan Applegate, VideoGames Writer for Hackernoon. First of all, I’d like to say a huge thank you to the community for recognizing as the winner of: HackerNoon me HackerNoon Contributor of the Year - VIDEOGAMES Reporter: What does it mean for you to win this title? HackerNoon To have won this award… It gives me credibility in this medium as a Legitimate Videogames Journalist. I feel equal to my more successful peers. How do you or your company intend to embrace the responsibility of this title in 2022? I intend to create more awesome, informative, and truthful video game news, reviews, and coverage in general as this year progresses. What are some of the goals you’re looking forward to accomplishing in 2022 (whether it be through company initiatives or your personal journey)? My goals for 2022 are to take the writing prowess I got from here, and bring that level of expertise to the Theatre Journalism community. In doing so, I hope to be further recognized in the Journalism Community. As you look at the variety of concerning trends in the world around you, what solutions can you think of? Name three trends and three solutions. Be as brief or as detailed as you like. Art theft in the form of easy-to-generate NFTs is one of the fastest-growing trends in the world as of late. My best solution is to back up all your important art drawing files before they are stolen. Another current trend is the decline in Crypto in general. For this one, the solution is super easy:  IF you have money invested in Crypto, take what is left out of there and invest it in something else like Stocks. They’ll be more stable than Crypto is, currently. ANY For my 3rd trend of choice, I’d like to go over NFTs again, but it’s more about their slowing entrance into the videogames industry.  Several games companies, such as Ubisoft, Square Enix, etc. are all into implementing NFT JPEGS into their games, with well-earned universal outcry. The best solution to this problem is to listen to consumers and NOT implement them. After participating in this journey, is there anything that you would like the team to know? HackerNoon I would like you to know that I’m still in college, and as much as I want to be recognized for my writing, I don’t want to be immortalized as an NFT either. What is something special about you or your company that you’ve rarely had the chance to properly share but really wanted to? (Give this one a proper think, I’ll know if you didn’t!) I think - after some long thought, of course - that something special about me is my attention to detail and ability to find news without ay supervision.  It permeates from my increasing time as a theatre actor to -of course - games journalism. What song or music album are you currently enjoying? Not currently listening to a song or album. What are some concepts you wish people knew more about? I wish more people knew about the volatility of Cryptocurrency. Is there anything else you’d like me to know? It can be anything. I’m a theatre actor and an award-winning Videogames journalist. I look forward to being interviewed if I end up winning again this year. Thank you for everything that you do! – Team. HackerNoon P.S. If you enjoy getting interviewed (AKA, the ol’ intellectual stimulation, check out some more interviews !) here For more information: Read about the Noonies . To see all of the winners you may visit , pick any award, and view the name that appears at the top. Or follow for posts with the list of names released over the course of the week of February 14, 2022. here this site this account Read the FAQs about or . To see all of the winners you may visit , pick any city and view the name that appears at the top. Or follow for posts with the list of names released over the course of the week of February 14, 2022. Startups here here this site this account Thank you to all of our sponsors! We truly appreciate your contribution to the tech world and thus the future! : Startups , , , , , , , , , , Blockster Brex FreeCodeCamp LaunchDarkly Coil Udacity Udemy Vercel Asia Pacific Transgender Network Bybit Everscale Network : Noonies The Noonies Awards are sponsored by: , , and hosted by: Bybit Avast TECH Domains HackerNoon

Stocks will be More Profitable than Crypto - Interview With Bryan Applegate

“AI literacy” is an issue that needs to be addressed. The vast majority of IT and line of business managers did not grow up with artificial intelligence. They are not comfortable with the technology and are happy to take “exploratory” meetings but are loathe to move forward on any AI project. “Without this type of program, we may well be condemned to sitting in meetings for years where everyone nods their head and smiles, but no one ever signs off on anything.” This has led to AI being trapped within Innovation teams that are highly segregated from the rest of the company, or being locked out of the enterprise altogether. What’s the solution? The managing class needs to be made to feel more comfortable with artificial intelligence. Their fears need to be allayed (the robot apocalypse has been cancelled), and their understanding of the technology and its strategic value has to be built up. Just like Johnny Appleseed, the industry needs to send out representatives across the land to raise the overall AI literacy of executives and managers. This will greatly accelerate AI adoption. Without this type of program, we may well be condemned to sitting in meetings for years where everyone nods their head and smiles, but no one ever signs off on anything. It’s time for all the Appleseeds out there to fill up their pouches and start walking the highways and byways of the big blue marble.

AI needs a Johnny Appleseed Program

Hey everyone, today I want to do a tutorial on one of my favorite ways to deploy a quick REST API, using NodeJS/Express, to an Amazon EC2 server. This technique essentially enables your EC2 server to respond to changes pushed to your GitHub repository. First Things First, “Hello World” Create a new directory on your machine for a NodeJS/Express app to live. I’m calling mine rekognition Open up a terminal, and run this command to initialize a package.json npm init -y Install express.js npm i express Create a basic express server with a ‘hello world’ at the default route const express = require('express');
const app = express();
const port = 3000;

app.get('/', (req, res) => {
    res.send('Hello World!');
});

app.listen(port, () => {
    console.log(`Example app listening at http://localhost:${port}`);
}); Test to make sure you are seeing ‘Hello World!’ at http://localhost:3000/ Good job, step one complete! 💪 Next, Let’s Push Our Code to GitHub Initialize a Git repo in your directory, and make your first commit — git init
git add .
git commit -m "First commit" Create a remote repository on your GitHub account Add the new repo as the origin, and push your branch. git remote add origin <REMOTE_REPOSITORY_URL>
git push -u origin master Replace <REMOTE_REPOSITORY_URL> with the link to the remote repo that you just created. You might need to change your repository settings to use ‘master’ as the default branch instead of ‘main.’ After you do this you can delete the ‘main’ branch. Step 2: complete! We’re cooking with gas ⛽️ Let’s Go to the Cloud — Setup the Ec2 Server Here are the steps to launch your EC2 Instance: Log in to your AWS Management Console. Navigate to the EC2 dashboard, and launch a new instance.



Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Select an instance type (e.g., t2.micro if you are under the free tier). Configure instance details, add storage, and add tags as necessary. Configure a security group to allow inbound traffic on ports you’ll need (at least TCP port 22 for SSH and your application’s port, and then 3000 for web traffic). Review and launch the instance; ensure that you save the key pair used for SSH access. Now, let’s test logging into your server via SSH on a terminal: ssh ec2-user@<YOUR_SERVER_IP> -i <YOUR_PRIVATE_KEY>.pem Replace the variables there with the values you defined for your EC2 instance. If you see this you’ve connected to your server, congrats! 👏 We’re Not Done Just Yet Though — We’re Just Getting Started 😏 Let’s install NodeJS on our server:sudo yum install -y nodejs Install pm2 globally on our server via npm sudo npm i -g pm2 Install git on the server, and configure your credentials: sudo yum install git -y git config --global user.name "Your Name"
git config --global user.email "your.email@example.com" Okay, now we’re going to create a var/www/ folder if it does not already exist: sudo mkdir -p /var/www Then add ownership to our ec2-user: sudo chown -R ec2-user:ec2-user /var/www Navigate to the directory from the root of your server — not the /home folder people 👌 cd ~/var/www Now, from here, we will clone our git repository: git clone https://github.com/USERNAME/REPO_NAME.git YOUR_PROJECT_DIRECTORY Replace [USERNAME] [REPO_NAME] and [YOUR_PROJECT_DIRECTORY] with your own values. Next, we change the directory into our repository, so cd YOUR_PROJECT_DIRECTORYcan create the ecosystem.config.js file for our pm2 setup: nano ecosystem.config.js It looks like this: module.exports = {
  apps : [{
    name: "my-app",  // A name for your application
    script: "app.js",  // The script file to launch the app
    instances: "max",  // This can be set to the number of CPU cores to use, or "max" to use all available
    autorestart: true,  // Automatically restart app if it crashes
    watch: false,  // Enable/disable watching file changes for automatic restart
    max_memory_restart: '1G',  // Optional: Restart app if it reaches a memory limit
    env: {
      NODE_ENV: "development",
    },
    env_production: {
      NODE_ENV: "production",
    }
  }]
}; Cool beans, okay — once that is created and saved, let’s start up the app with pm2: pm2 start ecosystem.config.js Now, we can check that we have a ‘Hello World!’ from our server on port 3000: To make pm2 start automatically on server restarts, let’s run: pm2 save
pm2 startup To check your server is running, you can do pm2 status;  you can read the docs on pm2 here If you’ve made it this far, you are a superstar ⭐️ Integration With GitHub Actions This is the last step in our process. We’re going to create a .yml file for Github actions to update our server anytime a change is pushed to our master branch In your repository, go to the ‘Actions’ tab and create a new custom workflow. I am calling mine nodejs.yml Here is the .yml file for updating the repo and restarting pm2: name: Node.js CI/CD on Amazon Linux

on:
  push:
    branches: [ master ]

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Install dependencies
      run: npm install

    - name: Deploy to AWS EC2
      uses: appleboy/scp-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        source: "./"  # This now correctly points to the current directory
        target: "/var/www/your_project_directory"

    - name: Restart PM2 application
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        script: |
          cd /var/www/your_project_directory
          pm2 reload all  # This command restarts your application Make sure to update ‘your_project_directory’ Lastly, you’ll need to add these environment secrets. REMOTE_HOSTthis is the IP address of your server; REMOTE_USER this is ec2-user for Amazon Linux 2 AMI, and then paste the contents of your .pem file as the SSH_PRIVATE_KEY You can do all of this in the repository settings: That’s it! We’re done yay 😁 You can test this all by changing the ‘Hello World’ message and pushing that change to your master branch; then you should see the update at http://your.ip.address:3000 It is a bit of a process to set up, but when you’re developing, it’s really nice to have an easy CI/CD pipeline automatically deploying changes to your REST API server. That way, you can quickly deploy the changes live and see them in the front end of your web/mobile application. Let me know if this was useful in the comments, and thanks for reading!! Peace out, — Wes Hey everyone, today I want to do a tutorial on one of my favorite ways to deploy a quick REST API, using NodeJS/Express, to an Amazon EC2 server. This technique essentially enables your EC2 server to respond to changes pushed to your GitHub repository. First Things First, “Hello World” Create a new directory on your machine for a NodeJS/Express app to live. I’m calling mine rekognition rekognition Open up a terminal, and run this command to initialize a package.json npm init -y npm init -y Install express.js npm i express npm i express Create a basic express server with a ‘hello world’ at the default route const express = require('express');
const app = express();
const port = 3000;

app.get('/', (req, res) => {
    res.send('Hello World!');
});

app.listen(port, () => {
    console.log(`Example app listening at http://localhost:${port}`);
}); const express = require('express');
const app = express();
const port = 3000;

app.get('/', (req, res) => {
    res.send('Hello World!');
});

app.listen(port, () => {
    console.log(`Example app listening at http://localhost:${port}`);
}); Test to make sure you are seeing ‘Hello World!’ at http://localhost:3000/ http://localhost:3000/ Good job, step one complete! 💪 Next, Let’s Push Our Code to GitHub Initialize a Git repo in your directory, and make your first commit — git init
git add .
git commit -m "First commit" git init
git add .
git commit -m "First commit" Create a remote repository on your GitHub account Add the new repo as the origin, and push your branch. git remote add origin <REMOTE_REPOSITORY_URL>
git push -u origin master git remote add origin <REMOTE_REPOSITORY_URL>
git push -u origin master Replace <REMOTE_REPOSITORY_URL> with the link to the remote repo that you just created. <REMOTE_REPOSITORY_URL> You might need to change your repository settings to use ‘master’ as the default branch instead of ‘main.’ After you do this you can delete the ‘main’ branch. Step 2: complete! We’re cooking with gas ⛽️ Let’s Go to the Cloud — Setup the Ec2 Server Here are the steps to launch your EC2 Instance: Log in to your AWS Management Console. Log in to your AWS Management Console . AWS Management Console Navigate to the EC2 dashboard, and launch a new instance. Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Navigate to the EC2 dashboard, and launch a new instance. Navigate to the EC2 dashboard, and launch a new instance. Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Choose an appropriate AMI (Amazon Machine Image); I am using Amazon Linux 2. Select an instance type (e.g., t2.micro if you are under the free tier). Select an instance type (e.g., t2.micro if you are under the free tier). Configure instance details, add storage, and add tags as necessary. Configure instance details, add storage, and add tags as necessary. Configure a security group to allow inbound traffic on ports you’ll need (at least TCP port 22 for SSH and your application’s port, and then 3000 for web traffic). Configure a security group to allow inbound traffic on ports you’ll need (at least TCP port 22 for SSH and your application’s port, and then 3000 for web traffic). Review and launch the instance; ensure that you save the key pair used for SSH access. Review and launch the instance; ensure that you save the key pair used for SSH access. Now, let’s test logging into your server via SSH on a terminal: ssh ec2-user@<YOUR_SERVER_IP> -i <YOUR_PRIVATE_KEY>.pem ssh ec2-user@<YOUR_SERVER_IP> -i <YOUR_PRIVATE_KEY>.pem Replace the variables there with the values you defined for your EC2 instance. If you see this you’ve connected to your server, congrats! 👏 We’re Not Done Just Yet Though — We’re Just Getting Started 😏 Let’s install NodeJS on our server: sudo yum install -y nodejs sudo yum install -y nodejs Install pm2 globally on our server via npm pm2 sudo npm i -g pm2 sudo npm i -g pm2 Install git on the server, and configure your credentials: sudo yum install git -y sudo yum install git -y git config --global user.name "Your Name"
git config --global user.email "your.email@example.com" git config --global user.name "Your Name"
git config --global user.email "your.email@example.com" Okay, now we’re going to create a var/www/ folder if it does not already exist: var/www/ sudo mkdir -p /var/www sudo mkdir -p /var/www Then add ownership to our ec2-user: sudo chown -R ec2-user:ec2-user /var/www sudo chown -R ec2-user:ec2-user /var/www Navigate to the directory from the root of your server — not the /home folder people 👌 cd ~/var/www from the root of your server cd ~/var/www Now, from here, we will clone our git repository: git clone https://github.com/USERNAME/REPO_NAME.git YOUR_PROJECT_DIRECTORY git clone https://github.com/USERNAME/REPO_NAME.git YOUR_PROJECT_DIRECTORY Replace [USERNAME] [REPO_NAME] and [YOUR_PROJECT_DIRECTORY] with your own values. Next, we change the directory into our repository, so cd YOUR_PROJECT_DIRECTORY can create the ecosystem.config.js file for our pm2 setup: cd YOUR_PROJECT_DIRECTORY ecosystem.config.js nano ecosystem.config.js nano ecosystem.config.js It looks like this: module.exports = {
  apps : [{
    name: "my-app",  // A name for your application
    script: "app.js",  // The script file to launch the app
    instances: "max",  // This can be set to the number of CPU cores to use, or "max" to use all available
    autorestart: true,  // Automatically restart app if it crashes
    watch: false,  // Enable/disable watching file changes for automatic restart
    max_memory_restart: '1G',  // Optional: Restart app if it reaches a memory limit
    env: {
      NODE_ENV: "development",
    },
    env_production: {
      NODE_ENV: "production",
    }
  }]
}; module.exports = {
  apps : [{
    name: "my-app",  // A name for your application
    script: "app.js",  // The script file to launch the app
    instances: "max",  // This can be set to the number of CPU cores to use, or "max" to use all available
    autorestart: true,  // Automatically restart app if it crashes
    watch: false,  // Enable/disable watching file changes for automatic restart
    max_memory_restart: '1G',  // Optional: Restart app if it reaches a memory limit
    env: {
      NODE_ENV: "development",
    },
    env_production: {
      NODE_ENV: "production",
    }
  }]
}; Cool beans, okay — once that is created and saved, let’s start up the app with pm2: pm2 start ecosystem.config.js pm2 start ecosystem.config.js Now, we can check that we have a ‘Hello World!’ from our server on port 3000: To make pm2 start automatically on server restarts, let’s run: pm2 save
pm2 startup pm2 save
pm2 startup To check your server is running, you can do pm2 status ;  you can read the docs on pm2 here pm2 status pm2 here If you’ve made it this far, you are a superstar ⭐️ Integration With GitHub Actions This is the last step in our process. We’re going to create a .yml file for Github actions to update our server anytime a change is pushed to our master branch .yml In your repository, go to the ‘Actions’ tab and create a new custom workflow. I am calling mine nodejs.yml nodejs.yml Here is the .yml file for updating the repo and restarting pm2: name: Node.js CI/CD on Amazon Linux

on:
  push:
    branches: [ master ]

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Install dependencies
      run: npm install

    - name: Deploy to AWS EC2
      uses: appleboy/scp-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        source: "./"  # This now correctly points to the current directory
        target: "/var/www/your_project_directory"

    - name: Restart PM2 application
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        script: |
          cd /var/www/your_project_directory
          pm2 reload all  # This command restarts your application name: Node.js CI/CD on Amazon Linux

on:
  push:
    branches: [ master ]

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2

    - name: Install dependencies
      run: npm install

    - name: Deploy to AWS EC2
      uses: appleboy/scp-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        source: "./"  # This now correctly points to the current directory
        target: "/var/www/your_project_directory"

    - name: Restart PM2 application
      uses: appleboy/ssh-action@master
      with:
        host: ${{ secrets.REMOTE_HOST }}
        username: ${{ secrets.REMOTE_USER }}
        key: ${{ secrets.SSH_PRIVATE_KEY }}
        script: |
          cd /var/www/your_project_directory
          pm2 reload all  # This command restarts your application Make sure to update ‘your_project_directory’ Lastly, you’ll need to add these environment secrets. REMOTE_HOST this is the IP address of your server; REMOTE_USER this is ec2-user for Amazon Linux 2 AMI, and then paste the contents of your .pem file as the SSH_PRIVATE_KEY REMOTE_HOST REMOTE_USER ec2-user SSH_PRIVATE_KEY You can do all of this in the repository settings: That’s it! We’re done yay 😁 You can test this all by changing the ‘Hello World’ message and pushing that change to your master branch; then you should see the update at http://your.ip.address:3000 http://your.ip.address:3000 It is a bit of a process to set up, but when you’re developing, it’s really nice to have an easy CI/CD pipeline automatically deploying changes to your REST API server. That way, you can quickly deploy the changes live and see them in the front end of your web/mobile application. Let me know if this was useful in the comments, and thanks for reading!! Peace out, — Wes

How to Create a CI/CD Pipeline Using GitHub and AWS EC2

GitHub এবং AWS EC2 ব্যবহার করে কিভাবে একটি CI/CD পাইপলাইন তৈরি করবেন

So erstellen Sie eine CI/CD-Pipeline mit GitHub und AWS EC2

Cómo crear una canalización de CI/CD utilizando GitHub y AWS EC2

Comment créer un pipeline CI/CD à l'aide de GitHub et AWS EC2

GitHub और AWS EC2 का उपयोग करके CI/CD पाइपलाइन कैसे बनाएं

GitHub と AWS EC2 を使用して CI/CD パイプラインを作成する方法

GitHub 및 AWS EC2를 사용하여 CI/CD 파이프라인을 만드는 방법

Como criar um pipeline de CI/CD usando GitHub e AWS EC2

Как создать конвейер CI/CD с помощью GitHub и AWS EC2

GitHub ve AWS EC2 Kullanılarak CI/CD Ardışık Düzeni Nasıl Oluşturulur

Cách tạo quy trình CI/CD bằng GitHub và AWS EC2

如何使用 GitHub 和 AWS EC2 创建 CI/CD 管道

Virtual Meetings have become an essential part of corporate collaboration, serving as the de facto way that ideas are exchanged, decisions are made, and strategies are devised. However, the true value of meetings is often diluted by their length and the complexity of the discussions. This is why note-taking and effective summaries and action points are so important. Converting long and often pointless discussions into short (actionable) summaries, meeting attendees can quickly catch up on meetings they missed, review decisions that were made, and understand discussions without having to sift through hours and hours of recordings. We thought it would be cool to create our summarizer. If you don't have one already, keep reading. This technical tutorial will guide you through creating a simple web application that summarizes daily meeting Transcripts using ApyHub’s AI Summarize Document API using NodeJS. Pre-requisites: Access to Google Meet and permission to access meeting transcripts.
A preferred programming language environment (e.g., Python).
ApyHub Account.
GitHub CLI is installed on your computer. Step 1: Clone the GitHub repository Open your terminal and run this command: git clone https://github.com/iamspathan/AI-Transcript-Summarizer.git This command will clone the project in your local environment. Once the project is cloned, you can open the repository in the code editor. Step 2. Install Required Packages: Here, in Node Package Manager (npm), we will install all the dependencies that our application needs to summarize the meeting transcribe. npm install Step 3: Add your API Key to the index.js file. Here, we will add our Secret API key from ApyHub. To generate an API key, you can visit the documentation page of AI Summarize Document API. Your secret looks like this ➡️
apy-token: APY****************************************** Copy this token and paste it in as shown in the code comment below. const express = require('express');
const fileUpload = require('express-fileupload');
const cors = require('cors');
const axios = require('axios');
const FormData = require('form-data');
const open = require('open');
const app = express();
const port = 3000;

app.use(cors());
app.use(fileUpload());

// Serve static files from the 'public' directory
app.use(express.static('public'));

app.post('/summarize', (req, res) => {
    console.log("summarixe called", req.files.file);
    if (!req.files || Object.keys(req.files).length === 0) {
        return res.status(400).send('No files were uploaded.');
    }

    // Assuming the file is attached to the request under the key 'file'
    const file = req.files.file;

    // Prepare the file to be sent using form-data
    const formData = new FormData();
    formData.append('file', file.data, file.name);

    // Set up the request headers, including the dynamic headers from form-data and the secret-apy token.
    const requestHeaders = {
        ...formData.getHeaders(),
        'apy-token': 'ADD YOUR OWN APY-TOKEN HERE'
    };

    // Call the AI Summarize API
    axios.post('https://api.apyhub.com/ai/summarize-documents/file', formData, { headers: requestHeaders })
        .then(apiResponse => {
            // Assuming the API returns JSON with a summary field
            console.log(apiResponse.data.data.summary);
            res.send({ summary: apiResponse.data.data.summary });
        })
        .catch(error => {
            console.error('Error calling the AI Summarize API:', error);
            res.status(500).send('Failed to summarize the document.');
        });
});

app.listen(port, () => {
    console.log(`Server running at http://localhost:${port}`);
    // Open the index.html file in the default browser
    open(`http://localhost:${port}`);
}); Once you’ve added the API key. Save the changes using the Ctrl+S Key. Step 4: Running Your Application Once you’ve added the API key. Save the changes using Ctrl+S in your terminal, and run this command.: node index.js That’s it :) As you can see, Now you can generate a meeting transcript anytime you want :) Virtual Meetings have become an essential part of corporate collaboration, serving as the de facto way that ideas are exchanged, decisions are made, and strategies are devised. However, the true value of meetings is often diluted by their length and the complexity of the discussions. This is why note-taking and effective summaries and action points are so important. Converting long and often pointless discussions into short (actionable) summaries, meeting attendees can quickly catch up on meetings they missed, review decisions that were made, and understand discussions without having to sift through hours and hours of recordings. We thought it would be cool to create our summarizer. If you don't have one already, keep reading. This technical tutorial will guide you through creating a simple web application that summarizes daily meeting Transcripts using ApyHub’s AI Summarize Document API using NodeJS. ApyHub’s AI Summarize Document API Pre-requisites: Access to Google Meet and permission to access meeting transcripts. A preferred programming language environment (e.g., Python). ApyHub Account. GitHub CLI is installed on your computer. Access to Google Meet and permission to access meeting transcripts. Google Meet A preferred programming language environment (e.g., Python). ApyHub Account . ApyHub Account GitHub CLI is installed on your computer. Step 1: Clone the GitHub repository Open your terminal and run this command: git clone https://github.com/iamspathan/AI-Transcript-Summarizer.git git clone https://github.com/iamspathan/AI-Transcript-Summarizer.git This command will clone the project in your local environment. Once the project is cloned, you can open the repository in the code editor. Step 2. Install Required Packages: Here, in Node Package Manager (npm), we will install all the dependencies that our application needs to summarize the meeting transcribe. npm install npm install Step 3: Add your API Key to the index.js file. Here, we will add our Secret API key from ApyHub. To generate an API key, you can visit the documentation page of AI Summarize Document API . Your secret looks like this ➡️ apy-token: APY****************************************** AI Summarize Document API apy-token: APY****************************************** Copy this token and paste it in as shown in the code comment below. const express = require('express');
const fileUpload = require('express-fileupload');
const cors = require('cors');
const axios = require('axios');
const FormData = require('form-data');
const open = require('open');
const app = express();
const port = 3000;

app.use(cors());
app.use(fileUpload());

// Serve static files from the 'public' directory
app.use(express.static('public'));

app.post('/summarize', (req, res) => {
    console.log("summarixe called", req.files.file);
    if (!req.files || Object.keys(req.files).length === 0) {
        return res.status(400).send('No files were uploaded.');
    }

    // Assuming the file is attached to the request under the key 'file'
    const file = req.files.file;

    // Prepare the file to be sent using form-data
    const formData = new FormData();
    formData.append('file', file.data, file.name);

    // Set up the request headers, including the dynamic headers from form-data and the secret-apy token.
    const requestHeaders = {
        ...formData.getHeaders(),
        'apy-token': 'ADD YOUR OWN APY-TOKEN HERE'
    };

    // Call the AI Summarize API
    axios.post('https://api.apyhub.com/ai/summarize-documents/file', formData, { headers: requestHeaders })
        .then(apiResponse => {
            // Assuming the API returns JSON with a summary field
            console.log(apiResponse.data.data.summary);
            res.send({ summary: apiResponse.data.data.summary });
        })
        .catch(error => {
            console.error('Error calling the AI Summarize API:', error);
            res.status(500).send('Failed to summarize the document.');
        });
});

app.listen(port, () => {
    console.log(`Server running at http://localhost:${port}`);
    // Open the index.html file in the default browser
    open(`http://localhost:${port}`);
}); const express = require('express');
const fileUpload = require('express-fileupload');
const cors = require('cors');
const axios = require('axios');
const FormData = require('form-data');
const open = require('open');
const app = express();
const port = 3000;

app.use(cors());
app.use(fileUpload());

// Serve static files from the 'public' directory
app.use(express.static('public'));

app.post('/summarize', (req, res) => {
    console.log("summarixe called", req.files.file);
    if (!req.files || Object.keys(req.files).length === 0) {
        return res.status(400).send('No files were uploaded.');
    }

    // Assuming the file is attached to the request under the key 'file'
    const file = req.files.file;

    // Prepare the file to be sent using form-data
    const formData = new FormData();
    formData.append('file', file.data, file.name);

    // Set up the request headers, including the dynamic headers from form-data and the secret-apy token.
    const requestHeaders = {
        ...formData.getHeaders(),
        'apy-token': 'ADD YOUR OWN APY-TOKEN HERE'
    };

    // Call the AI Summarize API
    axios.post('https://api.apyhub.com/ai/summarize-documents/file', formData, { headers: requestHeaders })
        .then(apiResponse => {
            // Assuming the API returns JSON with a summary field
            console.log(apiResponse.data.data.summary);
            res.send({ summary: apiResponse.data.data.summary });
        })
        .catch(error => {
            console.error('Error calling the AI Summarize API:', error);
            res.status(500).send('Failed to summarize the document.');
        });
});

app.listen(port, () => {
    console.log(`Server running at http://localhost:${port}`);
    // Open the index.html file in the default browser
    open(`http://localhost:${port}`);
}); Once you’ve added the API key. Save the changes using the Ctrl+S Key. Ctrl+S Step 4: Running Your Application Once you’ve added the API key. Save the changes using Ctrl+S in your terminal, and run this command.: node index.js node index.js That’s it :) As you can see, Now you can generate a meeting transcript anytime you want :)

Building an AI-Powered Summarizer using NodeJS and ApyHub API To Make Meetings Easy

Event notifications in MinIO may not seem thrilling at first, but once you harness their power, they illuminate the dynamics within your storage buckets. Event notifications are critical components of a full-fledged, efficient object storage system. Webhooks are my personal . They are like a Swiss Army knife in the world of events, offering a universal solution to various challenges. favorite tool for integrating with MinIO MinIO's user-friendly UI provides seamless service , but we're diving deeper in this guide. We're building services from scratch in Python, using their client credentials, to walk you through the nuts and bolts of MinIO integration. integrations In our exploration, we'll focus on deploying using docker-compose, a method that offers streamlined and efficient orchestration. This approach will involve setting up a cohesive environment for MinIO and Flask, enabling them to interact seamlessly. By integrating the MinIO service with its appropriate credentials and configurations, we aim to create a systematic workflow that effectively demonstrates the practical application of managing and responding to MinIO bucket events. Once we set up client configurations and define the structure for response data, as always, the real fun begins. This demonstration will highlight several key aspects of how you can connect your MinIO client to a Flask application where the event notification data can further be processed. We want you to feel comfortable in developing your own event-driven systems with MinIO, so utilize the services we've provided in the resource hosted on . blog-assets/flask-webhook-event-notifications MinIO’s GitHub Page Prepare to dive into a world where data handling is both an art and a science, made simpler with MinIO. It's an opportunity to innovate, create and revolutionize the way your apps work with data. MinIO and Integrated Services MinIO's integration into the exemplifies its adaptability across various cloud technologies. Webhooks are pivotal, offering developers the flexibility to craft custom integrations, whether for managing data across diverse cloud platforms or for local home lab setups. Kubernetes ecosystem This guide goes beyond theoretical concepts, providing you with practical, executable code snippets to build your integrations. It's an invitation to explore the boundless potential of your creativity in leveraging MinIO event notifications. Laying the Groundwork for a Python Application with Docker The initial phase of our journey is dedicated to harnessing the power of Docker's containerization to craft a robust Python application environment. Our approach centers around deploying with Docker-compose, a method chosen for its simplicity and effectiveness. This choice is designed to cater to a wide range of developers, prioritizing ease of use and rapid deployment while ensuring a high level of functionality. Utilizing Docker-compose, we create a user-friendly, configuration-driven setup. This environment is perfect for those seeking quick deployment without sacrificing the depth of their project's capabilities. It provides a straightforward pathway to integrate advanced webhook features and fine-tune MinIO settings, catering to the specific requirements of your project. Each step we take in setting up this environment is crucial. It's not just about getting the services up and running; it's about understanding and leveraging components to create a comprehensive system. Developing your own systems can be the spark that ignites your innovation, enhancing your overall data management strategy, and eventually turns your raw data into actionable, insightful information. Deploying MinIO and Integrated Services Deploy with Docker-Compose: Flask App and MinIO We will begin by setting up a Python application and its environment. This involves deploying MinIO with docker compose and the services to be integrated. To set up MinIO with a Flask application, we will be using the command to clone the repository to your local environment: git minio/blog-assets git clone https://github.com/minio/blog-assets.git

cd flask-webhook-event-notifications

docker-compose up This will clone the repository from GitHub, navigate to the directory containing the file, and start the MinIO and Flask services. minio/blog-assets /flask-webhook-event-notifications/ docker-compose.yaml Directory Structure This docker-compose structure outlines two services and their respective configuration variables. For visualization purposes, I have provided a tree view of the desired directory structure here: /flask-webhook-event-notifications
├── Dockerfile
├── app
│       └── main.py
└── docker-compose.yaml Setting up Webhooks in MinIO Configuring a webhook in MinIO can be accomplished through various methods ranging from using the user-interface, by using (the MinIO client utility), or by way of scripting with various programming languages. mc MinIO supports a , including: , , , , , , , , , and . variety of external services for event notifications AMQP (RabbitMQ) MQTT NATS NSQ Elasticsearch Kafka MySQL PostgreSQL Redis webhook services Setting up MinIO to utilize these involves a series of well-defined steps, ensuring that your MinIO instance not only captures but also effectively communicates important event data as  an interactive, responsive part of your application ecosystem. event notifications Understanding the Data Structure of MinIO Event Notifications The S3 event notifications from MinIO include a , essential for a comprehensive understanding and effective management of events. Below I have listed some of the values found from within the event data: detailed JSON data structure : The unique identifier of the object in the bucket. Key : The object’s version identifier for integrity and version control. eTag : The size of the object in bytes, indicating its scale. Size : Ensures the events are processed in the exact sequence they occurred. Sequencer : The media type of the object, specifying how to handle or display the file. ContentType : User-defined metadata attached to the object, providing additional context. UserMetadata : Bucket Details : The unique identifier for the bucket in AWS. ARN (Amazon Resource Name) : The name of the bucket where the object is stored. Name : Information about the owner of the bucket. OwnerIdentity : Indicates the version of the S3 event notification schema used. s3SchemaVersion : Identifier for the specific notification configuration that triggered this event. ConfigurationId This structure is particularly effective for , enabling systematic logging, parsing and analysis of interactions with the MinIO bucket. Flask applications Setting Up MinIO for Webhooks and Event-Driven Operations After deploying the outlined above, continue by using the MinIO Client, , command-line utility. This setup involves creating an alias in MinIO, configuring the endpoint and setting bucket notifications. docker-compose.yaml mc We will be working inside of an interactive terminal for the container, which we can spawn by running a single command: “minio” docker exec -it minio /bin/sh The reason for running our mc commands from within this shell is because the Docker image already has installed and ready to go. minio/minio mc Once inside the container’s interactive terminal, the process of configuring MinIO for event notifications using the MinIO Client (mc) involves the following key steps: : The first step involves creating an alias for your MinIO server using the MinIO Client (mc). This alias is a shortcut to your MinIO server, allowing you to easily execute further mc commands without repeatedly specifying the server’s address and access credentials. This step  simplifies the management of your MinIO server through the client. Setting Up MinIO Alias mc alias set myminio http://localhost:9000 minio minio123 : Configure a new webhook service endpoint in MinIO. This setup is done using either environment variables or runtime configuration settings, where you define important parameters such as the endpoint URL, an optional authentication token for security, and client certificates for secure connections. Adding the Webhook Endpoint to MinIO mc admin config set myminio notify_webhook:1 endpoint="http://flaskapp:5000/minio-event" queue_limit="10" : Once you have configured the settings, restart your MinIO deployment to ensure the changes take effect. Restarting the MinIO Deployment mc admin service restart myminio Expect: Restart command successfully sent to myminio. Type Ctrl-C to quit or wait to follow the status of the restart process....Restarted myminio successfully in 1 seconds : The next step involves using the mc event add command. This command is used to add new bucket notification events, setting the newly configured Webhook service as the target for these notifications. Configuring Bucket Notifications mc event add myminio/mybucket arn:minio:sqs::1:webhook --event put,get,delete Expect: Successfully added arn:minio:sqs::1:webhook : Run this command to list the event assigned to myminio/mybucket: List Bucket Subscribed Events minio mc event list myminio/mybucket Expect: arn:minio:sqs::1:webhook s3:ObjectCreated:*,s3:ObjectAccessed:*,s3:ObjectRemoved:*  Filter: : Run this command to list the event assigned to myminio/mybucket in JSON format: List Bucket Assigned Events (in JSON) minio mc event list myminio/mybucket arn:minio:sqs::1:webhook --json Expect: { "status": "success", "id": "", "event": ["s3:ObjectCreated:","s3:ObjectAccessed:", "s3:ObjectRemoved:*"], "prefix": "", "suffix": "", "arn": "arn:minio:sqs::1:webhook"} The Structure of the Event Notification Data Received by Flask Depending on the services or integration you are building, you may need to identify the event_data from your Flask app, and this requires a good understanding of the data your event provides. {
  "s3": {
    "bucket": {
      "arn": "arn:aws:s3:::mybucket",
      "name": "mybucket",
      "ownerIdentity": {
        "principalId": "minio"
      }
    },
    "object": {
      "key": "cmd.md",
      "eTag": "d8e8fca2dc0f896fd7cb4cb0031ba249",
      "size": 5,
      "sequencer": "17A9AB4FA93B35D8",
      "contentType": "text/markdown",
      "userMetadata": {
        "content-type": "text/markdown"
      }
    },
    "configurationId": "Config",
    "s3SchemaVersion": "1.0"
  },
  "source": {
    "host": "127.0.0.1",
    "port": "",
    "userAgent": "MinIO (linux; arm64) minio-go/v7.0.66 mc/RELEASE.2024-01-11T05-49-32Z"
  },
  "awsRegion": "",
  "eventName": "s3:ObjectCreated:Put",
  "eventTime": "2024-01-12T17:58:12.569Z",
  "eventSource": "minio:s3",
  "eventVersion": "2.0",
  "userIdentity": {
    "principalId": "minio"
  },
  "responseElements": {
    "x-amz-id-2": "dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8",
    "x-amz-request-id": "17A9AB4FA9328C8F",
    "x-minio-deployment-id": "c3642fb7-ab2a-44a0-96cb-246bf4d18e84",
    "x-minio-origin-endpoint": "http://172.18.0.3:9000"
  },
  "requestParameters": {
    "region": "",
    "principalId": "minio",
    "sourceIPAddress": "127.0.0.1"
  }
} By following these steps, you can effectively utilize MinIO event notifications, significantly automating data workflow processes. For more detailed guidance and information, please refer to the MinIO documentation on and . Bucket Notifications Monitoring Bucket and Object Events command-line tool for a more detailed, scriptable setup. The blog post further rounds out your understanding of the topic by emphasizing the importance of properly configuring PostgreSQL in the MinIO UI and the significance of restarting the MinIO server for changes to take effect. If you're interested in setting up , take a look at , where I’ve covered MinIO's extensive configuration and management of data events. These configurations range from using the for a user-friendly graphical interface to the MinIO with PostgreSQL Streamlining Data Events with MinIO and PostgreSQL MinIO Console mc Developing a Webhook with Flask to Receive Event Notifications Following the deployment of our environment, we now shift our focus to the integration of MinIO with Python, a key aspect of our data handling and processing system. This integration is pivotal in creating a cohesive ecosystem, where MinIO can seamlessly collaborate with Flask. Importing the Necessary Packages In our demonstration code, we carefully select Python imports to ensure the application's functionality aligns with its intended purpose. The package creates the web server infrastructure, defining endpoints to handle incoming HTTP requests. Then the application can be coded to handle the MinIO event notifications in any desired manner. flask from flask import  Flask, jsonify, request These imports collectively form the foundation of the application, enabling it to receive and process MinIO event notifications. Flask Application and Event Handling Endpoint in Python A Flask application is instantiated, and an endpoint is set up to handle POST requests at the route . Flask is a micro web framework in Python, ideal for setting up web applications and API endpoints. /minio-event app = Flask(__name__)

@app.route('/minio-event', methods=['POST'])
def handle_minio_event():
    event_data = request.json
    app.logger.info(f"Received MinIO event: {event_data}")
    return jsonify(event_data), 200 The function in the Flask app processes POST requests containing MinIO event data, and returns the received from the MinIO event notification. handle_minio_event event_data This approach facilitates real-time processing and response to storage events, enabling dynamic interaction between the MinIO storage system and the Flask application. Integrating Services with MinIO Bucket Events via Python Scripting This blog post used MinIO and Python in a Docker environment to demonstrate the power and flexibility of MinIO bucket event notifications, and demonstrates a strategic approach for creating scalable, efficient event-driven applications. The use of Docker, with its containerization technology, stands out for enabling components like MinIO and Flask to work independently yet cohesively. Of course, this containerized cloud-native setup minimizes conflicts and dependencies, highlighting Docker and Docker containers significance in modern software architecture. In conclusion of our exploration of MinIO webhook event notifications, I am convinced that the synergy of a dynamic programming language and MinIO’s formidable strength presents an unparalleled toolkit. This pairing paves the way for boundless opportunities in application development. It empowers us to not only innovate and streamline but also to expand our capabilities with remarkable efficiency and adaptability. This guide has demonstrated the simplicity and efficacy of API development using Python, laying a solid foundation for ongoing innovation and meeting ever-changing demands. It underscores the adaptability that is essential for the continued advancement in both data management and the evolution of application development. This approach is not just a methodology; it’s a pathway to future-proofing our technological endeavors.

Appleute

appleute.de

11-50 employees

Since 2018

COMPANY RANKING

APPLEUTE

EVERGREEN INDEX #579

Appleute WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

Appleute

appleute.de

11-50 employees

Since 2018

COMPANY RANKING

APPLEUTE

EVERGREEN INDEX #579

RELATED COMPANIESRANK

STORIES ABOUT APPLEUTE

Appleute WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!