<?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 Terence Lim on Medium]]></title>
        <description><![CDATA[Stories by Terence Lim on Medium]]></description>
        <link>https://medium.com/@terencelimxp?source=rss-2e1d7e332b35------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*eyvvT0k5cwXbHxXDKZke_Q.jpeg</url>
            <title>Stories by Terence Lim on Medium</title>
            <link>https://medium.com/@terencelimxp?source=rss-2e1d7e332b35------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:28:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@terencelimxp/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[Step-by-Step: How to dockerize and deploy a Node.js, Mongo app to Amazon ECS using AWS EC2]]></title>
            <link>https://medium.com/@terencelimxp/step-by-step-how-to-dockerize-and-deploy-a-node-js-mongo-app-to-amazon-ecs-using-aws-ec2-19489632e2d5?source=rss-2e1d7e332b35------2</link>
            <guid isPermaLink="false">https://medium.com/p/19489632e2d5</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Terence Lim]]></dc:creator>
            <pubDate>Sun, 15 Sep 2019 15:49:50 GMT</pubDate>
            <atom:updated>2019-09-15T15:52:38.622Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9t1WtPkCe23NOURemIKmug.png" /></figure><p>10 hours later…I finally got a client’s application live… While my memory is still fresh, I’ve decided to write and share about what I learnt while spending gruelling hours deploying the app. I’ll be focusing on the steps to deploy a basic Node.js app and the little key pointers to take note here and there, to avoid facing the same mistakes I did. And also, what tripped me when setting up to connect to MongoDB Atlas database.</p><p>Of course, if you’re well-versed with everything but would like to take a look at what might be causing your app deployment to fail, feel free to skip to Key-takeaways section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uj0Mk_OKrJ7fhgdhQgJakw.png" /><figcaption>Physical Deployment for Client’s app</figcaption></figure><h3><strong>Table of Contents</strong></h3><p>1. Introduction<br>2. Prerequisites<br>3. Setup Basic Node.js app<br>4. Create Dockerfile<br>5. Build Docker Image<br>6. Create ECR and push Docker Image to it<br>7. Create Cluster<br>8. Create Task Definition &amp; Service<br>9. Key-takeaways<br>10. Conclusion</p><h3><strong>Introduction</strong></h3><p>Docker enables us to rapidly deploy server environments in “containers.” These containers allow us to easily package up an <strong>application</strong> with all of the parts it needs, such as libraries and other dependencies, and ship it all out as one package. For more information on Docker, you may visit <a href="https://docs.docker.com/">here</a>.</p><h3>Prerequisites</h3><p>- Install <a href="https://docs.npmjs.com/downloading-and-installing-node-js-and-npm">NPM &amp; Node.js</a><br>- Install Docker (for <a href="https://docs.docker.com/docker-for-mac/install/">Mac Users</a> , for <a href="https://docs.docker.com/docker-for-windows/install/">Windows Users</a>)<br>- Sign up for AWS account<br>- Setup <a href="https://aws.amazon.com/cli/">AWS CLI</a></p><h3>Setup Basic Node.js app</h3><p>Through the terminal, go to the directory where you want the application to be stored.</p><pre>Run the following commands in your terminal<br>// create directory<br>mkdir nodejs-ecs-app</pre><pre>// change to created directory<br>cd nodejs-ecs-app</pre><pre>// initialize npm<br>npm init -y</pre><pre>// install express<br>npm install express</pre><pre>// create server.js file<br>touch server.js</pre><p>Then, through a code editor, open the server.js file and paste the code below into it.</p><pre>const express = require(&#39;express&#39;)</pre><pre>const app = express()<br>app.get(&#39;/&#39;, (req, res) =&gt; {<br>    res.send(&#39;Hello world from a Node.js ECS tutorial app!&#39;)<br>});</pre><pre>app.listen(3000, () =&gt; {<br>    console.log(&#39;Server is up on 3000&#39;)<br>});</pre><p>Then, run node server.js in your terminal and go to <a href="http://localhost:3000/">http://localhost:3000</a> to check if everything is setup correctly. If it is, you should get Hello world from a Node.js ECS tutorial app!displayed in your browser.</p><h3>Create Dockerfile</h3><p>A <strong>Dockerfile</strong> is a text document that contains all the commands a user could call on the command line to assemble an image.</p><p>In the terminal, run touch Dockerfile.</p><p>Then, through a code editor, open the Dockerfile file and paste the code below into it.</p><pre># Usually to select particular version instead of latest<br>FROM node:12.9.0 as base</pre><pre>RUN mkdir -p /srv/app<br>COPY . /srv/app<br>WORKDIR /srv/app</pre><pre># Install production dependencies<br>RUN npm install --production</pre><pre># Expose port for access outside of container<br>ENV PORT 3000<br>EXPOSE $PORT</pre><pre>CMD [&quot;node&quot;, &quot;server.js&quot;]</pre><p>Every Dockerfile starts with a base image as its foundation. And here, we get the official <a href="https://hub.docker.com/_/node/">Node.js</a> image hosted on Dockerhub.</p><ul><li>Let’s start our Dockerfile with FROM, which initializes a new build stage and sets the Base Image to be used.</li><li>Then, the RUN instruction will execute any commands in a new layer on top of the current image and commit the results. The resulting committed image will be used for the next step in the Dockerfile. Here, we created a subdirectory /srv/app that will hold our application code within the docker image.</li><li>Next, the WORKDIR instruction sets the working directory for any RUN, CMD, ENTRYPOINT, COPY and ADD instructions that follow it in the Dockerfile. Now, our working directory is /src/app.</li><li>Then, the COPY instruction copies new files or directories from &lt;src&gt; and adds them to the filesystem of the container at the path &lt;dest&gt;, in the following format COPY &lt;src&gt; &lt;dest&gt;.</li><li>Next, the EXPOSE instruction informs Docker that the container listens on the specified network ports at runtime. The specified port is 3000 here.</li><li>Lastly, theCMD instruction is used to tell Docker how to run our application. Since this is a Node.js app, we use node server.js. If it’s a Python app, then it could be eg. python server.py.</li></ul><h3>Build Docker Image</h3><p>Now that we have setup our Dockerfile, let’s build the image by running the command below in your terminal (in the same directory as your Dockerfile).</p><pre>docker build -t nodejs-ecs-app .</pre><p>If the docker build ran successfully, you should see these last 2 lines being printed (yours may not be 25ad0c5ef92c),</p><pre>Successfully built 25ad0c5ef92c<br>Successfully tagged nodejs-ecs-app:latest</pre><h3>Create ECR and push Docker Image to it</h3><ul><li>Go to the <a href="https://console.aws.amazon.com/ecs/home?region=us-east-1#/repositories">ECS Repositories page</a>.</li></ul><p>If you don’t have any repos yet, you will see the following.</p><ul><li>Click the <em>Get Started</em> button</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LcO8NPpW9b8lBlzll_-kOA.png" /><figcaption>AWS ECR</figcaption></figure><ul><li>At the Repositories page, click the <em>Create repository</em> button</li><li>Create a new repo called <em>nodejs-ecs-app</em></li></ul><p>When finished, you should see something like the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlCUXjAg-Br3gOOpUpMUxw.png" /><figcaption>After creating a repo on ECR</figcaption></figure><p>Before following the instructions given on AWS console to build, tag and push our Docker image, let’s ensure the AWS CLI is able to connect with your AWS account.</p><p>Run aws configure in your terminal and it should prompt the following.</p><pre>AWS Access Key ID [********************]:<br>AWS Secret Access Key [********************]:<br>Default region name [whatever region you setup in]:<br>Default output format [None]:</pre><p>Once the above is ensured, the following commands are to be run in the terminal.</p><ul><li>Retrieve the Docker login command that you can use to authenticate your Docker client to your registry</li></ul><pre>aws ecr get-login --no-include-email</pre><p>The above command prints the docker login command you need with your credentials for logging into ECR. Copy and paste, then press enter to log in.</p><p>Since we’ve already built our Docker image in the previous step, let’s head straight to tagging the image with a keyword so that we can push the image to the repo we created on AWS ECR.</p><p>Based on the repo I created, the command goes like this.</p><pre>docker tag nodejs-ecs-app:latest 721321647758.dkr.ecr.us-east-2.amazonaws.com/nodejs-ecs-app:latest</pre><p>Lastly, push the image to our AWS ECR repository.</p><pre>docker push 721321647758.dkr.ecr.us-east-2.amazonaws.com/nodejs-ecs-app:latest</pre><h3>Create Cluster</h3><ul><li>Go to the <a href="https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/clusters">ECS Clusters page</a>.</li></ul><p>If you don’t have any clusters yet, you will see the following.</p><ul><li>Click the <em>Create Cluster </em>button</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MzTDtn_WixUkD6AtPdeorA.png" /><figcaption>AWS ECS Cluster</figcaption></figure><p>Since we’ll be using EC2 to host our app, choose either EC2 Linux + Networking or EC2 Windows + Networking.</p><p>Next, set the following configurations.</p><ul><li>Cluster name: nodejs-ecs-cluster</li><li>EC2 instance type: t2-micro</li><li>Number of instances: 1</li><li>Key pair: None</li><li>VPC: New</li></ul><p>You may vary the size of the instance based on the size of your application. Here, we’ve selected the smallest. The smaller the size of your instance type, the cheaper it is to use (You’ll get billed monthly!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDu80DorIQI140AT2iZYtg.png" /><figcaption>After creating a cluster on ECS</figcaption></figure><p>Here, you may click on both the Service and Task tab. You’ll realise there is nothing running under them. Let’s head on to the final step!</p><h3>Create Task Definition &amp; Service</h3><ul><li>Go to the <a href="https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/taskDefinitions">ECS Task Definitions page</a>.</li></ul><p>If you don’t have any clusters yet, you will see the following.</p><ul><li>Click the <em>Create new Task Definition </em>button</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iEro3WXhvUinJRtdKC5iow.png" /><figcaption>AWS ECS Task Definition</figcaption></figure><p>Select EC2 option for launch type compatibility.</p><p>Next, set the following configurations.</p><ul><li>Task Definition Name: nodejs-ecs-task</li></ul><p>Click Add Container and put in the necessary details. Image would be the previous image name we pushed to AWS ECR (below is my own image).</p><ul><li>Container name: nodejs-ecs-app</li><li>Image: 721321647758.dkr.ecr.us-east-2.amazonaws.com/nodejs-ecs-app:latest</li><li>Port mappings: 80 (Host port) -&gt; 3000 (Container port)</li><li>Environment variables required (especially in production apps)</li><li>Under Storage and Logging, select Auto-configure CloudWatch Logs. This allows you to see logs on your EC2 instance running app and easily debug if there’s any errors. The CloudWatch logs can be found <a href="https://us-east-2.console.aws.amazon.com/cloudwatch/home?region=us-east-2">here</a>, when you click on the Logs tab on the left-side table.</li><li>Next, when everything is set, press Add.</li></ul><p>Lastly, hit Create to create the Task Definition.</p><p><strong>WE’RE ALMOST THERE!!</strong></p><ul><li>Go to the <a href="https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/taskDefinitions">ECS Task Definitions page</a>.</li><li>Check the nodejs-ecs-task<em> </em>and click Actions, then select Create Service.</li></ul><p>Next, set the following configurations.</p><ul><li>Launch type: EC2</li><li>Service name: nodejs-ecs-service</li><li>Number of tasks: 1</li></ul><p>Click Next step with default configurations all the way till the Review step. You should notice that your cluster on the review page is set to the cluster you created earlier, nodejs-ecs-cluster. Once everything has been set, click Create Service.</p><p>Once there’s indication that the service has been successfully created,</p><ul><li>Go to Cluster (through a link from the service we just created) &gt; EC2 instances &gt; Click on the container instance to reveal the public DNS.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jSqoU0M6XtT5-2Gb0tIxqA.png" /><figcaption>Container Instance of our deployed app</figcaption></figure><ul><li>Visit the public DNS to view the deployed app!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZjpBs9hvJ3y1E7psMniIZQ.png" /><figcaption>Deployed app through the web browser!</figcaption></figure><h3>Key-takeaways</h3><ul><li>Add CloudWatch logs (for easy debugging).</li><li>Add <em>0.0.0.0/0</em> to the whitelist to be able to connect from any IP. [If you’re planning to use external MongoDB cloud databases eg. MongoDB Atlas]</li><li>Ensure that MongoDB Atlas connection string used in your app is 100% matching, even an additional / at the last index can trip your app up (Happened to me…).</li><li>Add production environment variables through Task Definition &amp; use <a href="https://www.npmjs.com/package/dotenv">dotenv</a> to access them in your production application.</li></ul><h3>Conclusion</h3><p>As always, I hope this post has been useful. Feel free to share this post to anyone who may benefit from it!</p><p>If you have any questions, please feel free to leave a comment below.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19489632e2d5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Ease of Web-scraping with Python]]></title>
            <link>https://medium.com/@terencelimxp/the-ease-of-web-scraping-with-python-5ffabaddc21e?source=rss-2e1d7e332b35------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ffabaddc21e</guid>
            <category><![CDATA[scraping]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Terence Lim]]></dc:creator>
            <pubDate>Sat, 13 Apr 2019 00:50:38 GMT</pubDate>
            <atom:updated>2019-04-13T00:50:38.059Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0I7VXNRl1YiAcxCSY2lI3w.png" /></figure><p>Day-in-day-out, we face a myriad of tasks at work, and sometimes even from friends. Not too long ago, a friend of mine approached me to help with a task her manager assigned her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/276/1*u9HSM8jhMankDXZVYdyiZw.png" /><figcaption>Column of company names and… (please fill in the blanks)</figcaption></figure><p>The task was simple, to find out the location of all Headquarters in a list of companies. The list consisted of approximately 1300 companies.</p><p>Just a little disclaimer first, in case you guys are wondering how could my friend just throw her job to me! My friend is actually really hardworking. She actually spent 5 days manually searching google for each company’s information and keying them in one at a time, to the excel spreadsheet. But unfortunately… she lost all her data because she forgot to save. A very costly mistake, oops! (Lesson 1: Always save your work at timely intervals)</p><p>She read online that it can be done with Python scraping but with no experience in it, she reckon that would take her too much time. With her deadline just round the corner, she had no choice but to ask around for help. When she approached me, I was really excited about it, since I could put what I’ve learnt previously to good use.</p><p>Alright, enough story-sharing, let’s get down to scraping!</p><h3><strong>Getting Started</strong></h3><p>Make sure you have Python on your machines before we begin.</p><p><strong>Mac Users</strong><br>Python comes pre-installed on Mac OS X so it is easy to start using. Open up the terminal and type python —-version . You should be able to see your Python version pop-up.</p><p><strong>Window Users<br></strong>Python is not usually installed on Windows, so you may download it <a href="https://www.python.org/downloads/">here</a>.</p><p>Next, for scraping, we will utilize the BeautifulSoup library.<br>So friends, open up your terminal and type:</p><pre>pip install beautifulsoup4</pre><p>Before jumping into scraping websites, you should first familiarize yourself with HTML tags.</p><ol><li>All HTML documents must start with a document type declaration: &lt;!DOCTYPE html&gt;.</li><li>The HTML document itself begins with &lt;html&gt; and ends with &lt;/html&gt;.</li><li>The visible part of the HTML document is between &lt;body&gt; and &lt;/body&gt;.</li><li>HTML headings are defined with the &lt;h1&gt; to &lt;h6&gt; tags.</li><li>HTML paragraphs are defined with the &lt;p&gt; tag.</li><li>HTML links are defined with the &lt;a&gt; tag.</li></ol><p>These are just some basic tags, and there are many more such as HTML table with &lt;table&gt; tag, table row with &lt;tr&gt; tag etc. Read all about them on W3Schools website <a href="https://www.w3schools.com/HTML/">here</a>!</p><h3><strong>Take note</strong></h3><ol><li>Before scraping any website, ensure you’ve checked through their Terms and Conditions for the legal use of their data. Some websites also have mechanisms in place to prevent crawling of information. Remember to ask for permission if necessary!</li><li>Layout of websites may change over-time, meaning HTML tags may change and your web-scraper may not work anymore. (Why? More information on this later!)</li><li>Do not crawl data too aggressively on the website as you may crash it.</li></ol><p><strong>Analyzing the Web-Page</strong></p><p>As mentioned earlier, it is vital to check out the HTML tags prior to scraping. Let’s start with a simple page from <a href="https://www.glassdoor.com/glassdoor">Glassdoor</a> as an example. We can easily do that by right-clicking on any page and clicking the inspect button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xmmV7cvSOPvle_kKSl2A3w.png" /></figure><p>By simply hovering your cursor around the webpage, you will be able to find the respective HTML tag that nests the information you need.</p><p>From the DevTools view, under Elements section, we can see that there are multiple similar HTML tags &lt;div class=“infoEntity”&gt;. How can we then ensure we are getting the correct information we want?</p><p>Fear not, and let’s take a look at the code!</p><h3><strong>Code!!!</strong></h3><p>Before starting, let’s import all the libraries we’ll need.</p><pre>import requests<br>from bs4 import BeautifulSoup as BS</pre><p>Next, we’ll utilize the requests library simple API to get the HTML of a webpage.</p><pre>r = requests.get(&#39;http://www.example.com&#39;, timeout=10)</pre><p>It is advisable to set a timeout, to stop waiting for a response after a given number of seconds with the timeout parameter. Failure to do so can cause your program to hang indefinitely.</p><p>Then, we’ll access Response object, r body as bytes, by r.content and parsing the document with lxml, since CSS selectors are all we need, and also lxml is way faster than the other options.</p><pre>page = BS(r.content, &#39;lxml&#39;)</pre><p>Next, we’ll extract a list of all the information nested within the similar &lt;div class=“infoEntity”&gt; HTML tags. This can be done easily with BeautifulSoup’s findall API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*zU7zNNzzx3sFvqbnef2vkQ.png" /><figcaption>Expanding each &lt;div&gt; tag further…</figcaption></figure><p>As we expand each &lt;div&gt; tag further, we’ll notice a similar pattern, where the “headers” are found within the &lt;label&gt; tags and the information we want are found within the &lt;span&gt; tags. Let’s tackle this one step at a time.</p><p>We’ll extract the text from these HTML tags first.</p><pre># Returns a list of tags<br>relevant_tags = page.find_all(&#39;div&#39;, {&#39;class&#39;: &#39;infoEntity&#39;})<br>relevant_info = []<br>for tag in relevant_tags:<br>    relevant_info.append(tag.get_text())</pre><pre># Never forget list comprehension<br>relevant_info = [tag.get_text() for tag in page.find_all(&#39;div&#39;, {&#39;class&#39;: &#39;infoEntity&#39;})]</pre><pre># How relevant_info should look like<br># [&#39;Websitewww.glassdoor.com&#39;, &#39;HeadquartersMill Valley, CA&#39;, &#39;Size501 to 1000 employees&#39;, &#39;Founded 2007&#39;, ...etc]</pre><p>Since we are only interested in the location of the headquarters, let’s extract only the string with “Headquarters” in it.</p><pre># Get string with &#39;Headquarters&#39; in it<br>hq_string = [hq for hq in relevant_info if &#39;Headquarters&#39; in hq][0]</pre><pre># hq_string = &quot;HeadquartersMill Valley, CA&quot;</pre><pre># Extract only the location<br># Without getting index 1, it returns [&#39;Head&#39;, &#39;Mill Valley, CA&#39;]<br>hq_location = re.split(&#39;quarters&#39;, hq_string)[1]</pre><p>And there you go! The information you need!</p><p>Not forgetting, how should you extract the information into the excel spreadsheet?</p><p>We can utilize the popular Pandas library. Install it using pip install pandas .</p><pre># Import pandas<br>import pandas as pd</pre><pre>&quot;&quot;&quot;<br>Reading your existing company names ONLY csv file; Ensure your code and csv file is in the same directory if you&#39;re using the code format below<br>&quot;&quot;&quot;</pre><pre>companies_df = pd.read_csv(&#39;companies.csv&#39;)<br>companies_df.loc[companies_df[&#39;company&#39;] == &#39;glassdoor&#39;, &#39;headquarters&#39;] = hq_location<br>companies_df.to_csv(&#39;finishedmywork.csv&#39;)</pre><h3><strong>Advanced Usage</strong></h3><p>Well, let’s say if you had to further scrape more web-links nested within a HTML page, I’d recommend creating a Class object to store the information, so that you can easily access the information again.</p><pre>class Company:<br>  def __init__(self, name, google_query):<br>    self.name = name # name of the company you just scraped<br>    self.nested_urls = [] # list of urls found on first visited page<br>      <br>  def store_nested_url(https://medium.com/self,%20url):<br>    self.nested_urls.append(url)</pre><pre>def get_all_nested_urls(url):<br>  r = requests.get(&quot;www.example.com&quot;, timeout=10)<br>  first_page = BS(r.content, &quot;lxml&quot;)</pre><pre>  # all &#39;href&#39; tags are within &#39;a&#39; tags<br>  all_a_tags = first_page.find_all(&quot;a&quot;)</pre><pre>  all_href = [url[&#39;href&#39;] for url in all_a_tags]</pre><p>In such situations, I’d really encourage you to find a way to automate the process since it is cumbersome to perform it manually. Stay tuned for more automation tricks!</p><p>If you have any questions, please feel free to leave a comment below.</p><p><strong>References<br></strong><a href="http://www.w3schools.com/">https://www.w3schools.com</a><br><a href="https://www.crummy.com/software/BeautifulSoup/bs4/doc/">https://www.crummy.com/software/BeautifulSoup/bs4/doc/</a><br><a href="http://docs.python-requests.org/en/master/user/quickstart/">http://docs.python-requests.org/en/master/user/quickstart/</a></p><p>Automate away! ⚙</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ffabaddc21e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>