<?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 Ronald Aug on Medium]]></title>
        <description><![CDATA[Stories by Ronald Aug on Medium]]></description>
        <link>https://medium.com/@ronaldaug?source=rss-1ab0f960c539------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hp3ZnTlKSS4EAbDHq4iRJA.jpeg</url>
            <title>Stories by Ronald Aug on Medium</title>
            <link>https://medium.com/@ronaldaug?source=rss-1ab0f960c539------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:38:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ronaldaug/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[How to Migrate Your Supabase Database from One Project to Another]]></title>
            <link>https://ronaldaug.medium.com/how-to-migrate-your-supabase-database-from-one-project-to-another-963fe0ca4dd7?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/963fe0ca4dd7</guid>
            <category><![CDATA[migration]]></category>
            <category><![CDATA[migrate]]></category>
            <category><![CDATA[postgresql]]></category>
            <category><![CDATA[supabase]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Wed, 23 Apr 2025 07:54:25 GMT</pubDate>
            <atom:updated>2026-01-10T03:06:27.864Z</atom:updated>
            <content:encoded><![CDATA[<h3>Supabase Migration Guide: Moving Data Between Projects</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PRLvL0v8mBdNPVc1BzAhyg.png" /></figure><p>Supabase makes it easy to spin up fully managed PostgreSQL databases in seconds — but what if you need to migrate your entire database from one Supabase project to another?</p><p>Maybe you want to:</p><ul><li>Clone your production database into staging for testing</li><li>Migrate data between different environments or teams</li><li>Move everything from a temporary project to a permanent one</li></ul><p>In this guide, I’ll walk you through how to properly migrate your Supabase database (schema and data) from one project to another using PostgreSQL tools like pg_dump and psql.</p><h3>Installing PostgreSQL on macOS (with Homebrew)</h3><p>If you haven’t installed the PostgreSQL CLI tools yet, this is how I installed them on my Mac using Homebrew:</p><pre>brew install postgresql</pre><p>If you’re on Windows or Linux, you’ll need to find the appropriate installation method for your system.</p><h3>Step 1: Dump the Source Project</h3><p>You’ll want to extract both the <strong>schema</strong> and the <strong>data</strong> from your original Supabase project.</p><h3>Dump the Data</h3><p>This command will dump the whole database.</p><pre>pg_dump -Fc &quot;postgresql://&lt;user&gt;:&lt;password&gt;@&lt;source-host&gt;:5432/postgres&quot; &gt; full_backup.dump</pre><p>Now you have full_db.dump.</p><h3>Step 2: Import into the Destination Project</h3><p>With your dumps ready, it’s time to move everything into your <strong>new Supabase project</strong>.</p><h3>Restore the database</h3><p>Run the following command to restore all of your data into the new database:</p><pre>pg_restore -d &quot;postgresql://&lt;user&gt;:&lt;password&gt;@&lt;destination-host&gt;:5432/new_db&quot; full_db.dump</pre><p>At this point, your migration is complete.</p><h3>Handling Version Mismatches</h3><p>Sometimes when you try to dump your Supabase database, you might run into a version mismatch error like this:</p><pre>pg_dump: error: server version: 15.8; pg_dump version: 14.17 (Homebrew)<br>pg_dump: error: aborting because of server version mismatch</pre><p>This happens when the version of the pg_dump tool on your machine is different from the PostgreSQL server version that Supabase is using.</p><p>To fix it, uninstall the mismatched version and install the correct one:</p><pre>brew uninstall postgresql<br>brew install postgresql@15    # Match Supabase server version<br>brew link postgresql@15 --force</pre><p>After that, try running your dump commands again and the error should go away.</p><h3>Pro Tips</h3><ul><li>Always test your migration on a new Supabase project before running it in production</li><li>Be cautious when importing schemas into an existing project — it may override existing tables</li><li>Supabase auto-generates roles and policies — don’t overwrite these unless you know what you’re doing</li></ul><h3>Conclusion</h3><p>Migrating between Supabase projects is straightforward when you use the right tools. With pg_dump and psql, you can move both your schema and your data confidently and cleanly.</p><p>Supabase gives you the full power of PostgreSQL, and with a bit of command-line knowledge, you can migrate between environments with ease.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=963fe0ca4dd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Clean Approach to Supabase Policies: Dynamic Role-Based Access Control (RBAC)]]></title>
            <link>https://ronaldaug.medium.com/a-clean-approach-to-supabase-policies-dynamic-role-based-access-control-rbac-4dadf68f108a?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dadf68f108a</guid>
            <category><![CDATA[supabase]]></category>
            <category><![CDATA[permission]]></category>
            <category><![CDATA[roles]]></category>
            <category><![CDATA[rbac]]></category>
            <category><![CDATA[refactor]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Fri, 18 Apr 2025 07:54:46 GMT</pubDate>
            <atom:updated>2025-07-22T05:06:02.683Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Refactor your messy Postgres policies into one clean, scalable pattern with just 4 rules per table.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*teDleSSU5S0Z114_nG-fwQ.jpeg" /></figure><h3>The Problem: Supabase Policies Can Get Messy, Fast</h3><p>If you’re building anything beyond a simple todo app, you’ll probably need:</p><ul><li>Multiple user roles (e.g. admin, manager, employee)</li><li>Role-specific access control (e.g. only managers can approve leave)</li><li>Permissions that evolve as your app grows</li></ul><p>In Supabase, this quickly leads to <strong>dozens of policies per table</strong>, like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/389c12241b427ebae31b416c6d95b1f9/href">https://medium.com/media/389c12241b427ebae31b416c6d95b1f9/href</a></iframe><p>This becomes <strong>unmanageable</strong>, especially when:</p><ul><li>You want to add new roles</li><li>You want to change permissions</li><li>You don’t want to write SQL every time</li></ul><h3>The Goal: Centralized, Dynamic RBAC in Supabase</h3><p>We want to move to a setup where:</p><ul><li>✅ All roles and permissions live in tables (roles, permissions, etc.)</li><li>✅ Admins can manage them via UI (no SQL needed)</li><li>✅ Each table only needs 4 simple policies (CRUD)</li><li>✅ The logic for access control is centralized in one place</li></ul><h3>Step 1: Define Your Role Tables</h3><p>Create these tables in your Supabase schema:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/53947a90b5d0829d41eb96216b7a27be/href">https://medium.com/media/53947a90b5d0829d41eb96216b7a27be/href</a></iframe><h3>Step 2: Create a Dynamic authorize() Function</h3><p>This function checks if the current user is allowed to perform a specific action on a given resource (like leaves.read).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bcd7190fec0644edaab997a55c334d27/href">https://medium.com/media/bcd7190fec0644edaab997a55c334d27/href</a></iframe><h3>Step 3: Write Just 4 Policies Per Table</h3><p>No more role-specific policy clutter. Just plug in the dynamic authorize() function.</p><p>For example, for the leaves table:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f3222ba9393acf20c298cab1af1fd442/href">https://medium.com/media/f3222ba9393acf20c298cab1af1fd442/href</a></iframe><p>That’s it! You now have full RBAC powered by SQL and backed by a UI-manageable schema.</p><p>Here’s a cleaner version:</p><p>Sometimes calling</p><h4>supabase().rpc(‘authorize’)</h4><p>can fail with an error like:</p><h4>{<br> “code”: “42501”,<br> “message”: “permission denied for schema public”,<br> “details”: null,<br> “hint”: null<br>}</h4><p>To fix this, grant the `authenticated` role permission to use the `public` schema and execute the `authorize` function:</p><h4>GRANT USAGE ON SCHEMA public TO authenticated;<br>GRANT EXECUTE ON FUNCTION public.authorize(text) TO authenticated;</h4><p>If the permission issue persists, consider trying this solution on github.</p><p><a href="https://github.com/orgs/supabase/discussions/35757">permission denied for table · supabase · Discussion #35757</a></p><h3>Bonus Tips</h3><ul><li>🛡 You can add a superadmin flag instead of checking the role name</li><li>🔁 Want multiple roles per user? Just change user_roles to a many-to-many model</li><li>🚀 Want even more flexibility? Add granular scopes like can_approve, can_export, etc.</li></ul><h3>The Result</h3><p>BeforeAfterDozens of policiesJust 4 per tableHard-coded role logicCentralized in authorize()SQL-only updatesUI-based permission controlNo admin overviewAdmins can see &amp; update roles/permissions easily</p><h3>Conclusion</h3><p>This RBAC pattern gives you:</p><ul><li>Clean, maintainable policies</li><li>A clear separation of concerns</li><li>Flexibility to scale roles and permissions over time</li><li>Admin-friendly UI possibilities</li></ul><blockquote><em>✨ Say goodbye to policy sprawl. Say hello to scalable, centralized access control.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dadf68f108a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chatty Form, Form to Conversational Chat Bot]]></title>
            <link>https://ronaldaug.medium.com/form-bee-form-to-conversational-chat-bot-ad69f720fdb7?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad69f720fdb7</guid>
            <category><![CDATA[google-forms]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[chat]]></category>
            <category><![CDATA[submission]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Tue, 30 Apr 2024 14:25:02 GMT</pubDate>
            <atom:updated>2024-12-12T06:28:02.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_3B-EQuDP9pouegymyM23A.jpeg" /></figure><p>Hey there! Tired of using those traditional web forms? Meet “Chatty Form” — a trendy WordPress plugin revolutionizing the form-filling game! Instead of mundane forms, Chatty Form presents a chat bot interface that makes the process interactive and enjoyable.</p><p><a href="https://chattyform.com/">Chatty Form</a></p><h3>Chat Bot Magic</h3><p>Chatty Form’s chat bot UI is where the magic unfolds. It engages you with questions in a chat-style format, akin to those trendy chat bots on websites. This approach makes filling out forms feel more natural and fun, eliminating the daunting task of starting with a blank form.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/788/1*yBm51dhfmRqXzUsH-HSQoQ.png" /></figure><h3>Customize and Personalize</h3><p>Chatty Form offers the flexibility to personalize your chat bot experience. You can customize the icon, choose your preferred colors, craft a welcoming message, incorporate sounds, and design custom thank-you messages. It’s like having your personalized chat bot companion tailored to your taste.</p><h3>Stand Out from the Crowd</h3><p>Chatty Form goes beyond being just a form plugin; it’s a dynamic way to gather data that distinguishes you from the rest. Unlike tools like Google Forms or Typebot, Chatty Form’s conversational style enhances engagement and completion rates. Moreover, its seamless integration with WordPress simplifies data management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s5zsfU6Pe8nU5V5-3Flr1Q.png" /></figure><h3>Free and Feature-Packed</h3><p>What’s even more exciting about Chatty Form is that it’s not only fun and engaging but also free! — you can enjoy all the perks of this chat bot plugin without spending a penny. Additionally, it offers features like email sending, unlimited form creation, limitless submissions acceptance, and seamless integration with third-party apps through webhooks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H1QV--vHU21uq2oMGBsTAw.png" /></figure><h3>Wrap Up</h3><p>Don’t just take our word for it — why not give it a spin yourself? Experience the Chatty Form<a href="https://chattyform.com/"> demo here </a>and witness how it can transform your mundane forms into an engaging chat bot adventure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad69f720fdb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating Cockpit CMS v1 to v2]]></title>
            <link>https://ronaldaug.medium.com/migrating-cockpit-cms-v1-to-v2-90376a64df22?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/90376a64df22</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[migrating]]></category>
            <category><![CDATA[cockpit-cms]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Mon, 10 Apr 2023 05:43:07 GMT</pubDate>
            <atom:updated>2023-04-10T05:43:07.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRAVFYO1ED0V2q2AdiS7jw.jpeg" /></figure><p>Cockpit CMS is an open-source, headless content management system that allows developers and content creators to easily manage and publish content for their websites and applications.</p><p>This article will explain the process of migrating from Cockpit CMS version 1 to version 2.</p><p>— — -</p><blockquote>Disclaimer: This article is based on my own experience of migrating from Cockpit v1 to v2. Therefore, I recommend backing up your storage folder before attempting any changes, and note that this guide is only for the <strong>Collection Data and Cockpit default DB (SQLite)</strong>.</blockquote><blockquote>For the purposes of this guide, I will be using a collection called contact.</blockquote><ul><li>1. Prepare SQLite data</li><li>2. Create Models in v2</li><li>3. Delete newly created collection table</li><li>4. Rename SQLite table</li><li>5. Append “_state” property to collection document</li></ul><h3>1. Prepare SQLite data</h3><p>First, copy the collections.sqlite file from the storage/data folder of v1, rename it content.sqlite, and replace the content.sqlite file in the storage/data folder of v2.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EAHsPdWGsFmsQUL40szKRA.png" /></figure><blockquote>Make sure to backup the content.sqlite file to avoid losing any data.</blockquote><p>— — -</p><h3>2. Create Models in v2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HZBt0DbT5aMvqRwqXMiiDQ.jpeg" /></figure><p>Unfortunately, you cannot automatically export and import your v1 collections/fields into Cockpit v2. You must manually create the collections and their fields in v2. After creating the model, PHP schemas will be generated in the storage/content folder.</p><blockquote>Ensure that the collection name and fields are the same as in v1.</blockquote><p>— — -</p><h3>3. Delete newly created collection table</h3><p>Using a <a href="https://sqlitebrowser.org/dl/"><strong>SQLite database browser</strong></a>, open the content.sqlite file. In my case, the model name is contact, so there will be two tables with similar names: contact (v1 table) and collections_contact (v2 table, created in step 2).</p><p>Delete the collections_contact table as we only want the PHP schemas under storage/content and will use the contact table from v1.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-NMzspV4CkQUa0bHJNFNsQ.png" /></figure><p>— — -</p><h3>4. Rename SQLite table</h3><p>As we will be using the contact table and its data from v1, we can now rename it to collections_contact according to the v2 table format. In my case, I renamed the table from contact to collections_contact. If you have a different model name, it will be something like collections_{model_name}.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cbwjpXI6Sm-YFe7UIdGI6Q.png" /></figure><p>— —</p><h3>5. Append “_state” property to collection document</h3><p>After renaming the table, you would see the collections data is in the Cockpit v2 dashboard.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bQyom3d3P--s-8gp1IrcXg.png" /></figure><p>However, if we try to get the data through API, it will only return a blank array because all content is in <strong>Draft</strong> status.</p><p>This happens because _state is a new property in Cockpit v2 that determines the status of content, such as Draft or Published.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZPRCGtsaNN6WxxXZ_Hz9Qw.png" /></figure><p>As we are migrating the content from v1, all content objects are missing the _state property, causing Cockpit to assume that the _state value is false and keep all the content in draft status. To fix this, we need to append a key and value object to every content object (document under collections_contact table).</p><p>We can achieve this by running the following SQLite query, replacing collections_contact with your table name:</p><pre>UPDATE collections_contact<br>SET document = substr(document, 1, length(document)-1) || &#39;,&quot;_state&quot;:1}&#39;;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s8OxEU8C6VVRI_G2RBREYQ.png" /></figure><p>This query updates the document column for all rows in the collections_contact table by replacing the last character } with ,&quot;_state&quot;:1}.</p><blockquote>This is a way of appending a key and value to a JSON object.</blockquote><p>After adding &quot;_state&quot;:1 to the documents, we can now get the content through API, and all the content will be in <strong>Published</strong> status.</p><p>I hope this guide helps you migrate your Cockpit CMS from v1 to v2 successfully.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90376a64df22" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your .htaccess rule doesn’t work on SiteGround hosting?]]></title>
            <link>https://ronaldaug.medium.com/why-your-htaccess-rule-doesnt-work-on-siteground-hosting-d2a4fbb55ecb?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2a4fbb55ecb</guid>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[htaccess]]></category>
            <category><![CDATA[siteground]]></category>
            <category><![CDATA[apache]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Sun, 11 Dec 2022 08:44:09 GMT</pubDate>
            <atom:updated>2022-12-11T09:19:28.676Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why your .htaccess rule doesn’t work on SiteGround hosting?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q6NtDs9gm9Kk7a8Lh-bpLg.jpeg" /></figure><p>I was stuck for a day setting up the .htaccess file on Siteground hosting.<br>In fact, SiteGround serves the static asset files on top of Nginx to make the website faster. However, one of my .htaccess rules is to protect media files from direct access and it no longer trigger due to <strong>NGINX DIRECT DELIVERY.</strong></p><p>This is a warning message from SiteGround.</p><blockquote>With NGINX Direct Delivery we will serve most of the static resources of your website (images, JS, CSS and others) directly through NGINX to achieve the fastest possible loading time. It works for all kind of applications without additional customisation.</blockquote><blockquote>For best results we highly recommend having NGINX Direct Delivery enabled at all times. However, if you need to use custom caching .htaccess rules for your static content you may need to switch it off.</blockquote><p>To make my .htaccess rule work as expect, I had to turn off <strong>NGINX Direct Delivery</strong> option under the <strong>speed &gt; caching</strong> of SiteGround’s setting.</p><blockquote>Make sure to <strong>flush the dynamic cache</strong> before testing the rule again.</blockquote><p><em>Just sharing the issue and solution what I encountered today. Thanks for reading.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2a4fbb55ecb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP restful API with sim-rest ( only 10 KB )]]></title>
            <link>https://ronaldaug.medium.com/php-restful-api-with-sim-rest-only-10-kb-422da0738e30?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/422da0738e30</guid>
            <category><![CDATA[lightweight]]></category>
            <category><![CDATA[php]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[sim-rest]]></category>
            <category><![CDATA[restful]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Tue, 07 Apr 2020 03:44:17 GMT</pubDate>
            <atom:updated>2021-05-06T07:07:59.895Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iv8Ar5XBJ56z3FueSa4l5A.png" /></figure><blockquote>What is sim-rest?</blockquote><blockquote><strong>sim-rest</strong> is a super lightweight, file-based API and it will help you build an API under a few minutes.</blockquote><blockquote>Why another library?</blockquote><blockquote>As a frontend developer, I was looking for a simple API or Headless API to connect with my client side JS frameworks such as React, Vue &amp; Angular but most of the them are very big, with many dependencies and lots of configurations. That’s why I tried to build a very simple one and it became <strong>sim-rest</strong>. Hope it helps you.</blockquote><p>These are the amazing features of <strong>sim-rest</strong>.</p><ul><li>Only 10 KB (gzip)</li><li>PHP 7+</li><li>Router (GET, POST, DELETE, PUT)</li><li>Pass parameters via router</li><li>JSON file database</li><li>JWT like token-based authentication</li><li>Auth protected routes</li><li>Eloquent like DB selector</li><li>Less configuration</li><li>Zero dependencies</li></ul><p>Ok let’s get started</p><p>Firstly download or clone <strong>sim-rest</strong> <a href="https://github.com/ronaldaug/sim-rest">here</a></p><p>After downloading, cd into <strong>sim-rest</strong> project folder</p><p>Run this command in the terminal and serve <strong>sim-rest</strong> on port 4000</p><pre>php -S localhost:4000</pre><blockquote>Note: I can run this command because I have <strong>php</strong> installed in my machine. If it doesn’t work in your machine, you can also serve <strong>sim-rest </strong>via <strong>xampp</strong> or <strong>mamp</strong> server</blockquote><p>let’s openlocalhost:4000 in the browser.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*vA1bSX_rrC78GnNxRvevOw.png" /></figure><p>If you see as this screenshoot, <strong>sim-rest</strong> is ready on your machine.</p><p>Let’s open index.php and add this code.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/11f41d18463819accef13ed1648fc731/href">https://medium.com/media/11f41d18463819accef13ed1648fc731/href</a></iframe><p>That’s it, you’ve just declared a very simple <strong>GET</strong> request on /test route. Openhttps://localhost:4000/test in the browser and see the magic.</p><p>Let’s make a todo collection API</p><p>To build an API, we have to follow these 3 steps.</p><ul><li>1. Create a collection under <strong>collections</strong> folder</li><li>2. Create a user inside <strong>config.php</strong></li><li>3. Create routes inside <strong>index.php</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y1p7bbR5Aq59ha2zxTcAsg.png" /></figure><h3>Step 1</h3><p>let’s create a new <strong>todo</strong> collection,</p><p>so we have to create <strong>todos.php</strong> file under collections folder and add this below codes.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ce0ae491ff38bbded903886f40532f7/href">https://medium.com/media/2ce0ae491ff38bbded903886f40532f7/href</a></iframe><p>Actually this is a very simple JSON object. But for security reason, we have to add a few lines of php codes at the top of the file to protect from direct access.</p><h3>Step 2</h3><p>Let’s edit <strong>config.php</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/963fac3db2d4143e127f112f1643ec8d/href">https://medium.com/media/963fac3db2d4143e127f112f1643ec8d/href</a></iframe><p>Initially, you’ll see <strong>two users</strong> in <strong>admin</strong> array, here, we can edit or create user (who can access the API).</p><blockquote>Just for tutorial purpose, I’ll keep this <strong>config.php</strong> file as origin.</blockquote><h3>Step 3</h3><p>Let’s create routes inside <strong>index.php</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ed92bc9216b4a09cd562028ddf619486/href">https://medium.com/media/ed92bc9216b4a09cd562028ddf619486/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D6tseAdni_aT2TlsUWHwcw.png" /></figure><p>That’s it! we have a todo API. Let’s give it a try from <strong>postman</strong>.</p><h3>Get the whole todo collection</h3><p>As GET request isn’t protect, we don’t need to provide token. We can simply fetch/todos route to get the whole collection.</p><p>It will return an empty array because recently when we create “todos.php” collection file, we didn’t add any data.</p><h3>Create a todo via API</h3><p>As we’ve declared a <strong>post request</strong> route under <strong>Protected routes</strong> as below. We have to authenticate first. Otherwise, the API won’t allow us to create a new todo.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/64a56e6239d3cded5f9ffb165ffc45f8/href">https://medium.com/media/64a56e6239d3cded5f9ffb165ffc45f8/href</a></iframe><h3>Authentication</h3><p>Let’s send a POST request to <strong>/auth </strong>route and get the <strong>Token</strong>. Here, the request data must be JSON type</p><p>Content-Type: application/json</p><p>Request credential example</p><pre>{<br>  username:&quot;admin1&quot;,<br>  password:&quot;admin1&quot;<br>}</pre><p>If we pass the authentication, the response data will return back as below screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cqi3I9lU13FpkpeVv6ORxA.png" /></figure><p>Now we have a token, it’s time to create a new Todo.</p><p>Grab the <strong>Token </strong>and<strong> </strong>let’s append in the header as<strong> Bearer Token</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6X0_xoXJbJxK-0YxJC-UTQ.png" /></figure><blockquote>In this example, I only add two properties “completed” and “task”. We can add the properties as many as we want.</blockquote><p>Let’s send post request and create a new todo. If it works fine, a requested todo data will return.</p><p>After creating, we can fetch “/todos” route with GET request again, there will be a new todo in a todo collection as below screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*Ezh6z9d03PqK0-EU6HSZYg.png" /></figure><h3>[Updated]</h3><p>There are more features for filtering data like limiting and sorting.</p><h3>Limit</h3><p><strong>Example of limiting 10 items</strong></p><blockquote><a href="https://localhost:4000/todos?limit=10">https://localhost:4000/todos?limit=10</a></blockquote><h3>Sort</h3><p><strong>Example of order by ASC (DESC is default)</strong></p><blockquote><a href="https://localhost:4000/todos?limit=10">https://localhost:4000/todos?sort=</a>ASC</blockquote><h3>Only</h3><p><strong>Example of getting only specific keys</strong></p><blockquote><a href="https://localhost:4000/todos?limit=10">https://localhost:4000/todos?only=</a>title,author</blockquote><p>Thanks for reading this tutorial.</p><p>I hope <strong>sim-rest </strong>would help your frontend work a bit easier.</p><p>This tutorial may not cover all CRUD operations, including PUT,DELETE request, you can still access those information in the documentation.</p><blockquote>For more about <strong>sim-rest </strong>and its’ features, you can read the <a href="https://ronaldaug.gitbook.io/sim-rest/">documentation here</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=422da0738e30" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build a full stack Express GraphQL API with GraphQL Designer in a few minutes.]]></title>
            <link>https://ronaldaug.medium.com/build-a-full-stack-express-graphql-api-with-graphql-designer-in-a-few-minutes-a2f66568acb8?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2f66568acb8</guid>
            <category><![CDATA[express]]></category>
            <category><![CDATA[designer]]></category>
            <category><![CDATA[graphql]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[mongodb]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Sat, 12 Jan 2019 08:33:38 GMT</pubDate>
            <atom:updated>2019-10-06T01:06:56.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FFtDG_tw9hjs6AKtqZatnw.jpeg" /></figure><p>This article is about building an express graphQL API with GraphQL Designer. And this is especially for beginners who want to build an express graphQL API without any coding.</p><blockquote>If you are interested to learn about graphQL, I would suggest you to learn at <a href="https://www.howtographql.com/">HowToGraphQL.com</a>.</blockquote><p>What is GraphQL designer?<br>According to GraphQL designer’s <a href="https://github.com/GraphQL-Designer/graphqldesigner.com">github</a> page,</p><p><a href="http://graphqldesigner.com/"><em>GraphQL Designer</em></a><em> is a prototyping tool to develop full-stack GraphQL applications. With a few simple inputs, GraphQL Designer auto generates code for download, to start and implement your new application including GraphQL root queries, schemas, mutations, and client queries. Also available for download are the NoSQL schemas or SQL build scripts, and a server file.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fny2LJ6w2MoBS5X49XSAqw.gif" /></figure><p>From my understanding, <strong>GraphQL Designer</strong> is a tool to build an express graphQL API in a very short time. <br>And It has these amazing features</p><p>— GD provides 3 different database options ( MongoDB, MySQL, PostgreSQL)</p><p>— GD generates <strong>GraphQL Types, Root Queries, Mutations and Resolvers </strong>out of the box. Not only for the server side schemas, GD also generates client React graphql <strong>Queries and Mutations</strong>.</p><p>— GD is built on top of express and <a href="https://www.npmjs.com/package/express-graphql">express-graphql</a>.</p><p>— You don’t have to write any line of codes. ( MAGIC! 😀)</p><p>— GD is open source and available to download on <a href="https://github.com/GraphQL-Designer/graphqldesigner.com">Github</a>.</p><p>— Export GraphQL API source codes in a single click.</p><p>Before we start playing with GD, let’s take a look to our data structure for the API first.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHDF0wqBbUYV9u8ubgAeYg.png" /></figure><p>This diagram shows <strong>User</strong> and <strong>Post</strong> table with their fields. <em>(Here, we are not going to build a complex data structures because this is just for a tutorial.)</em></p><p>The database has two tables “User and Post”. And there will be a relational field called “Author” to link between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/1*DmP0n-womUwmMSCLntvaXA.gif" /></figure><p>Ok let’s get started with GraphQL designer on <a href="http://graphqldesigner.com/">http://graphqldesigner.com</a>.</p><h3>1. Choose database option.</h3><p>When you first open the GD home page, you will see a popup to choose the database options. You can choose any database that you want. (For this tutorial, I am going to choose MongoDB)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*XEGsxHBgw5VxIGA0F4hBrw.jpeg" /></figure><h3>2. Create tables</h3><p>According to our data structure, we have to create two tables (“User” and “Post”) in the right panel. (Make sure the Table name is <strong>singular</strong>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*-b-KHk6dyJaEtFI3om0elA.jpeg" /></figure><h3>3. Create table fields</h3><p>After you created two tables, let’s click on “<strong>ADD FIELD</strong>” to add more fields.</p><p>(As <strong>ID</strong> is a default field, we don’t have to worry for it).</p><p>Let’s create three different fields <strong><em>(username, email, password) </em></strong>for <strong>User</strong> table.</p><pre>username | String | unique | required<br>email | String | unique | required<br>password | String | required</pre><p>We can specify field types and make them <strong>unique</strong> or <strong>required</strong> by switching the toggles under the field names.</p><p>Again, let’s create four different fields <strong><em>(title, description, tags, author)</em></strong> for <strong>Post</strong> table.</p><pre>title | String | required<br>description | String<br>tags | String<br>author | ID (many to one relation with User)</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*E50Hv0nCvxa2GWhfzVbKQA.jpeg" /></figure><h3>4. Add a r<strong>elational field.</strong></h3><p>Let’s make a relationship between <strong>Post</strong> and <strong>User</strong> table, we have to create a new field name “Author” with “<strong>Many to one</strong>” reference type. ( Here, <strong>many to one</strong> is like- there will be many posts and each post will has a single user(author)).</p><p><em>(If you want to know more about </em><strong><em>many to one </em></strong><em>and</em><strong><em> one to many </em></strong><em>relationships, you can </em><a href="https://stackoverflow.com/questions/4601703/difference-between-one-to-many-and-many-to-one-relationship"><em>read here.</em></a><em>)</em></p><h3>5. Export graphQL schemas and codes.</h3><blockquote>Here, if you have the existing node app, you can copy the schemas from a <strong>CODE</strong> tab and add into your app. But I will go with the entire generated app.</blockquote><p>We can click on <strong>EXPORT CODE</strong> to export GraphQL schemas and codes.<br>It will download a zip file named “<strong>graphql</strong>”.</p><p>Before we start our API server, we have to edit a single file and install required nodejs dependencies.</p><p>Extract the downloaded file and enter into that folder from your <strong>Terminal.</strong></p><pre>cd Downloads/graphql</pre><p>Then, install the dependencies.</p><pre>npm install</pre><p>After the installation is finished, let’s edit <strong>index.js </strong>which is inside the <strong>server</strong> folder. On line 18, set the “<strong>graphiql”</strong> value to <strong>true </strong>as the below screenshot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l7dpVjN_xKL2adUI4S4sPA.jpeg" /></figure><h3>6. Link to MongoDB</h3><p>In the same file, you will see a MongoDB url.</p><blockquote><em>Initially, the default MongoDB url will link to localhost, <br>If you prefer using localhost you can use it, <br>But If you want to use online Mongo database, you can use </em><a href="https://mlab.com/"><em>MLab.com</em></a><em> which provides a free plan for 500MB.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*fW9EpyufZEBkUIKJgUqnOA.jpeg" /></figure><blockquote>Note: Instead of pasting MongoDB url directly inside <strong>index.js</strong>, I would recommend using <strong>dotenv (.env)</strong> file for a better security.</blockquote><p>And run the below command to start the server.</p><pre>npm run start</pre><p>The server will be running on port 4000.</p><h3><strong>7. Add data to MongoDB</strong></h3><p>Before we do something, we need to add the data first because our newly created mongoDB is still a blank.</p><p>So, let’s open</p><pre><a href="http://localhost:4000."><strong>http://localhost:4000</strong></a><strong>/graphql</strong></pre><p>You will see a GraphQL playground called <a href="https://github.com/graphql/graphiql"><strong>Graphiql</strong></a>, which is an in-browser IDE for graphQL queries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*qti1z6_RLovxoqK6YSVlrg.jpeg" /></figure><p>let’s add a new <strong>user </strong>from <strong>graqhiql </strong>IDE, <br>type the below graphql <strong>mutation</strong> inside the left box and press play button. It will add a new user into the database.</p><pre>mutation{<br>  addUser(<br>   username:&quot;John Doe&quot;,<br>   email:&quot;<a href="/service/mailto:john@doe.com">john@doe.com</a>&quot;,<br>   password:&quot;123456&quot;<br>){<br>    id<br>    username<br>    email<br>   }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*fA13qF1oz41Rh2wlZOvgWg.jpeg" /></figure><blockquote><strong>Important</strong>: This is a demo app and I don’t hash the password. If you are building a real world app for production, you must hash the password with “bcrypt” before you store in your database, otherwise anyone can see the user’s passwords.(And this article won’t cover about Graphql Authentication)</blockquote><p>And let’s add a new <strong>post </strong>with the below <strong>mutation</strong>.</p><pre>mutation{<br>  addPost(<br>   title:&quot;My first post&quot;,<br>   description:&quot;This is the description of my first post&quot;,<br>   tags:&quot;Hello,world&quot;<br>){<br>    id<br>    title<br>    description<br>   }<br>}</pre><p>Again, let’s add one more post.</p><pre>mutation{<br>  addPost(<br>   title:&quot;My second post&quot;,<br>   description:&quot;This is the description of my second post&quot;,<br>   tags:&quot;second,Hello,world&quot;<br>){<br>    id<br>    title<br>    description<br>   }<br>}</pre><p>So now we have one user and two posts in our database.</p><h3>8. Query the data from API</h3><p>let’s query our data by using the below queries.</p><p><strong>Get all posts with related Author</strong></p><blockquote>Here is a trick, although we have added “<strong>author</strong>” (as a relational field), we have to query as “<strong>relatedUser</strong>”.</blockquote><pre>{<br>  everyPost{<br>    title<br>    description<br>    relatedUser{<br>      id<br>      username<br>      email<br>    }<br>  }<br>}</pre><p>The above query will return all posts with a <strong>related user</strong> ( Author )</p><p><strong>Get a single post</strong></p><pre>{<br>  post(id:&quot;5c3757f6c127c934b7198685&quot;){<br>    title<br>    description<br>    tags<br>  }<br>}</pre><p>This will return a single user.</p><p>And we can do all CRUD stuffs with our API, GraphQL Designer automatically generated all queries and mutations for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/347/1*z93nv4DOf-1odSIqkR5upg.gif" /></figure><p><em>And also we don’t have to remember any single query or mutation.</em></p><p>Every GraphQL IDE has a very convenience <strong>documentation</strong> in the right panel. You can just click on <strong>Docs </strong>in<strong> </strong>the right corner of IDE, and see all the queries and mutations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*9iUa_UinRkIp4ActLUOTCg.jpeg" /></figure><p>Thanks for reading this article, I hope you learn something from this.</p><p>References</p><p><a href="http://www.graphqldesigner.com/">http://www.graphqldesigner.com/</a><br><a href="https://github.com/graphql/graphiql">https://github.com/graphql/graphiql</a><br><a href="https://github.com/GraphQL-Designer/graphqldesigner.com">https://github.com/GraphQL-Designer/graphqldesigner.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2f66568acb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vue Google autocomplete with multiple input fields.]]></title>
            <link>https://ronaldaug.medium.com/vue-google-autocomplete-with-multiple-input-fields-9b7c08a1a394?source=rss-1ab0f960c539------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b7c08a1a394</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[autocomplete]]></category>
            <category><![CDATA[google-maps]]></category>
            <dc:creator><![CDATA[Ronald Aug]]></dc:creator>
            <pubDate>Thu, 24 May 2018 08:59:19 GMT</pubDate>
            <atom:updated>2018-10-19T06:31:58.708Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-REtwEHURE0uf583eTS1Lw.jpeg" /></figure><p><strong>Requirements <br>- Google api link with api key<br>- </strong><a href="https://github.com/olefirenko/vue-google-autocomplete"><strong>Vue Google AutoComplete</strong></a><strong><br>- Vue Js</strong></p><p>Before we start, we have to include google api link in our app first.</p><p><em>Example google api link</em></p><pre>&lt;script type=&quot;text/javascript&quot; src=&quot;<a href="https://maps.googleapis.com/maps/api/js?key=AIzaSyDMc_9Dwj0e91HWO6Yc_iv-2oBYkURVWHs&amp;amp;libraries=places">https://maps.googleapis.com/maps/api/js?key=<strong>thisisyourkey</strong>&amp;amp;libraries=places</a>&quot;&gt;&lt;/script&gt;</pre><h4>1 — Install vue-google-autocomplete</h4><p>Firstly, let’s intall <a href="https://github.com/olefirenko/vue-google-autocomplete"><strong>vue-google-autocomplete</strong></a> into our project with this command.</p><pre>npm install vue-google-autocomplete --save</pre><p>or</p><pre>yarn add vue-google-autocomplete</pre><h4>2— Import into your project.</h4><p>And we can just directly import <a href="https://github.com/olefirenko/vue-google-autocomplete"><strong>vue-google-autocomplete</strong></a> into our vue component as below.</p><pre>&lt;script&gt;</pre><pre>// import Auto complete google map<br><strong>import VueGoogleAutocomplete from ‘vue-google-autocomplete’</strong></pre><pre> export default {</pre><pre>//use as a component<br><strong> components: {VueGoogleAutocomplete},</strong></pre><pre> data: function() {<br>  return {........}<br> }<br>}</pre><pre>&lt;/script&gt;</pre><h4>3 — Use vue-google-autocompete syntax inside the template</h4><p>After we imported the <a href="https://github.com/olefirenko/vue-google-autocomplete"><strong>vue-google-autocomplete</strong></a><strong> </strong>plugin<strong> </strong>then we can start adding input syntax inside the template.</p><pre>&lt;template&gt;</pre><pre>&lt;vue-google-autocomplete<br>    id=&quot;<strong>from_address</strong>&quot;<br>    classname=&quot;form-control&quot;<br>    placeholder=&quot;Start typing&quot;<br>    v-on:placechanged=&quot;getFromAddress&quot;<br>    v-on:error=&quot;handleError&quot;<br>&gt;<br>&lt;/vue-google-autocomplete&gt;</pre><pre>&lt;vue-google-autocomplete<br>    id=&quot;<strong>to_address</strong>&quot;<br>    classname=&quot;form-control&quot;<br>    placeholder=&quot;Start typing&quot;<br>    v-on:placechanged=&quot;getToAddress&quot;<br>    v-on:error=&quot;handleError&quot;<br>&gt;<br>&lt;/vue-google-autocomplete&gt;</pre><pre>&lt;/template&gt;</pre><p>As you can see I added two different input ids, one is <strong>from_address</strong> and another one is <strong>to_address</strong>.<br>- <em>Here is a trick, if the </em><strong><em>id</em></strong><em> name is the same for both inputs, it’s not going to work.</em></p><h4>4 — Types Attribute [updated]</h4><pre>&lt;vue-google-autocomplete<br>    <strong>types=&quot;&quot;</strong><br>    id=&quot;to_address&quot;<br>    classname=&quot;form-control&quot;<br>    placeholder=&quot;Start typing&quot;<br>    v-on:placechanged=&quot;getToAddress&quot;<br>    v-on:error=&quot;handleError&quot;<br>&gt;<br>&lt;/vue-google-autocomplete&gt;</pre><p>If there is no <strong>types</strong> attribute, vue-google-autocomplete will only fetch the <strong>street address (by default)</strong>, instead of fetching all the addresses. So, put the attribute <strong>types </strong>and set the value to blank. It will fetch all Google map addresses.<br>You can also set the (argument) value of <strong>types</strong> to <strong>cities , regions. </strong>Check the <a href="https://github.com/olefirenko/vue-google-autocomplete#user-content-correct-usage-of-the-types-parameter">example here</a></p><h4>5 — Define the input variables.</h4><pre>&lt;script&gt;</pre><pre> ....</pre><pre> data: function() {<br>       return {<br>                <strong>from_address</strong>:{},<br>                <strong>to_address</strong>:{}<br>        }<br>  },<br>  ....</pre><pre>&lt;/script&gt;</pre><h4>6 — Add methods for the response data.</h4><p>And we can get the response data on <strong>placechanged. <br></strong>we can pass 3 parameters for the map data.</p><p>1 — Address data</p><p>2 — Place result data</p><p>3 — The map id</p><pre>&lt;script&gt;</pre><pre>methods:{</pre><pre>            getFromAddress(from_address, placeResultData, id) {<br>                this.from_address = from_address;<br>                console.log(<strong>from_address</strong>);<br>            },<br>            getToAddress(to_address, placeResultData, id){<br>                this.to_address = to_address;<br>                console.log(<strong>to_address</strong>);<br>            },<br>            handleError(error){<br>                alert(error)<br>            }</pre><pre>}</pre><pre>&lt;/script&gt;</pre><p>Here, I just <strong>console.log</strong> the response data. In your case, you can bind it or append it into your vue app as you like. Thanks for reading.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-cW_EUlK-XkV2dacf68Shw.png" /></figure><p>Boilerplate — <a href="https://github.com/ronaldaug/google-vue-autocomplete-boilerplate">https://github.com/ronaldaug/google-vue-autocomplete-boilerplate</a></p><p>Reference— <a href="https://github.com/olefirenko/vue-google-autocomplete">https://github.com/olefirenko/vue-google-autocomplete</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b7c08a1a394" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>