<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Karl Montenegro on Medium]]></title>
        <description><![CDATA[Stories by Karl Montenegro on Medium]]></description>
        <link>https://medium.com/@karlmontenegro?source=rss-63bff010a6de------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QxzDXmo5EhUbRqPrQqBFTQ.jpeg</url>
            <title>Stories by Karl Montenegro on Medium</title>
            <link>https://medium.com/@karlmontenegro?source=rss-63bff010a6de------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 07:12:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@karlmontenegro/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Deploying a React + TypeScript app in Amazon Lightsail (with Nginx) — An updated guide in 18 steps.]]></title>
            <link>https://medium.com/@karlmontenegro/deploying-a-react-typescript-app-in-amazon-lightsail-with-nginx-an-updated-guide-in-18-steps-da8e33f4a329?source=rss-63bff010a6de------2</link>
            <guid isPermaLink="false">https://medium.com/p/da8e33f4a329</guid>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[nginx]]></category>
            <category><![CDATA[lightsail]]></category>
            <dc:creator><![CDATA[Karl Montenegro]]></dc:creator>
            <pubDate>Wed, 04 Sep 2024 04:01:51 GMT</pubDate>
            <atom:updated>2024-09-04T04:03:42.418Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EupW5tEbUe_IJvjDc3p4YQ.jpeg" /></figure><h3>Deploying a React + TypeScript app in AWS Lightsail (with Nginx) — A Basic Guide To Publish Your App In 18 steps.</h3><p>While making preparations before our wedding, my fiance and I decided to send out digital invitations since we didn’t want to spend too much on the first of 2 wedding ceremonies. If you wanna be “completely married” you go through the legal and the religious route in my country.</p><p>I thought: “Since I’m a software engineer/developer I’ll code the invitations myself”, even that, for the longest time my success when doing web development was mixed.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F25117042&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fthanos-gif-25117042&amp;image=https%3A%2F%2Fmedia.tenor.com%2Fu8YEMwIfJGMAAAAN%2Fthanos.png&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f1759cb2aab5a8dc55c72537e4c59d0/href">https://medium.com/media/8f1759cb2aab5a8dc55c72537e4c59d0/href</a></iframe><p>My first freelance job was redesigning a small webpage. I knew the basics of static html5/css3 so I decided to take a stab at it. Long story short, the webpage worked but I accidentally deleted an associated site that they had for the hotel’s restaurant and it’s menu.</p><p>But hey, it’s been a really long time since then, I’ve worked in a lot of projects, I’m pretty good at programming so, it must be different right? Well… for the most part, I applied Bulma CSS to a ReactJS app with a TypeScript template. I managed to design the invite, setup a basic form for RSVP and all… until the dreaded deploy arrived.</p><p>I must say, there are a lot of resources regarding how to serve your app by running a single line of code, maybe this looks familiar?</p><pre>npm install -g serve<br>serve build 8000</pre><p>For testing purposes, this is more than fine, but for serving a “set and forget” webpage, that you don’t wanna go all sysadmin on it since you need to focus on more important stuff like getting married, it’s not enough.</p><p>Even though that I tried to make this approach work using pm2 I quickly realized that I would have to keep on monitoring the process for it not to die on me all of the sudden, or take extra time reading configuration docs for it to start on every instance reload and keep the webpage alive.</p><h3>NGINX to the Rescue</h3><p>It’s almost obvious that NGINX is super reliable in this scenario, but I must say that, after spending a full day researching how to setup NGINX to serve my app, the devil is in the details.</p><p><em>Quick Note: What follows is the consolidation of several resources I found on the matter. This is geared towards people that don’t want to get too carried away in server infrastructure or maintenance, but they REALLY want to get their website online. This setup can be improved/scaled depending on your site’s needs. Will be adding notes on each step that requires extra attention so you don’t get stuck.</em></p><h3>Setting Up The Instance</h3><h4>Step 1: Create an AWS account and head to</h4><p><a href="https://lightsail.aws.amazon.com/">https://lightsail.aws.amazon.com/</a></p><h4>Step 2: Hit the Create Instance button</h4><h4>Step 3: Pick a Linux/Unix instance image</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/923/1*wAFd_XhbhZjgGSzZmZ2MxQ.png" /></figure><h4>Step 4: Select Operating System (OS) only and pick Ubuntu with the latest version.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/919/1*i5F21x8yuaq3wiQN32lJBQ.png" /><figcaption>If you are an experienced Linux user and you know the nuances between the versions go ahead and select the other one.</figcaption></figure><h4>Step 5: Select an instance memory size of minimum 2GB (Very Important)</h4><p>This is very important since you will be creating a production build of your React app on this instance each time you update the project (more on that later). If you pick less than 2GB of memory, the build will have trouble finishing in time and you’ll end up with a blocked instance for several minutes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/939/1*gn3eyt9XTO9ne0GtARycmQ.png" /></figure><h4>Step 6: Setup a good identifier and click on Create Instance</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/905/1*fXkBRjfTnlA-lelVkpRamw.png" /></figure><p>Your instance after a couple of seconds should be running and it should look something like this on the dashboard</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*Ng_g0Zk8szulbxAFMUH-dQ.png" /></figure><h4><strong>Step 7: Setup a Static IP for your instance (Muy Importante)</strong></h4><p>So far so good, but if you need to restart your instance for some reason (i.e. app crash, or instance failing unexpectedly) its IP will reset, your Domain won’t match the IP and you’ll have a bad time, so let’s make a static IP so this doesn’t happen.</p><p>Go to Networking and click on Create static IP, select your instance as the one that you want to attach it to and put a name on the static IP for future reference. Click on create and there you go!</p><p><em>Quick note on Domains: This is the IP that you’ll need to set your Domain name to on the management platform of the Domain Name Provider of your choice. Usually you use this static IP and the Public IPv6 of the instance (you can find this last one on the manage section of your instance by clicking the 3 dots).</em></p><h3>Configuring The Instance So It Serves Your App</h3><h4>Step 8: Open a browser based SSH terminal to your instance</h4><p>You can also do this from PuTTY or SSH in Terminal, but for our purposes we will do it from the browser based terminal that AWS provides us. Click on the 3 dots, then Manage</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*aqzyzHPI-bRdpsa9jVIsmQ.png" /></figure><p>Click then on Connect using SSH, a new window will appear with a terminal, we can do all the final configuration from here on out.</p><h4>Step 9: Update package listings and install Nginx</h4><p>Type on the terminal the following:</p><pre>sudo apt-get update</pre><p>This updates your package listings in the instance. Next, we install nginx:</p><pre>sudo apt-get install nginx</pre><p>After finishing the install, lets make sure that Nginx is allowed access through the firewall by executing this:</p><pre>sudo ufw allow &#39;Nginx Full&#39;</pre><h4>Step 10: Install NodeJS and NPM to build our React app in the instance</h4><p>Use curl tool to download the Node setup script:</p><pre>sudo curl -sL https://deb.nodesource.com/setup_10.x -o nodesource_setup.sh</pre><p><em>Important Note: Make sure the version of Node that you download is the same or higher than the one you used to create your app. So if you created it with node 22.0.0, change</em> setup_10.x<em>to</em> setup_22.x</p><p>Then, run the script with bash:</p><pre>sudo bash nodesource_setup.sh</pre><p>After setup, install the latest Node.js package:</p><pre>sudo apt-get install nodejs</pre><p>Npm gets installed with node too. Finally, install build-essential package to ensure that all our npm packages will work correctly, this is an optional step but to be sure let’s do it:</p><pre>sudo apt-get install build-essential</pre><h4>Step 11: Get your code into the Lightsail Instance</h4><p>If you are familiar with React and TypeScript probably you are more than familiarized with git. Upload your app’s project to your favorite repository manager (i.e. github, bitbucket, etc) and make this repository public.</p><p><em>Important Note: This is required so that you can just run a git clone command from the Lightsail instance and get all your code there. For our current purposes this works, but for future endeavours you will have to setup key pairs and make the repository private for security concerns.</em></p><p>Type on your terminal the following:</p><pre>cd ~<br>git clone https://your_repository_manager_url/your_username/your_repository_name.git</pre><p>This will clone your project at root level in it’s own folder.</p><h4>Step 12: Install your project’s dependencies and create a production build</h4><p>Navigate to your project’s folder and then install its dependencies</p><pre>cd your_repository_name<br>npm i</pre><p>Lastly, lets’s make a production optimized build by running:</p><pre>npm run build</pre><p><em>Important: npm run build tends to require a lot of resources while building, that’s why we picked an instance with at least 2GB of memory, so we don’t worry about performance issues. If you opted for a lower memory instance, you can refer to Step 6.5 from Olafaloofian’s guide </em><a href="https://github.com/Olafaloofian/React-Frontend-Lightsail-Deployment?tab=readme-ov-file#step-65-weaksauce-extras"><em>here</em></a><em> which inspired this article.</em></p><h4>Step 13: Create Symbolic Links For Nginx</h4><p>If we copy the repository within the base folder, we could be showing too much of the source code to Nginx. A good practice is to only copy the built files after running npm run build.</p><p>Although, this is good, this can get tedious after a while, since we would need to manually copy the build folder every time we make a new feature in the app. So we use symbolic links to create a linked folder within Nginx that has a dynamic copy of our built app, which gets updated everytime we run the build command.</p><p>To set this up, we navigate to Nginx base folder, we remove the default html folder already created there and then we create a folder named after the domain of our app.</p><pre>cd /var/www/<br>sudo rm -r html<br>sudo mkdir your_domain.com</pre><p>At this point, we will start using our Domain name as the name of the folder to make sure that Nginx knows what to serve. Next, lets add the symbolic link to that domain folder using the ln -s command:</p><pre>sudo ln -s /home/your_username/your_repository_name/build/* /var/www/your_domain.com/</pre><p>Before running make, sure that the route symbolic link route to your repository’s build folder is correct.</p><p><em>Important Note: By default, Lightsail uses the name of the instance’s OS as the username, you can find that information in the Manage section of your instance.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/652/1*-6x1bVcotmH2KIfDi4_ZTg.png" /></figure><p>After this, any new builds we execute at /home/your_username/your_repository will get mirrored to /var/www/your_domain.com/ thus relieving us from copying the build folder manually every time.</p><h4>Step 14: Edit NGINX Configuration Files</h4><p>We need to edit 2 files here: sites-available and sites-enabled, by creating a config file on sites-available we can leverage symbolic links to have a copy of that file over there, and once again avoid manually copying these</p><p>Let’s navigate to Nginx /etc folder and remove the default file already created there:</p><pre>cd /etc/nginx/sites-available<br>sudo rm -r default</pre><p>Also, let’s navigate to sites-enabled and delete the default file there too:</p><pre>cd /etc/nginx/sites-enabled<br>sudo rm -r default</pre><p>Removing these files prevent errors when testing our Nginx configuration, so make sure they are gone.</p><p>Let’s open vim to create a new file there with the configuration (you can use nano if you want, but I prefer vim)</p><pre>sudo vim your_domain.com</pre><p>To start editing the file, press the i key to start INSERT mode and type the following:</p><pre>server {<br> listen 80 default_server;<br> listen [::]:80 default_server;<br> root /var/www/your_domain.com;<br> index index.html;<br> server_name your_domain.com www.your_domain.com;<br> location / {<br>   try_files $uri $uri/ /index.html;<br> }<br>}</pre><p>Basically, this tells Nginx to listen to port 80 as the default_server. Then, at root /var/www/your_domain.com we have the folder that holds the dynamic copy of the React app’s build folder files and subdirectories, among them, the index.html file, which is the entry point of our whole app.</p><p>Next, we have the server_name, which tells Nginx which domains to resolve, you can include all the domains that need to redirect to root.</p><p>Lastly, location tells it to resolve any paths not available in the project route back to index.html instead of throwing an error and crashing the app.</p><p>Lets wrap this up by closing vim, press ESC to exit insert mode and then type :wq to save and quit the editor. Then let’s enter the following to create the last symbolic link between sites-available and sites-enabled:</p><pre>sudo ln -s /etc/nginx/sites-available/your_domain.com /etc/nginx/sites-enabled/your_domain.com</pre><p>This will create the dynamic copy in sites-enabled. Finally, let’s run a quick test to make sure that the config is correct:</p><pre>sudo nginx -t</pre><p>If this is successful, let’s restart Nginx to serve our app:</p><pre>sudo systemctl restart nginx</pre><h3>And Then… A 403 Appears!</h3><p>If you have gotten this far and you visit your domain in your browser you should see your React app up and running… BUT in most cases, you’ll see a 403 Forbidden error page.</p><p>This is what most tutorials omit to mention, and you could spend several hours trying to figure out what you did wrong… or you could just change the user on the nginx.conf file.</p><p><em>Note: Thanks to Mehdi for </em><a href="https://stackoverflow.com/a/60871679"><em>this answer</em></a><em>, you are the GOAT!.</em></p><h4>Step 15: Add your user to the nginx.conf file</h4><p>Lets navigate to /etc/nginx/ and then open the file with vim once again:</p><pre>cd /etc/nginx/<br>sudo vim nginx.conf</pre><p>Check if the user on top of the file is set to your default user (in our case it’s ubuntu since it’s the default user created by the Lightsail instance). Press i to insert text in the file like before, and add the following:</p><pre>user your_instance_user;</pre><p>Press ESC and then type :wq to save and quit vim. Then lets validate the config file by running:</p><pre>sudo nginx -t</pre><p>If it tests successfully, restart Nginx once again and reload your page:</p><pre>sudo systemctl restart nginx</pre><p>Nginx sometimes runs as a different user than the one at root level, so we need to make sure it runs with the correct permissions to serve our app.</p><h3>And Then… It Works!… but still needs the SSL</h3><p>And the wedding invitations app is ready for service…</p><p>BUT!</p><p>If you don’t want your website to fall into the pit of uncertainty and constant reminders that the user’s connection is insecure, you need to setup an SSL certificate for it. Don’t worry, this can be done free of charge and in the same terminal that we know and love so far.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ftenor.com%2Fembed%2F26462219&amp;display_name=Tenor&amp;url=https%3A%2F%2Ftenor.com%2Fview%2Fcerts-breath-mints-retsyn-gif-26462219&amp;image=https%3A%2F%2Fmedia.tenor.com%2Ft8SgHIzOs8kAAAAN%2Fcerts-breath-mints.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=tenor" width="600" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/6644fbef3ffc67cb9d0b188ae8852752/href">https://medium.com/media/6644fbef3ffc67cb9d0b188ae8852752/href</a></iframe><h4>Step 16: Install Certbot</h4><p>Let’s first install Certbot in our instance:</p><pre>sudo apt install certbot python3-certbot-nginx</pre><p>If you recall the setup we did on Step 14, we placed all the domain names that would resolve to the root folder of our site for the server_name field in the config file. Let’s check once more that the configuration is correct, so that Certbot can find it and update it automatically once it generates or certificates.</p><pre>sudo nginx -t</pre><p>If this succeeds let’s restart Nginx once more so the configuration takes place</p><pre>sudo systemctl restart nginx</pre><h4>Step 17: Configure HTTPS through the Firewall</h4><p>After this step, your website won’t allow connections through HTTP, but through HTTPS, which will solve any security issues that your browser detects.</p><p>Let’s first allow Nginx Full profile through the firewall and delete redundant Nginx HTTP profile allowance:</p><pre>sudo ufw allow &#39;Nginx Full&#39;<br>sudo ufw delete allow &#39;Nginx HTTP&#39;</pre><p>This will stop Nginx allowing HTTP connections. Your website may not be accessible as before, but don’t worry, we’ll set up HTTPS now.</p><p><em>Important Note: Make sure you add special firewall rules on your Lightsail instance, that way you can open </em>port 443<em> for incoming connections. Otherwise, the </em>HTTPS<em> configuration won’t work. You can do this in the Manage Instance page in the Networking tab.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/776/1*VJRc5PHrZV3ClecdZTT9Yg.png" /></figure><h4>Step 18: Obtain your SSL Certificate</h4><p>Lets run Certbot to obtain the certificate:</p><pre>sudo certbot --nginx -d your_domain.com -d www.your_domain.com</pre><p>This runs certbot with the --nginx plugin, using -d to specify the domain names we’d like the certificate to be valid for. Make sure you include all the domains you want added to the certificate (basically the ones you specified before in the sites-available folder on Step 14.</p><p>The first time you run Certbot, it’ll ask you for your email and to agree to the terms and conditions. If prompted with this screen:</p><pre>Output<br>Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.<br>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>1: No redirect - Make no further changes to the webserver configuration.<br>2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for<br>new sites, or if you&#39;re confident your site works on HTTPS. You can undo this<br>change by editing your web server&#39;s configuration.<br>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>Select the appropriate number [1-2] then [enter] (press &#39;c&#39; to cancel):</pre><p>Select option 2 and then press Enter, that way all the requests will be redirected to HTTPS, securing your site. After that, your certs will be downloaded, installed and loaded. Test it by accessing your site with https:// at the begining and you’ll see that the browser alert is gone!</p><h3>And we are DONE!</h3><p>Congratulations on making it this far. This is a compilation guide I decided to put together for any other person that decides to deploy their React application using Nginx on Lightsail.</p><p>Nginx is probably one of the most reliable ways to serve a website without getting in the nitty gritty of daemons, process managers, server startup config files, etc. As a mobile developer getting more comfortable in web development is a go to tool to quickly publish my site ideas and test them in the wild.</p><p>Also, React + TypeScript is a good way to retain that application/architectural feel that sometimes is hard to translate into web development structure, specially coming from a mobile dev background.</p><h3>Acknowledgements</h3><p>As I said before, this is a compilation of several tutorials put out by other authors regarding this subject. I just simply decided to streamline and reduce the process to something repeatable (with notes for issues that could get you stuck if you don’t solve them) for your next React project deploy. Thanks to:</p><ul><li><a href="https://medium.com/u/299d31f07e87"><strong>Yuhao Cooper</strong></a><strong> — How To Deploy React App On AWS Lightsail and Build Your Own Website.</strong></li></ul><p><a href="https://medium.com/@yuhaocooper/how-to-deploy-react-app-on-aws-lightsail-and-build-your-own-website-d4937c5c8792">https://medium.com/@yuhaocooper/how-to-deploy-react-app-on-aws-lightsail-and-build-your-own-website-d4937c5c8792</a></p><ul><li><a href="https://github.com/Olafaloofian"><strong>Olafaloofian</strong></a><strong> — React Frontend Lightsail Deployment:</strong></li></ul><p><a href="https://github.com/Olafaloofian/React-Frontend-Lightsail-Deployment?tab=readme-ov-file#step-65-weaksauce-extras">https://github.com/Olafaloofian/React-Frontend-Lightsail-Deployment?tab=readme-ov-file#step-65-weaksauce-extras</a></p><ul><li><strong>Brian Boucheron — How to secure nginx with let’s encrypt on ubuntu 20.04</strong></li></ul><p><a href="https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-20-04">https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-20-04</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da8e33f4a329" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reinvent Your Show And Gain Back Your Musical Thunder]]></title>
            <link>https://medium.com/@karlmontenegro/redefine-your-musical-product-and-gain-back-your-thunder-a55ab9ca55b1?source=rss-63bff010a6de------2</link>
            <guid isPermaLink="false">https://medium.com/p/a55ab9ca55b1</guid>
            <category><![CDATA[radio]]></category>
            <category><![CDATA[podcast]]></category>
            <category><![CDATA[rock-and-roll]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[edm]]></category>
            <dc:creator><![CDATA[Karl Montenegro]]></dc:creator>
            <pubDate>Thu, 09 Nov 2017 19:18:23 GMT</pubDate>
            <atom:updated>2018-01-06T01:16:06.954Z</atom:updated>
            <content:encoded><![CDATA[<p>After a few bumpy months while relocating to Chile, I’m glad to announce that I’m finally back with full force with my weekly podcast: Electric Jungle. For all of the people that hasn’t had the opportunity to listen to the first 90 episodes of my show, it can be summarized in one phrase: musical growth.</p><p>When I started my show several years ago, I slowly but surely started finding my own voice within the piles of music found at the end of a recently built bridge between the mainstream and the underground (i.e. the rise of the bedroom producer of 2010). I was able to find new music everywhere and build something that fitted my liking, then record cues on it and present the finest selection I could come up with at the moment as a finished product. Slowly but surely, like I said, I started getting burnt out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XQv4lDzCD7McjmGEW7i1OA.jpeg" /><figcaption>One of many nights playing the hits — Photo by Miguel Angel Delgado Gaspar</figcaption></figure><p>I realized that the music that I knew and loved slowly started getting more and more generic. Tracks sounded the same and I personally felt that electronic music diverged into a version of itself that lacked creativity and where everyone started copying blatantly from other producers in order to sell more.</p><p><strong>Dig Deeper</strong></p><p>To change my state of mind, I decided to reset the way I dig for music. When selecting records, I completely disregard the hyped up tracks that formed most EDM top 10 charts. They have full teams of people dedicated to promoting them so they don’t really need the help of another DJ to do this.</p><p>When you read between the lines and find music that resonates with you and not necessarily conforms to the norm set by pop electronic music then you’ll start finding your true voice. For me, I’ve always been a sucker for afro/latin-american influenced house music, so I decided to specialize myself into old school house music with heavy tribal influences.</p><p>After recording a few shows in this new format, I felt that my product resonated directly with my personality and what I tried to represent as an electronic musician.</p><p><strong>Let Them Know What You’re Doing</strong></p><p>With this approach you’ll realize that many of the artists you support aren’t that popular yet, so they can be a lot more accessible than the big players in the scene. With each episode I recorded, I took the time to contact each and every one of the producers I supported and let them know that they had a secure spot on my show if they released more material. Sometimes, they’ll respond and will want to be more active in your show.</p><p>An example of this is a guest feature track that I wanted to include in my show by a producer that recently has been supported by Pete Tong’s Essential Mix in the legendary BBC Radio 1, I gave it a shot and decided to contact the guy. First, I let him know what I was doing, and after that I asked him if he could record a shoutout for my show. After some waiting, it happened. Now, would I have had the opportunity with bigger DJ’s? You never know, but due to their schedule it’s unlikely.</p><p>Just like that, by using this approach I helped out a very promising up and coming musician, I empowered my show as a platform and I remained true to my own style of music.</p><p><strong>Always Record Yourself</strong></p><p>Many people that start podcasts or mix shows simply don’t record themselves welcoming the listeners to the show and presenting the tracks out. This is due to the fact that we, as music lovers, tend to feel that the music is more than enough to keep the attention of the listener because we freakin’ love the tunes we collected for our audience. This is true for seasoned listeners or for fans of the style of music you play, but for newer fans, it can be a little daunting not to have a connection with the music that they know (i.e. a familiar voice). When you talk in your show, you develop a connection with the listener, a complicity between yourself and them when listening to something that wouldn’t be considered “normal”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*LL-2WcRSWxirvAv2CgkJLA.jpeg" /><figcaption><em>“So you like The Clash, for real?”</em></figcaption></figure><p>If you are starting out, you must record yourself presenting the show, saying who you are and set your voice as an accessory to the music you compiled for your listeners. You don’t have to present each and every track, make some of the music a little mysterious so that the audience keeps listening to your show, as the only channel where they’ll find this kind of music.</p><p><strong>Final Thoughts</strong></p><p>Disruption can be a good thing when you’ve reached a limit creatively that you feel it can’t be averted. You should be having fun when making music and feel that the finished product resonates with who you are, not with what’s trendy this month. I hope my 2 cents on the matter help upcoming DJ’s or even seasoned ones. Right now, I’m finishing up episode #98 for this sunday, taking my time so it comes out the way I want it to be. If you wanna check out the finished results, you can right here:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttp%253A%252F%252Fapi.soundcloud.com%252Fplaylists%252F346563206%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fkarlmontenegro%2Fsets%2Fkarl-montenegro-presents&amp;image=http%3A%2F%2Fa1.sndcdn.com%2Fimages%2Ffb_placeholder.png%3F1510066857&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/8f85f8f9f74d0f1e3ec6a0d833947b28/href">https://medium.com/media/8f85f8f9f74d0f1e3ec6a0d833947b28/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a55ab9ca55b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>