You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: site/Build/br/event-based-architechture-for-spritekit/index.html
+1-1
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,7 @@ <h1>Arquitetura baseada em eventos para SpriteKit</h1>
175
175
<spanclass="call">playDeathSound</span>()
176
176
}
177
177
}</code></pre>
178
-
<p>E por fim, para mostrar a facilidade de se criar objetos que interagem com o sistema como um todo e causam efeitos na cadeia, mesmo que não sejam SKNodes, para adicionar suporte aos controles de Xbox One e PlayStation 4 no nosso jogo, podemos simplesmente adicionar uma classe como esta:</p>
178
+
<p>E por fim, para mostrar a facilidade de se criar objetos que interagem com o sistema como um todo e causam efeitos na cadeia, mesmo que não sejam SKNodes, para adicionar suporte aos controles de Xbox e PlayStation no nosso jogo, podemos simplesmente adicionar uma classe como esta:</p>
Copy file name to clipboardexpand all lines: site/Build/en/index.html
+10-1
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,16 @@
38
38
<h1class="huge">Hey, it's me, Mauricio</h1>
39
39
<h2>Apple tech talk and the like</h2>
40
40
</div>
41
-
<div></div>
41
+
<div>
42
+
<div>
43
+
<h2><ahref="/en/serversideswift" class="inverted link-underline link-underline-opacity-100 link-underline-opacity-100-hover">Let's talk about Swift on Linux?</a></h2>
44
+
<p>Swift on Linux is an area little explored by Apple platform developers, but it can be a very useful tool and an immense source of knowledge, and it is very worth learning.</p>
45
+
</div>
46
+
<div>
47
+
<h2><ahref="/en/event-based-architecture-for-spritekit" class="inverted link-underline link-underline-opacity-100 link-underline-opacity-100-hover">Event-Based Architecture for SpriteKit</a></h2>
48
+
<p>Let’s take a look at how we can simplify app development with SpriteKit.</p>
<metacontent="Swift on Linux is an area little explored by Apple platform developers, but it can be a very useful tool and an immense source of knowledge, and it is very worth learning." name="description" />
7
+
<metacontent="Mauricio Cardozo" name="author" />
8
+
<metacontent="Ignite v0.2.1" name="generator" />
9
+
<title>Let's talk about Swift on Linux? – Mauricio Cardozo</title>
<metacontent="Let's talk about Swift on Linux?" property="og:title" />
15
+
<metacontent="Let's talk about Swift on Linux?" name="twitter:title" />
16
+
<metacontent="Swift on Linux is an area little explored by Apple platform developers, but it can be a very useful tool and an immense source of knowledge, and it is very worth learning." property="og:description" />
17
+
<metacontent="Swift on Linux is an area little explored by Apple platform developers, but it can be a very useful tool and an immense source of knowledge, and it is very worth learning." name="twitter:description" />
<metacontent="Swift on Linux is an area little explored by Apple platform developers, but it can be a very useful tool and an immense source of knowledge, and it is very worth learning." property="og:description" />
<p>Swift on Linux is an area little explored by Apple platform developers, but it can be a very useful tool and an immense source of knowledge, and it is very worth learning.</p>
49
+
<p>We all already understand writing code, and seeing the result of our creation is not very different from other platforms when we are on the server, but one thing that I personally have always had a lot of problems with is: How do I make my code available to other people? We already know how to upload an app to the App Store, but what about uploading an open service on the internet? There are so many ways, all correct, each in its own way and it is almost impossible to choose one.</p>
50
+
<h2>The Project</h2>
51
+
<p>I created <ahref="https://t.me/F1LandinhoBot">@F1LandinhoBot</a> with the purpose of helping me to remember the times of Formula 1 races in a group of friends, accessing Telegram’s API and sending messages so that we would not miss any races whatsoever.</p>
52
+
<imgsrc="/images/serverswift/telegram.png" />
53
+
<p>And everything worked fine running directly on my Mac, but I don't want to leave my Mac on all the time running this code for the bot to work and I don't even want to think about how I'm going to guarantee that it will work all the time. Where I live, power outages are pretty common, and it seems like a waste of my computer's processing power anyway.</p>
54
+
<p>So I decided to put this code to run on my Amazon server, which I've already had running a <ahref="https://quake.host">Quake server</a> for a few years, so I wouldn't need to pay a single penny more than I already paid for it to get the service up and running. The Swift setup on Linux is fully detailed on <ahref="https://swift.org">Swift.org</a> and despite being a little long, it is easy to follow. I cloned the code from GitHub and I wasn't expecting what came next:</p>
55
+
<imgsrc="/images/serverswift/wont-build.png" />
56
+
<pclass="center muted caption">OpenCombine is a library made specifically for us to use Combine on Linux, how come it doesn't exist? Since when is URLSession an AnyObject?</p>
57
+
<h2>Swift on Linux</h2>
58
+
<p>There are some speed bumps along the way to server-side Swift that are rarely mentioned, mainly because they are abstracted by the famous frameworks, but that you will encounter very quickly if you go the route of writing "pure" code. They all exist because Swift on Mac does not have the same libraries as Swift on Linux. The Foundation, which we are quite used to using in the Apple world, is not the same Foundation that exists in Linux, and <ahref="https://forums.swift.org/t/what-are-best-practices-to-write-a-linux-software-on-macos/">this is not documented</a> anywhere. It's a problem that <ahref="https://www.swift.org/blog/future-of-foundation/">is not going to last long</a>, but it's still a problem.</p>
59
+
<imgsrc="/images/serverswift/urlsession.png" />
60
+
<pclass="center muted caption">URLSession is on a completely different library on Linux, that does not even exist on macOS!</p>
61
+
<h2>Publishing our work</h2>
62
+
<p>Once these problems were resolved, I finally had my project compiling and running on the server! But now, how do I leave it running there? I can't just close the ssh in my terminal, because it will stop the code from executing. To solve this problem, I used <code>systemd</code>, which is Ubuntu's default service manager.</p>
63
+
<p>The configuration file is very simple. I asked GPT to create a base and I customized it with the needs I had, like my environment variables (don't put them directly in your code!) and what my service would have to do if a problem occurred.</p>
<spanclass="type">WorkingDirectory</span>=/home/ubuntu/<spanclass="type">LandinhoBot<br/>ExecStart</span>=/home/ubuntu/swift/swift-<spanclass="number">5.7.3</span>-<spanclass="type">RELEASE</span>-ubuntu22.<spanclass="number">04</span>/usr/bin/swift run
<p>After that, I still need to enter the server, download the code, compile and run the service. This whole process is very boring to do, and as it is not part of our daily lives, we may even forget what all these steps are like, so I wrote a very simple deploy script, to make the process easier. It downloads the code, compiles it and restarts the service:</p>
<p>But I still have to log into the server, run the script and check if everything is ok. It can be better. To solve this, after talking to a friend who is full-stack, I decided to go for the simplest route possible: Automate the process that I was already doing manually, through GitHub Actions.</p>
run: ssh server 'cd <spanclass="type">LandinhoBot</span>; sh deploy.<spanclass="property">sh</span>'
110
+
env:
111
+
host: ${% raw %}{{secrets.<spanclass="type">SSH_HOST</span>}}{% endraw %}
112
+
username: ${% raw %}{{secrets.<spanclass="type">SSH_USERNAME</span>}}{% endraw %}
113
+
key: ${% raw %}{{secrets.<spanclass="type">SSH_KEY</span>}}{% endraw %}</code></pre>
114
+
<p>It's important to thank <ahref="https://twitter.com/flpms">@flpms</a>, who is the friend I mentioned during the article. The part of the configuration that creates the SSH configuration file for GitHub Actions is his authorship.</p>
115
+
<p>Dissecting the Actions configuration, we have a job that will be executed every time a push happens on my <code>main</code> branch, with a step to configure SSH and a step to execute our deploy script.</p>
116
+
<p>And that's it! This way you can automate the execution of your code on any Linux machine that you have access to the terminal. But there is another alternative:</p>
117
+
<h2>Platform as a Service</h2>
118
+
<p>An easier way to do this entire process is using a platform like <ahref="https://render.com">Render</a> (or thousands of other services that do the same thing), which will abstract the entire process of configuring the environment, deploying it when there is a merge, and it will give you other perks, such as database backups and so on. This whole facility has its cost ($), and if you want to upgrade another service, the costs will rise way faster.</p>
119
+
<imgsrc="/images/serverswift/render.png" />
120
+
<p>There's not much to say about these platforms, each one will have its own particularities, but it's an alternative that I really enjoy using! The less time we spend on infrastructure, the more we can invest in the product itself, and that's what matters in the end. Until next time!</p>
0 commit comments