<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on 이글루</title><link>https://trulybright.dev/en/posts/</link><description>Recent content in Posts on 이글루</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 08 Sep 2025 13:38:34 +0900</lastBuildDate><atom:link href="https://trulybright.dev/en/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting Up Monorepo for a Unity Project</title><link>https://trulybright.dev/en/posts/setting-up-monorepo-for-a-unity-project/</link><pubDate>Mon, 08 Sep 2025 13:38:34 +0900</pubDate><guid>https://trulybright.dev/en/posts/setting-up-monorepo-for-a-unity-project/</guid><description>In a Client-Server architecture, the client and the server need to share the api codebase for consistency. Some solutions to do so are as follows:
Git submodule: Have three repositories (client, server, api). The client repo adds the api repo as a submodule. Do the same for the server. Monorepo: Have one repository (say MyGame). Create three directories at the root: /Client, /Server and /Api, each containing its corresponding codes. Symlink: Create a Symlink to the API for the client and the server to reference.</description></item></channel></rss>