<?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 Brigitta Rucz on Medium]]></title>
        <description><![CDATA[Stories by Brigitta Rucz on Medium]]></description>
        <link>https://medium.com/@brigittarucz?source=rss-3c1ab65f98d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MNAHBAlKAf2UoiPdXRYkcQ.jpeg</url>
            <title>Stories by Brigitta Rucz on Medium</title>
            <link>https://medium.com/@brigittarucz?source=rss-3c1ab65f98d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:47:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brigittarucz/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[What Mistakes To Avoid When You Come Across New Technologies]]></title>
            <link>https://brigittarucz.medium.com/what-mistakes-to-avoid-when-you-come-across-new-technologies-ecda548f89cf?source=rss-3c1ab65f98d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ecda548f89cf</guid>
            <category><![CDATA[technology-news]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[mistakes]]></category>
            <dc:creator><![CDATA[Brigitta Rucz]]></dc:creator>
            <pubDate>Sat, 13 Feb 2021 09:23:07 GMT</pubDate>
            <atom:updated>2021-02-13T09:23:07.161Z</atom:updated>
            <content:encoded><![CDATA[<h4>A shared personal analysis on how things could have been done better.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nyag7rdYSBdsArjb" /><figcaption>Photo by <a href="https://unsplash.com/@storybyphil?utm_source=medium&amp;utm_medium=referral">Phil Desforges</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Imagine that you are trying to set a project live and you have absolutely no clue on how to do it. And while you are at it, sprinkle that with some technologies that integrate together in a specific way, while each of them requires its own process of deployment. How would you go around it? I can try to save you the headache, or at least some of it, and walk you through my own experience.</p><p>To give you a bit of context, I have tried to put out in the open a NodeJS based project combined with two databases, MariaDB and ArangoDB. You can check it out <a href="https://medium.com/@brigittarucz/deploying-a-nodejs-mariadb-and-arangodb-based-project-on-digitalocean-fc1f9709b6a0">here</a>. As I am not that informed in stuff that concerns anything else than basic web development stacks, the notions that I encountered down the road were nothing less but obscure. Bash scripting, network ports and cloud hosting? I can recognize their difficulty now, by retrospectively analysing the course of events, but one month ago when all this started? I had absolutely no idea what I would stand up against.</p><h4><strong>Mistake #1 Always diving in head-first</strong></h4><p>When you encounter something completely new it can be very painful and time consuming to test it all by experimentation. I do understand the notion that different people have different ways of learning: some prefer theory while others prefer practice, which is perfectly fine. But, within a topic of an increased complexity you should have a minimum, even vague idea about what is it that you are doing through a mixed approach. The reasoning behind this is pretty simple — if you miss out on a key information here — either you waste hours, days or even weeks, either you do not even manage to deploy.</p><p>As the events have progressed, with no knowledge whatsoever about the proper course of action, I have resumed to Stack Overflow and countless of hours invested in Google searches. Moreover, I was rushing to finish this, while having multiple other things going on simultaneously. This was nothing else than a phase. A phase that can be resumed to a couple of words: busy and stressful — which leads me to:</p><h4><strong>Mistake #2 Letting stress affect the quality of your work</strong></h4><p>Stress and overworking under absurd deadlines, the plagues of the modern world that are responsible for various health problems. In the scenario implying a developer, especially one engaging with new, abstract concepts, it is needed to enter a zone of deep focus. If you feel stress building up remember: <em>in small doses it can light the fuel and launch the rocket into space, but in big doses it can generate an explosion destroying the rocket without even having it set off</em>. So use it with caution and if you feel overwhelmed, burned out or you have had absolutely enough with the error from line 83 that doesn’t cease to exist — just take a break. Really. Have one.</p><p>Problem solving is obviously one of the most important qualities in the developer’s toolkit — you want to be good at assessing circumstances and analysing sources of information to come up with a solution. But, know your brain as well and get acquainted with its capacities. <a href="https://hbr.org/2012/09/three-ways-to-think-deeply-at-work?fbclid=IwAR0mMqe_GM-vHeSwmo2qKTIweP4EmuF1W-WliABQgqeEIaPxRJiA4UaIm4U">A study conducted by NeuroLeadership Group</a> on no less than 6,000 people has figured that some problems are far too big for the conscious brain to tackle which is why pausing on the matter and distracting yourself with something else — even for a brief period of time — can actually lead you to coming back to that “Aha! I got it!” sort of a moment. For the record, you do not need more than 2 minutes of distraction for the unconscious mind to set in.</p><p>Throughout this mini rollercoaster of a deployment, I could observe that the more relaxed I was, the more focused and patient I became, which comparatively lead to faster positive results. Though, there were some issues that seemed to be unsolvable. And that happened because in the way that I was trying to handle them, they truly were. So, a project with two different databases was not the best idea to begin with, especially when I did not know how to manage deploying at least one. But trying to do it all at once? Absolutely not. Which brings me to:</p><h4><strong>Mistake #3 Not breaking the work into smaller chunks</strong></h4><p>This has proven to be quite the classic, especially when you do not take the time to step back and analyse what is that you are trying to achieve. In certain social situations, not responding straight away can be the best course of action to eliminate biases and assumptions. Even if this is a 1:1 conversation with yourself, be it conscious or unconscious, trying not to cave into the instinct of straight up writing code or commands can prove to be much more fruitful because you refuse to be the victim of your own code related assumptions. Also while you’re doing that, go for having an overview and divide the task into smaller chunks for the sake of your project and your own nerves.</p><p>Naturally, I have started to think in steps rather than in jumps. You could argue that this advice is so obvious, and I will say yes, it surely is. Everything that I said is obvious — which is why it is so easy to overlook.</p><p>When I started to focus on getting little done, I could actually do it. Nevertheless, I have hit some walls. Quite hard and with no way of breaking through. Every goal is achievable in code, but not in any way you could think of. An improper use of your technologies can be quite detrimental to the scope, which leads me to:</p><h4><strong>Mistake #4 Not knowing what you are going to use inside out</strong></h4><p>It does not really matter if we speak here about frameworks, programming languages or different given systems. I was trying to connect Arango for days on end to my hosting provider and no matter if I was using a deployment in Azure, Arango Oasis or Digital Ocean for it — the error was the same. I tried to search for answers in different ways but could not find one that would fit.</p><p>When you think about the maturity of a technology, chances are that the older it is, the more have developers tried, failed and engaged into problem solving with each other. I do recognize Arango’s huge potential — but it is new nevertheless, compared to other seniors in the business, like MySQL, so it can be harder to troubleshoot. Luckily enough, this was only done as a personal project, but in an actual job setting, implementing a technology with developers inexperienced in handling it from start to finish can cost valuable resources. You might have thought by now that the problem that I encountered was with Arango, but I got you here, that was not the case — it is only a side note. The issue that I had was looking from a wrong angle at the problem because this was actually related to my hosting provider. Hence, I totally neglected diving deeper into understanding a system so crucial for my deployment and I wasted an incredible amount of time on troubleshooting something else while missing out on a detail so trivial.</p><p>On an ending note, after all, I did manage to successfully deploy. Though, I did something more relevant than that which is I reminded myself not to overlook the obvious. It can happen to all of us, no matter the experience level because these valuable lessons are so easy to forget. The main takeaway is experiment — as much as you can because it is very important to get acquainted with new technologies. All I am trying to say is choose to do it smartly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ecda548f89cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deploying a NodeJS, MariaDB and ArangoDB based project on DigitalOcean]]></title>
            <link>https://brigittarucz.medium.com/deploying-a-nodejs-mariadb-and-arangodb-based-project-on-digitalocean-fc1f9709b6a0?source=rss-3c1ab65f98d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc1f9709b6a0</guid>
            <category><![CDATA[deployment]]></category>
            <category><![CDATA[mariadb]]></category>
            <category><![CDATA[arangodb]]></category>
            <category><![CDATA[node]]></category>
            <category><![CDATA[digitalocean]]></category>
            <dc:creator><![CDATA[Brigitta Rucz]]></dc:creator>
            <pubDate>Wed, 20 Jan 2021 17:02:51 GMT</pubDate>
            <atom:updated>2021-01-20T17:02:51.190Z</atom:updated>
            <content:encoded><![CDATA[<h4>A comprehensive beginner guide for getting your app out in the open.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wZ_GC8uPpplVdEoN" /><figcaption>Photo by <a href="https://unsplash.com/@euwars?utm_source=medium&amp;utm_medium=referral">Farzad Nazifi</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a developer playing around with these things, I can only assume you would like to see them somewhere else than hanging around on localhost. Maybe it’s a personal ambition of yours or maybe you want to apply for some jobs, case in which “<em>But it worked on my computer</em>” will not help you too much. Regardless, I have crafted this guide for you and also for me — probably I will forget it all soon enough.</p><p>To get started, ensure your project is successfully running on localhost. I will anyways provide some starter files lower below. No need to skim through just yet. In case you have a domain name, you want to start with that because DNS propagation can take a while.</p><p>Configure this first in your own domain registrar. Personally I use one.com, so just go and change the name servers, pointing them to DigitalOcean. You can use this <a href="https://www.whatsmydns.net/">DNS Checker</a> to verify the propagation’s status.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*WgkNmtjDf8gUEgP-M6-lSw.png" /></figure><p>Then create an account on DigitalOcean and go in the right panel of the interface to droplets — create a new one. Choose as distribution Ubuntu 20.04 (LTS) x64. As a plan I used the Basic $10 one with 2GB / 1 CPU and 50 GB / SSD disk. Know that in the Node docs they recommend against using any cloud providers that offer services with minimum specs needed to run Ubuntu. They advise for a virtual machine with at least 2GB of RAM, 4 vCPUs and 25GB of storage. Plus we’ll also need Arango operating simultaneously which also requires 1GB of RAM and 1 CPU. Oh and did I mention PhpMyAdmin? So, this might not be enough — you should do some math before to calculate the server requirements for your web app. But for the scope of this guide, we’ll manage just fine.</p><p>Choose a datacenter region closer to you and an SSH based authentication. What I am going to showcase next is done on Windows 10. If you are using other operating system you will have to search for the equivalent of this command. Click on new SSH key and open the PowerShell where you input the following:</p><pre>ssh-keygen</pre><p>This will require you to enter a file name, so only add the Windows path alongside the name. It will ask to add a passphrase as well, you can decide not to and enter your way through it.</p><pre>C:/path/.ssh/id_sample_droplet</pre><p>Copy the SSH key content:</p><pre>cat C:/path/.ssh/id_sample_droplet.pub</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/1*894CwKaIcAE5w9qKmI1KLw.png" /></figure><p>And then paste the key on DigitalOcean, while also adding an appropiate name for it. Create the droplet and in the meantime, go to the networking tab in the right panel of the GUI and add your domain. This will create by default three NS records. Configure an A record that directs to the droplet and a CNAME that follows this pattern in the hostname <a href="http://www.yourdomain.com/">www.yourdomain.com</a> as an alias of yourdomain.com, which is the A record just created. Theoretically, these are used to map your domain name to the IP, hence you will automatically get directed to the latter.</p><p>With your droplet created, you are now the proud owner of a nice public ipv4. Copy that in order to ssh into your droplet and go to your PowerShell where you input:</p><pre>ssh -i /path/to/key/id_sample_droplet root@167.31.43.431</pre><p>Click yes to continue connecting as the first time you log in, the server has no idea that this is your machine. If succesfull, you’ll get a message stating that the host key fingerprint was saved to the list of known hosts and you should technically be connected now as root. Add a new user due to security concerns, as root is the first one hackers are trying to break into.</p><pre>adduser newuser</pre><p>You’ll be asked for a password — it might be a good idea to use a password generator and save it for future reference. Give yourself administrative privileges:</p><pre>usermod -aG sudo newuser</pre><p>So, at the point you are in now, trying to ssh with the new user created will deny your permission. That is because you have to append the public key to each user:</p><pre>cd /home/newuser/<br>mkdir .ssh<br>cp /root/.ssh/authorized_keys /home/newuser/.ssh/authorized_keys</pre><p>In Linux, the ownership of every file is based on a set of permissions. You have to ensure the correct permissions are applied. These are set with the chmod command followed in our case, by an integer.</p><ul><li><a href="https://chmodcommand.com/chmod-700/">700</a> — the Owner can read, write and execute; Group and Others cannot do anything to the file.</li><li><a href="https://chmodcommand.com/chmod-644/">644</a> — the Owner can read and write; Group and Others can read.</li></ul><pre>chmod 700 /home/newuser/.ssh<br>chmod 644 /home/newuser/.ssh/authorized_keys</pre><p>Set the owner, the group and test for changes by using the command followed by your path ls -l /home/newuser/.ssh:</p><pre>chown -R newuser:newuser /home/newuser/.ssh</pre><p>Now verifythat you are able to login with your new user account and password. All good? Let’s move on. Install ArangoDB by following <a href="https://computingforgeeks.com/how-to-install-arangodb-on-ubuntu-linux/">this guide</a>, then test if your instance is available at your own ipv4 followed by the port in the format <em>167.31.43.431:8529</em>. If succesful, install MariaDB and PhpMyAdmin.</p><pre>sudo apt-get install mariadb-server mariadb-client<br>sudo apt-get install phpmyadmin php-mbstring</pre><p>It is very important that when you go through the installation of PhpMyAdmin you <strong>select Apache2 as a web server </strong>to be configured automatically. In order to do that, hit space bar to select, then tab and enter. You should secure this newly created instance by disabling root login and allowing access to the GUI only from specific IPs. But for now, I will resume myself only to creating a new user and grant that user access and privileges:</p><pre>sudo mysql</pre><p>Now, you have entered into the database’s shell. Run the following:</p><pre>MariaDB&gt; CREATE USER &#39;newuser&#39;@&#39;localhost&#39; IDENTIFIED BY &#39;insecurepassword&#39;;</pre><pre>MariaDB&gt; GRANT ALL PRIVILEGES ON *.* TO ‘newuser&#39;@&#39;localhost&#39; WITH GRANT OPTION;</pre><pre>MariaDB&gt; exit</pre><p>Test your connection by accessing your droplet’s IP followed by /phpmyadmin in the format <em>167.31.43.431/phpmyadmin </em>and connecting with the newly created user. Now we need to take care of NodeJS and NPM by inputting the following commands:</p><pre>sudo apt install nodejs<br>test nodejs -v </pre><p>Always test to check if the commands you are running are successful. It is better to be on the safe side, than realize halfway through your deployment that stuff is not running properly.</p><pre>sudo apt install npm<br>test npm -v</pre><p>If you want to follow along completely, make sure that you have sample data in your databases and modify the names of the tables or collections accordingly. Project dependencies included in the package.json file are kept to a minimum — I have <em>arangojs, body-parser, express and mysql2</em>. Now, regarding app.js its structure is the one below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e41f67f9bdc576c575f25dbf1bdf469c/href">https://medium.com/media/e41f67f9bdc576c575f25dbf1bdf469c/href</a></iframe><p>No matter the project, it is highly relevant here to ensure that you have it in a Github repository. Go to your droplet and create a folder in home with mkdir where you will store your apps, then clone your project there.</p><pre>git clone <a href="https://github.com/brigittarucz/deployment_file.git">https://github.com/username/deployment.git</a></pre><p>Now, cd into the newly created folder which should be the same as the repository name and configure your database files accordingly. Basically, keep an eye on the ports and make sure they are correct, with 3306 for Maria and 8529 for Arango. When you configure the latter one, add to the host the IP address of the droplet. This might sound counterintuitive, but leave for the relational based database localhost in the configuration. Lastly, enter your newly created credentials for each system. You can open the file to do all these by running:</p><pre>sudo nano app.js</pre><p>Once you have brought all the needed modifications, save and exit, then run the installer for the dependencies:</p><pre>npm install</pre><p>And now, the moment of truth — if you followed along correctly and this post is not old enough to become obsolete, chances are that you will see data displayed through the base command that starts up your node server:</p><pre>node app.js</pre><p>This is not sufficient though. You have come quite far but there is still a bit to go. Your app might crash, unfortunately. It’s what apps do in case of memory leaks, error events or poor performance. PM2 is a pretty cool process manager crafted for Node which will revive your application in case it encounters fatal errors.</p><pre>sudo npm i -g pm2</pre><p>Preferably, you’re still in the same folder where you start the app by inputting:</p><pre>pm2 start app.js</pre><p>Which will lead you to a table view like the one below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*36Nz3G5YdyvMiM3dPPBtTA.png" /></figure><p>In case you experience difficulties with your apps, pm2 monit might become a good tool to keep in mind for troubleshooting. I strongly recommend checking their docs to see what else it can do. But, going back to our stuff, I can only imagine that you want the app available to the outside world, because as it is now — you are the only one that knows of its existence. So lets get it out by manipulating the firewall:</p><pre>sudo ufw enable</pre><p>Now, you have to enable ssh through it. That is because once you type the above command, you need further configurations to allow what gets past the firewall and what not. If you neglect this you will experience lots of fun with some connections that are either timed out or refused and the only way you’ll get back into your droplet will be by launching the recovery console.</p><pre>sudo ufw allow ssh</pre><p>As we have the application running on port 3000, we want to be able to connect to it from the outside world. In order to allow incoming tcp packets to this port run the following:</p><pre>sudo ufw allow 3000/tcp</pre><p>Remember when you configured DNS records, like what, ages ago? No? Well that can possibly mean that maybe you skipped the step. Which is fine, just take the IP and add it in the browser, followed by :3000. If you did tackle with the DNS though, you can use it to access Arango, PhpMyAdmin and your app. Take the A record from the networking tab and add in the browser, again followed by the port number and you should see the message coming from what you have just deployed! :)</p><p>Further improvements might include getting rid of the port number through using a reverse proxy and <a href="https://linuxtogether.org/configuring-reverse-proxy-for-node-using-apache-mod-proxy/">this guide</a> seems up for the challenge. Also, you might consider adding a self signed SSL certificate for https connections, in which case you might want to check out <a href="https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-apache-in-ubuntu-18-04">this guide</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc1f9709b6a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>