If you’re a developer or someone who spends a lot of time online, you know how important it is to have a professional online presence. Recently, I decided to take a unique approach by using my domain, <a href="http://geoffslaven.com" target="_blank" rel="noopener nofollow">geoffslaven.com</a>, to redirect to my Daily.dev profile page.
<h4>Why Redirect to Daily.dev?</h4>
When I discovered Daily.dev, I was instantly impressed by its functionality and the community it fosters. It’s a platform that helps developers stay updated with the latest news, and I wanted my site to reflect my active engagement within the tech community. By redirecting my domain to my profile, I can showcase my interests and contributions without needing to maintain a separate website.
<h4>Setting Up the Redirect with Nginx</h4>
To get started, I needed to set up a redirect using Nginx. Here’s how I did it:
<ol>
<li>
Install Nginx: If you haven’t already, you’ll need to have Nginx installed on your server. You can follow the installation instructions specific to your operating system.
</li>
<li>
Configure Nginx: Once Nginx is up and running, I found the configuration file located at <code>/etc/nginx/sites-available/</code>. You can also create a new config file specifically for your domain.
</li>
<li>
Add the Redirect: In the server block, I added the following lines:
</li>
</ol>
<pre><code>
server {
 listen 80;
 server_name geoffslaven.com www.geoffslaven.com;

 return 301 https://app.daily.dev/mythobyte;
}
server {
 listen 443 ssl;
 server_name geoffslaven.com www.geoffslaven.com;

 ssl_certificate /your/path;
 ssl_certificate_key /your/path;

 return 307 https://app.daily.dev/mythobyte;
}

</code></pre>
Made a change to 307 as <a href="https://app.daily.dev/capjavert" data-mention-id="LJSkpBexOSCWc8INyu3Eu" data-mention-username="capjavert" translate="no">@capjavert</a> mentioned in his comment.
This tells Nginx to listen for requests to my domain and permanently redirect them to my Daily.dev profile.
4: Enable the Site: 	<code>sudo ln -s /etc/nginx/sites-available/geoffslaven.com /etc/nginx/sites-enabled/	</code>
<ol start="5">
<li>
Test the Configuration: After saving the changes, I ran <code>nginx -t</code> to check for any syntax errors in the configuration files.
</li>
<li>
Reload Nginx: Finally, I applied the changes by reloading Nginx with the command <code>sudo systemctl reload nginx</code>.
</li>
</ol>
<h4>The Result</h4>
Now, when someone types in <a href="http://geoffslaven.com" target="_blank" rel="noopener nofollow">geoffslaven.com</a>, they are instantly redirected to my Daily.dev profile. It’s a seamless experience that helps me maintain my online presence without the hassle of managing a traditional website.
<h4>Conclusion</h4>
Using your domain to redirect visitors to a specific profile or resource can be a clever way to establish an online identity. With just a few simple steps using Nginx, I transformed my domain into a gateway for others to connect with my work and interests on Daily.dev. I hope this guide inspires you to make the most of your domains!
Please don’t hesitate to contact me if you have any questions or are considering a similar setup.

Terminal

Geoff Slaven

How I Redirected My Domain to Daily.dev

There’s a lot more coming to the profile

<a href="https://app.daily.dev/mythobyte" data-mention-id="TlPKIWsj0D7A082jcGYnq" data-mention-username="mythobyte" translate="no">@mythobyte</a> really cool use case! That said you might want to use 307 status code for redirect, daily.dev might be safe bet, but when redirecting to domain/website you do not control it is better to use temporary redirect (307) so you can always revert it back if you want to host something from your own domain in the future. Still almost same experience for your use case, but gives you more options in the future.
Issue with permanent redirect (301) for this use case is that it can be cached by browsers/CDNs and other clients so they will no longer check your domain but just straight go to previous redirected page (even if you change the redirect to something else).

I see your domain is pointing to Cloudflare’s DNS, you could’ve just made a Redirect rule in Cloudflare.