<?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 Jochen Kirstätter on Medium]]></title>
        <description><![CDATA[Stories by Jochen Kirstätter on Medium]]></description>
        <link>https://medium.com/@jochen.kirstaetter?source=rss-63a3d7a84479------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*DFBZ54zcMd1v551m.</url>
            <title>Stories by Jochen Kirstätter on Medium</title>
            <link>https://medium.com/@jochen.kirstaetter?source=rss-63a3d7a84479------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:16:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jochen.kirstaetter/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[Customise Your Instance of Jitsi Meet]]></title>
            <link>https://medium.com/@jochen.kirstaetter/customise-your-instance-of-jitsi-meet-635eb51bd517?source=rss-63a3d7a84479------2</link>
            <guid isPermaLink="false">https://medium.com/p/635eb51bd517</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[jitsi]]></category>
            <dc:creator><![CDATA[Jochen Kirstätter]]></dc:creator>
            <pubDate>Fri, 11 Sep 2026 07:31:01 GMT</pubDate>
            <atom:updated>2026-09-11T07:31:01.677Z</atom:updated>
            <content:encoded><![CDATA[<p>In the previous two articles of this series, we set up our self-hosted video conferencing infrastructure. First, we walked through how to <a href="https://jochen.kirstaetter.name/install-jitsi-meet-on-gcp.html">Install Jitsi Meet on Compute Engine (GCP)</a>, providing a scalable, isolated WebRTC server. Next, we secured our installation against unauthorised room squatting by learning how to <a href="https://jochen.kirstaetter.name/authentication-jitsi-meet.html">Enable Authentication in Jitsi Meet</a>.</p><p>This content been published <a href="https://jochen.kirstaetter.name/customise-jitsi-meet">here</a> originally.</p><p>Now that your instance is operational and secure, it is time to make it truly your own.</p><p>Out of the box, Jitsi Meet displays default branding, external links to the Jitsi community, and generic meeting room titles. Customising the interface to display your own logo, custom colour scheme, tailored welcome text, and default audio/video behaviour transforms a generic utility into a professional, cohesive communication platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fHJCWEza80zyFAmVTgknIw.jpeg" /></figure><p>However, anyone who has modified a Debian or Ubuntu package installation knows the frustration of running apt-get upgrade only to find that their custom logos, stylesheets, and configurations have been completely overwritten.</p><p>In this third article, we will explore:</p><ul><li>Core feature configuration in hostname-config.js.</li><li>Visual appearance customisation covering logos, watermarks, titles, and welcome content.</li><li>Practical strategies to make customisations upgrade-persistent across package updates with hardened Nginx rules and caching.</li><li>Google Calendar integration for agenda synchronisation on the landing page and user settings.</li><li>Desktop and mobile client integration, including in-browser WebRTC vs native mobile app server configuration.</li></ul><p>Note</p><p>The adjustments described below require administrative permissions. You can execute them by launching an interactive root terminal (sudo -i) or by prefixing individual commands with sudo.</p><h3>Core feature configuration</h3><p>The primary configuration file controlling client-side behaviour is located at:</p><pre>sudo nano /etc/jitsi/meet/$(hostname -f)-config.js</pre><p>This JavaScript file is loaded by every participant’s browser before entering a room. It governs meeting defaults, audio/video policies, and third-party integrations.</p><h3>Essential participant settings</h3><p>When hosting large meetups or webinars, having every attendee enter with microphones and cameras blazing creates immediate audio feedback and bandwidth congestion. You can set sane defaults:</p><pre>// Start every participant muted to avoid immediate audio feedback<br>startWithAudioMuted: true,<br><br>// Start participants with video muted if bandwidth is constrained<br>startWithVideoMuted: false,<br><br>// Require participants to verify mic and camera in a prejoin lobby<br>prejoinPageEnabled: true,<br><br>// Default UI language (e.g. English)<br>defaultLanguage: &#39;en&#39;,<br><br>// Enable or disable peer-to-peer mode for 1-on-1 calls<br>p2p: {<br>    enabled: true,<br>    preferH264: true<br>}</pre><h3>Branding and appearance customisation</h3><p>The visual presentation of Jitsi Meet is distributed across static HTML templates, configuration files, and image assets located in /usr/share/jitsi-meet/.</p><h3>Custom watermark &amp; logos</h3><p>The most recognisable element in a Jitsi call is the watermark shown in the top-left corner of the video grid.</p><ul><li><strong>Main Watermark</strong>: /usr/share/jitsi-meet/images/watermark.png</li><li><strong>Favicon</strong>: /usr/share/jitsi-meet/favicon.ico</li></ul><p>To display your community or company logo, prepare a transparent PNG image (recommended size: 166 × 48 px) and replace the default file:</p><pre>sudo cp /path/to/my-logo.png /usr/share/jitsi-meet/images/watermark.png</pre><h3>Fine-tuning UI elements</h3><p>To adjust watermark links, application names, and toolbar buttons, open the interface configuration:</p><pre>sudo nano /usr/share/jitsi-meet/interface_config.js</pre><p>Key variables to customise include:</p><pre>// Customise the application name shown on browser tabs and notifications<br>APP_NAME: &#39;MSCC Meet&#39;,<br>NATIVE_APP_NAME: &#39;MSCC Meet&#39;,<br><br>// Direct clicking the top-left logo to your organisation website<br>JITSI_WATERMARK_LINK: &#39;https://www.mscc.mu&#39;,<br><br>// Hide promotional banners<br>SHOW_JITSI_WATERMARK_FOR_GUESTS: true,<br>SHOW_WATERMARK_FOR_GUESTS: false,<br><br>// Curate visible toolbar buttons to remove unused features<br>TOOLBAR_BUTTONS: [<br>    &#39;microphone&#39;, &#39;camera&#39;, &#39;closedcaptions&#39;, &#39;desktop&#39;, &#39;fullscreen&#39;,<br>    &#39;fodeviceselection&#39;, &#39;hangup&#39;, &#39;profile&#39;, &#39;chat&#39;, &#39;recording&#39;,<br>    &#39;livestreaming&#39;, &#39;etherpad&#39;, &#39;sharedvideo&#39;, &#39;settings&#39;, &#39;raisehand&#39;,<br>    &#39;videoquality&#39;, &#39;filmstrip&#39;, &#39;tileview&#39;, &#39;shortcuts&#39;, &#39;help&#39;<br>],</pre><p>Note</p><p>In recent Jitsi Meet releases, several user interface parameters originally located in interface_config.js (such as toolbarButtons and filmstrip controls) are being progressively consolidated directly into config.js. If you are running an updated package version or containerised deployment, verify whether your target parameter has moved into your primary config.js schema.</p><h3>Social media &amp; Open Graph previews</h3><p>When you share a meeting URL on messaging platforms like Slack, Microsoft Teams, or WhatsApp, the client fetches Open Graph metadata to render a link preview card.</p><p>Open /usr/share/jitsi-meet/title.html:</p><pre>sudo nano /usr/share/jitsi-meet/title.html</pre><p>Replace the default tags with your custom branding:</p><pre>&lt;title&gt;MSCC Meet - Monthly Code &amp; Coffee Chat&lt;/title&gt;<br>&lt;meta property=&quot;og:title&quot; content=&quot;MSCC Meet - Monthly Code &amp; Coffee Chat&quot; /&gt;<br>&lt;meta property=&quot;og:image&quot; content=&quot;/images/watermark.png&quot; /&gt;<br>&lt;meta property=&quot;og:description&quot; content=&quot;Secure, high-quality video meetings hosted by the Mauritius Software Craftsmanship Community.&quot; /&gt;<br>&lt;meta itemprop=&quot;name&quot; content=&quot;MSCC Meet&quot; /&gt;</pre><h3>Landing page footer &amp; welcome content</h3><p>The landing page displays a room creation box. You can inject custom announcements, code of conduct links, or server sponsorship details below this box using welcomePageAdditionalContent.html:</p><pre>sudo nano /usr/share/jitsi-meet/static/welcomePageAdditionalContent.html</pre><p>Add your custom HTML snippet:</p><pre>&lt;template id=&quot;welcome-page-additional-content-template&quot;&gt;<br>    &lt;div style=&quot;text-align: center; margin-top: 2rem; color: #fff;&quot;&gt;<br>        &lt;p&gt;Hosted by the &lt;strong&gt;Mauritius Software Craftsmanship Community&lt;/strong&gt;.&lt;/p&gt;<br>        &lt;p&gt;&lt;small&gt;Please respect our &lt;a href=&quot;https://www.mscc.mu/code-of-conduct/&quot; target=&quot;_blank&quot; style=&quot;color: #4a90e2;&quot;&gt;Code of Conduct&lt;/a&gt; during all sessions.&lt;/small&gt;&lt;/p&gt;<br>    &lt;/div&gt;<br>&lt;/template&gt;</pre><h3>The upgrade dilemma</h3><p>Here is the catch: Jitsi Meet receives frequent software updates. When you run sudo apt-get upgrade, the jitsi-meet-web package extracts clean upstream files into /usr/share/jitsi-meet/.</p><p>Without precaution, your custom watermark.png, interface_config.js, title.html, and welcome snippets are immediately overwritten by the default upstream templates.</p><p>To solve this, we employ two different strategies depending on your operational preferences.</p><h3>Virtual locations via Nginx aliases (recommended)</h3><p>The most robust architectural solution is to separate your custom assets from the operating system’s package directory entirely.</p><p>By placing your custom assets in an independent directory (e.g. /var/www/jitsi-custom/) and using Nginx location alias directives, Nginx intercepts requests for specific assets and serves your custom files before the request ever touches /usr/share/jitsi-meet/.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t1NzYfUFWhz3uiXoJL6bnQ.png" /></figure><h4>Create an isolated custom assets directory</h4><pre>sudo mkdir -p /var/www/jitsi-custom/images<br>sudo mkdir -p /var/www/jitsi-custom/static<br><br># Copy your branding assets into the safe location<br>sudo cp /path/to/my-logo.png /var/www/jitsi-custom/images/watermark.png<br>sudo cp /usr/share/jitsi-meet/static/welcomePageAdditionalContent.html /var/www/jitsi-custom/static/</pre><h4>Configure Nginx location directives</h4><p>Open your active Jitsi Nginx server block:</p><pre>sudo nano /etc/nginx/sites-available/$(hostname -f).conf</pre><p>Inside the server block listening on port 443, insert the specific alias overrides <strong>above</strong> the general root block:</p><pre># ----------------------------------------------------<br># Upgrade-Safe Custom Branding Aliases<br># ----------------------------------------------------<br>location ^~ /images/watermark.png {<br>    alias /var/www/jitsi-custom/images/watermark.png;<br>    add_header Cache-Control &quot;no-cache, must-revalidate&quot;;<br>}<br><br>location ^~ /static/welcomePageAdditionalContent.html {<br>    alias /var/www/jitsi-custom/static/welcomePageAdditionalContent.html;<br>    add_header Cache-Control &quot;no-cache, must-revalidate&quot;;<br>}</pre><p>Two specific architectural choices make this block particularly resilient:</p><ul><li><strong>Prefix Matching (</strong><strong>^~)</strong>: Using ^~ instructs Nginx that once this prefix matches, it must stop checking for any subsequent regular expression locations (~ or ~*). Jitsi Meet&#39;s default Nginx configuration includes regular expressions for routing room names; using ^~ ensures that your custom asset aliases take absolute precedence without being bypassed by upstream regex rules.</li><li><strong>Cache-Control Headers</strong>: Web browsers aggressively cache static PNG images and HTML snippets. Without explicit cache instructions, attendees may continue seeing the default Jitsi logo or outdated announcements long after you have refreshed files on disk. Adding Cache-Control &quot;no-cache, must-revalidate&quot; forces the browser to revalidate the asset with Nginx on every request. If the file has not changed, Nginx replies with a fast 304 Not Modified, giving you instantaneous visual updates without wasting network bandwidth.</li></ul><h4>Test and reload Nginx</h4><pre>sudo nginx -t<br>sudo systemctl reload nginx</pre><p>Whenever apt-get upgrade updates jitsi-meet-web, it can freely replace /usr/share/jitsi-meet/images/watermark.png. Nginx will continue serving your file from /var/www/jitsi-custom/ without skipping a beat!</p><h3>Git time-capsule in /usr/share/jitsi-meet</h3><p>If you prefer modifying files directly in-place (for example, when tweaking complex CSS or JavaScript logic across multiple files), you can turn /usr/share/jitsi-meet into a local Git repository.</p><p>Version control acts like an operational time-capsule: it tracks all your modifications, alerts you when an upgrade changes upstream templates, and lets you reapply your changes smoothly.</p><h4>Initialise the local repository</h4><p>Ensure git is installed, navigate to the web root, and create the baseline commit:</p><pre>sudo apt-get install -y git<br>cd /usr/share/jitsi-meet<br><br>sudo git init<br>sudo git config user.name &quot;Jitsi Administrator&quot;<br>sudo git config user.email &quot;admin@localhost&quot;<br><br># Stage the untouched upstream installation<br>sudo git add .<br>sudo git commit -m &quot;Initial upstream baseline installation&quot;</pre><h4>Apply and commit custom modifications</h4><p>Make your changes to interface_config.js, title.html, and images, then commit them to a dedicated branch:</p><pre>sudo git checkout -b custom-branding<br>sudo git add -A<br>sudo git commit -m &quot;feat(branding): apply custom logos, watermarks, and welcome text&quot;</pre><h4>Upgrade routine: Stash, upgrade, and pop</h4><p>When package upgrades arrive, use Git to preserve your modifications:</p><pre>cd /usr/share/jitsi-meet<br><br># Stash active customisations<br>sudo git stash<br><br># Run the system package upgrade<br>sudo apt-get update &amp;&amp; sudo apt-get --only-upgrade install -y jitsi-meet-web<br><br># Commit new upstream files to repository<br>sudo git add -A<br>sudo git commit -m &quot;chore(upstream): update jitsi-meet-web package&quot;<br><br># Reapply custom branding branch modifications<br>sudo git stash pop</pre><p>If any conflict occurs (for instance, if upstream renamed a variable in interface_config.js), Git will highlight the exact lines requiring adjustment rather than silently overwriting your work.</p><p>With upgrades in check, let’s have a look at integrations with other systems.</p><h3>Integrate Google Calendar</h3><p>Coordinating virtual meetings often introduces unnecessary friction when attendees have to search through calendar invites, email threads, and messaging channels to find the correct room URL.</p><p>Jitsi Meet includes native support for Google Calendar synchronisation. When enabled, your instance surfaces an interactive agenda view directly on the landing page and within user settings, allowing participants to view their schedule and enter community meetups with a single click.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CCeBZfDIjDXgD9M-n_-IOw.png" /></figure><h3>Google Cloud project and OAuth credentials</h3><p>Because Part 1 of this series deployed our instance on Google Cloud Compute Engine, you already have access to the Google Cloud Console. To configure calendar synchronisation, create an OAuth 2.0 client:</p><ul><li><strong>Enable the API</strong>: In your Google Cloud project, navigate to <strong>APIs &amp; Services &gt; Library</strong>, search for <strong>Google Calendar API</strong>, and click <strong>Enable</strong>.</li><li><strong>Configure the OAuth Consent Screen</strong>: Under <strong>APIs &amp; Services &gt; OAuth consent screen</strong>, select <strong>External</strong> (for public community members) or <strong>Internal</strong> (for Google Workspace organisations). Enter your application title (e.g. <em>MSCC Meetup Calendar</em>) and contact information. Add the read-only scope: <a href="https://www.googleapis.com/auth/calendar.events.readonly">https://www.googleapis.com/auth/calendar.events.readonly</a></li><li><strong>Generate Web Credentials</strong>: Under <strong>APIs &amp; Services &gt; Credentials</strong>, click <strong>Create Credentials &gt; OAuth client ID</strong>.</li><li><strong>Application type</strong>: Web application.</li><li><strong>Name</strong>: Jitsi Meet Calendar Client.</li><li><strong>Authorised JavaScript origins</strong>: Enter your instance base URL (e.g. <a href="https://meet.mscc.mu)./">https://meet.mscc.mu).</a></li><li><strong>Authorised redirect URIs</strong>: Enter your instance OAuth callback endpoint: <a href="https://meet.mscc.mu/static/oauth.html">https://meet.mscc.mu/static/oauth.html</a></li><li><strong>Copy the Client ID</strong>: Google generates an alphanumeric string ending in .apps.googleusercontent.com. You do not need a client secret, as this authentication flow executes entirely in the client browser.</li></ul><p>Tip</p><p>If you leave your OAuth consent screen in <strong>Testing</strong> status, Google limits authentication strictly to 100 explicitly invited Google accounts. For open community instances, transition the consent screen to <strong>In production</strong> (or add your core team members to the test user list) to avoid access errors.</p><h3>Adjust the Jitsi configuration</h3><p>Once you have your OAuth Client ID, open your server configuration file:</p><pre>sudo nano /etc/jitsi/meet/$(hostname -f)-config.js</pre><p>Locate the calendar settings section and enable the feature alongside your Google Client ID:</p><pre>// ----------------------------------------------------<br>// Google Calendar Synchronisation<br>// ----------------------------------------------------<br>enableCalendarIntegration: true,<br><br>// Google API OAuth 2.0 Web Client ID<br>googleApiApplicationClientID: &#39;1234567890-abcdefghijklmnopqrstuvwxyz.apps.googleusercontent.com&#39;,</pre><p>Save the file. Because config.js is fetched dynamically by clients on each page load, there is no need to restart system services. The change takes effect immediately upon hard-refreshing your browser.</p><h3>The welcome page and settings experience</h3><p>With the configuration active, participants experience two integration touchpoints:</p><figure><img alt="MSCC Meet Landing Page Calendar Integration" src="https://cdn-images-1.medium.com/max/752/1*zwgHSdudLlZpviOszCE79Q.png" /><figcaption>MSCC Meet Landing Page Calendar Integration</figcaption></figure><figure><img alt="Calendar Settings Dialog" src="https://cdn-images-1.medium.com/max/628/1*vPBVDgK0XuauTnHMehfxCQ.png" /><figcaption>Calendar Settings Dialog</figcaption></figure><p><strong>Landing Page Agenda</strong>: Below the room name input, the <strong>Calendar</strong> tab displays a <em>“Connect your calendar”</em> call-to-action. Once authenticated, Jitsi displays upcoming meetings for the day. If a calendar invite contains a Jitsi meeting URL in its location or description, a prominent <strong>Join</strong> button appears next to the scheduled time.</p><p><strong>In-Meeting Preferences</strong>: Users can also link or disconnect their calendar account at any time by opening <strong>Settings &gt; Calendar</strong> and clicking <em>“Sign in with Google”</em>.</p><p>All OAuth tokens and calendar event payloads are processed and retained exclusively within the attendee’s browser local storage. The Jitsi server never stores, inspects, or proxies private calendar contents, ensuring complete user privacy.</p><h3>Desktop client integration (Jitsi Meet Electron)</h3><p>In addition to web browsers, participants can connect via the official cross-platform desktop application: <a href="https://github.com/jitsi/jitsi-meet-electron">Jitsi Meet Electron</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*uIGvSnXrcQ9hzG0cTHalpg.png" /><figcaption>Using the Jitsi Meet Desktop (Electron-based</figcaption></figure><p>To ensure that the Electron desktop wrapper can frame your server without security policy violations, verify that your Nginx SSL server block includes standard frame options:</p><pre>add_header X-Frame-Options &quot;SAMEORIGIN&quot;;</pre><p>The desktop client provides hardware push-to-talk hotkeys, system tray minimisation, and native screen-sharing selectors that bypass browser permission prompts.</p><h3>Mobile experience</h3><p>When community members open a meeting link on smartphones or tablets, their experience depends heavily on how your instance handles mobile clients. By default, Jitsi Meet prompts mobile visitors with a full-screen interstitial banner urging them to install the official mobile application.</p><p>Depending on your audience and operational needs, you can either streamline the in-browser WebRTC experience for friction-free joining or guide participants into the native mobile application configured for your custom domain.</p><h3>Seamless in-browser WebRTC</h3><p>If you run public webinars or developer meetups with casual attendees, forcing guests to download a mobile app creates immediate participation friction. Modern mobile browsers (such as Chrome for Android and Safari on iOS) fully support WebRTC audio, video, and screen viewing without requiring third-party software.</p><p>You can suppress the promotional install interstitial and allow participants to enter meetings directly within their mobile browser.</p><h4>Disable mobile deep linking</h4><p>Open your primary configuration file:</p><pre>sudo nano /etc/jitsi/meet/$(hostname -f)-config.js</pre><p>Add or adjust the deep-linking parameters:</p><pre>// ----------------------------------------------------<br>// Mobile Browser WebRTC Experience<br>// ----------------------------------------------------<br>// Disable the interstitial prompt that pushes native mobile apps<br>disableDeepLinking: true,<br><br>// In modern Jitsi Meet releases with nested configuration objects:<br>deeplinking: {<br>    disabled: true<br>},</pre><h4>Suppress promotional banners</h4><p>Next, disable the promotional banners in the interface configuration:</p><pre>sudo nano /usr/share/jitsi-meet/interface_config.js</pre><p>Set the mobile app promotion flag to false:</p><pre>// Hide the mobile app promotional banner<br>MOBILE_APP_PROMO: false,</pre><p>With these settings applied, attendees tapping a meeting link on their phone land straight in the prejoin lobby or video room inside their mobile browser.</p><p>Note</p><p>While in-browser mobile WebRTC is convenient for guests, mobile operating systems enforce aggressive background tab management. If an attendee locks their screen or switches apps, mobile Safari and Chrome may suspend video feeds. For regular team members or moderators, the native app offers superior stability.</p><h3>Native mobile app configuration</h3><p>For recurring community members and moderators who participate frequently from mobile devices, the official <a href="https://jitsi.org/api/">Jitsi Meet Mobile App</a> (available on iOS and Android) delivers native background audio processing, hardware battery optimisation, and incoming call notifications.</p><p>However, there is an important operational pitfall to avoid:</p><figure><img alt="Configuring the custom Server URL in Jitsi Meet mobile settings" src="https://cdn-images-1.medium.com/max/1024/1*WXXJcHH5HUAtNe_pKwFuCA.png" /><figcaption>Configuring the custom Server URL in Jitsi Meet mobile settings</figcaption></figure><p>By default, the Jitsi Meet mobile app connects to the public cloud infrastructure hosted at https://meet.jit.si. If an attendee installs the app from the store and enters a room name such as MSCCMonthlyMeetup, the application connects to public Jitsi infrastructure, leaving them isolated from your self-hosted community server on meet.mscc.mu!</p><p>To ensure mobile app users join your private instance:</p><p><strong>Configure the default server URL</strong>: Inside the mobile app, tap the <strong>Settings</strong> gear icon and set the <strong>Server URL</strong> field to your instance domain:</p><pre>https://meet.mscc.mu</pre><p>Once saved, all rooms created or entered from the app automatically route to your self-hosted infrastructure.</p><p><strong>Direct Joining via Deep Links</strong>: When deep linking remains enabled on your server, sharing a full meeting link (such as https://meet.mscc.mu/MSCCMonthlyMeetup) automatically prompts the phone to open the meeting inside the installed mobile app while passing your custom domain as the conference host.</p><h3>Retrospective note: Bare-metal VMs vs modern containers</h3><p>When this series was originally authored in 2020 during the rapid community pivot to remote collaboration, running standalone Debian VMs on Google Cloud Compute Engine was the standard deployment architecture for community servers.</p><p>Today, many engineers opt for containerised orchestration using <strong>Docker Jitsi Meet</strong> (docker-compose). The encouraging takeaway is that <strong>the underlying principles remain identical</strong>:</p><ul><li>Rather than modifying /usr/share/jitsi-meet/, Docker deployments map persistent local directories to container volume mounts (such as ~/.jitsi-meet-cfg/web/).</li><li>Rather than tweaking host Nginx configs, custom virtual locations are placed in containerised Nginx snippet directories (web/custom-snippets/).</li></ul><p>Understanding how the web client, configuration layers, and reverse proxies interact gives you total mastery over your video infrastructure, regardless of whether you deploy on bare metal or in containers.</p><h3>Summary and series recap</h3><p>Looking back at what we have covered across the series so far:</p><ul><li><a href="https://jochen.kirstaetter.name/install-jitsi-meet-on-gcp.html"><strong>Installation on GCP</strong></a>: Provisioning GCP Compute Engine VMs, firewall rules, and automated Let’s Encrypt SSL certificates.</li><li><a href="https://jochen.kirstaetter.name/authentication-jitsi-meet.html"><strong>Authentication and Security</strong></a>: Securing rooms with Prosody internal authentication and guest focus delegation in Jicofo.</li><li><strong>Interface Customisation and Branding</strong>: Tailoring features in config.js, branding the UI with logos and custom HTML, locking in upgrade persistence via Nginx virtual locations, and tuning client experiences for desktop and mobile devices.</li></ul><p>You now possess a private, branded, secure, and resilient video conferencing platform under your complete operational control.</p><h3>Share your Jitsi story</h3><p>What is your actual experience running or joining calls on Jitsi Meet? Did you learn the hard way about package upgrade wipeouts after a routine apt-get blew away your bespoke logos, or have you spent late nights wrestling with Nginx routing and mobile WebRTC permissions?</p><p>Which unforeseen pitfalls caught you completely off guard, what ingenious hacks did you deploy to keep your community connected, and what nagging reservations still make you look twice at commercial alternatives?</p><p>Do not keep those hard-earned lessons locked away on your staging box. Tell me about your setup, your triumphs, and your catastrophic misconfigurations on <a href="https://x.com/JKirstaetter">X (@JKirstaetter)</a>, compare notes on <a href="https://bsky.app/profile/jochen.kirstaetter.name">BlueSky (@jochen.kirstaetter.name)</a>, ping me on <a href="https://mastodon.social/@JKirstaetter">Mastodon (@JKirstaetter)</a>, or subscribe to the <a href="https://jochen.kirstaetter.name/rss/">RSS Feed</a> for more hands-on DevOps deep dives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=635eb51bd517" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enable authentication in your instance of Jitsi Meet]]></title>
            <link>https://medium.com/@jochen.kirstaetter/enable-authentication-in-your-instance-of-jitsi-meet-77edc3f60cbd?source=rss-63a3d7a84479------2</link>
            <guid isPermaLink="false">https://medium.com/p/77edc3f60cbd</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[jitsi]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Jochen Kirstätter]]></dc:creator>
            <pubDate>Wed, 09 Sep 2026 09:46:00 GMT</pubDate>
            <atom:updated>2026-09-09T09:46:00.977Z</atom:updated>
            <content:encoded><![CDATA[<p>A basic installation of Jitsi Meet gets you up and running within shortest time, probably in less than 15 minutes. There are hardly any configuration changes necessary. Most important information is a fully qualified domain name (FQDN), and that’s it.</p><p>This content been published <a href="https://jochen.kirstaetter.name/authentication-jitsi-meet">here</a> originally.</p><p>However such a default installation of Jitsi Meet is open. Meaning, that anyone knowing the URL of your server can create a new meeting room and start to have video conferences using your instance and probably causing additional cost.</p><p>In this second article on Jitsi Meet we are going to enable authentication to avoid any misuse from public users. Please read <a href="https://jochen.kirstaetter.name/install-jitsi-meet-on-gcp.html">Install Jitsi Meet on Compute Engine (GCP)</a> in case you have not created your own instance yet.</p><p>Securing your instance of Jitsi Meet requires three configuration changes plus the creation of user accounts with permission to host conference calls.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*td4L75_pgRQlZOWbefg60g.png" /><figcaption>Guests and non-authenticated users cannot create a meeting room</figcaption></figure><p>Let’s have a look at the architecture of Jitsi Meet to get a better understanding.</p><figure><img alt="Courtesy of [https://www.brring.com/2020/04/04/setting-up-a-jitsi-server-in-less-than-15-minutes/" src="https://cdn-images-1.medium.com/max/1024/1*RjFtpnZYuVG71IX1pbtMGw.png" /><figcaption>Courtesy of <a href="https://www.brring.com/2020/04/04/setting-up-a-jitsi-server-in-less-than-15-minutes/">https://www.brring.com/2020/04/04/setting-up-a-jitsi-server-in-less-than-15-minutes/</a></figcaption></figure><p>It is possible to allow only authenticated users for creating new conference rooms. Whenever a new room is about to be created Jitsi Meet will prompt for user name and password. After the room is created others will still be able to join from an anonymous domain.</p><h3>Extend the Prosody configuration</h3><p>The central component of Jitsi Meet is the Prosody XMPP server which is responsible for user management among other tasks, like authentication.</p><p>Open the configuration file of your domain with your preferred text editor.</p><pre>nano /etc/prosody/conf.d/$(hostname -f).cfg.lua</pre><p>Here you change the current value of <em>authentication</em> from anonymous to internal_hashed like so.</p><pre>VirtualHost &quot;meet.mscc.mu&quot;<br>        -- enabled = false -- Remove this line to enable this host<br>        -- authentication = &quot;anonymous&quot;<br>        authentication = &quot;internal_hashed&quot;<br>...</pre><p>Additionally, you add a new virtual host definition at the end of the same file.</p><pre>...<br>VirtualHost &quot;guest.meet.mscc.mu&quot;<br>    authentication = &quot;anonymous&quot;<br>    c2s_require_encryption = false</pre><p>Save the file to confirm the modifications**.**</p><p><strong>Note:</strong> The domain of the guest VirtualHost is internal only. It does not require any DNS record or SSL certificate.</p><p>The outcome is now that the primary VirtualHost of your Jitsi instance would require any kind of authentication to create a conference meeting room whereas the VirtualHost for guests still grants access to anonymous users.</p><h3>Add guest domain to Jitsi Meet frontend</h3><p>After adding the guest domain to the XMPP server component, you need to add this VirtualHost to the configuration object in the web frontend.</p><p>Open the config file with a text editor.</p><pre>nano /etc/jitsi/meet/$(hostname -f)-config.js</pre><p>Then you add the directive anonymousdomain into your hosts object.</p><pre>hosts: {<br>        // XMPP domain.<br>        domain: &#39;meet.mscc.mu&#39;,<br><br>        // When using authentication, domain for guest users.<br>        // anonymousdomain: &#39;guest.example.com&#39;,<br>        anonymousdomain: &#39;guest.meet.mscc.mu&#39;,<br>...</pre><p>Save and close the configuration file to confirm your modifications.</p><p>As you might see in the comment in the hosts sections, it already stipulates that your instance is going to use the new domain for guest users.</p><h3>Change Jitsi Conference Focus</h3><p>Next, you have to configure the <a href="https://github.com/jitsi/jicofo">Jitsi Conference Focus (jicofo)</a> component to allow requests from an authenticated domain only. For that you need to add the protected URL to the properties files. Open it with a text editor.</p><pre>nano /etc/jitsi/jicofo/sip-communicator.properties</pre><p>Add the key-value pair org.jitsi.jicofo.auth.URL=XMPP:&lt;domain&gt; at the end of the file, and save it.</p><pre>...<br>org.jitsi.jicofo.auth.URL=XMPP:meet.mscc.mu</pre><h3>Restart all Jitsi services involved</h3><p>With all changes mentioned above you need to restart the services to apply all modifications. Run the following commands or restart your VM instance completely.</p><pre>service prosody restart<br>service jicofo restart<br>service jitsi-videobridge2 restart<br>service nginx restart</pre><h3>Check the log files</h3><p>Should you come across some unexpected issues always have a look at the log files first. Here is a brief overview of where to check.</p><pre># Prosody<br>tail -f /var/log/prosody/prosody.log<br><br># Jicofo<br>tail -f /var/log/jitsi/jicofo.log<br><br># Jitsi video bridge<br>tail -f /var/log/jitsi/jvb.log<br><br># nginx<br>tail -f /var/log/nginx/error.log</pre><h3>Create your moderators</h3><p>For the last step, now that authentication is active, you need to create at least one user which is going to have permissions to create meeting rooms.</p><p>According to the architecture it is the Prosody component which is responsible for this part. The command prosodyctl helps you to manage your XMPP server and therefore your user base.</p><p>You can add and enable a user with the following command.</p><pre>prosodyctl register joki $(hostname -f) VerySecretPassword</pre><p>The syntax is described here.</p><pre>prosodyctl register --help<br>Usage: /usr/bin/prosodyctl register USER HOST [PASSWORD]<br> Register a user on the server, with the given password</pre><p>Unfortunately, this is <strong><em>not</em> GDPR-compliant</strong>, because “enabling users to set their password without the admin knowing it” is a basic and unavoidable security measure.</p><h3>Congratulations!</h3><p>You completed all necessary steps to enable authentication in your instance of Jitsi Meet. All steps described above are mainly based on the official guide to <a href="https://github.com/jitsi/jicofo#secure-domain">Secure domain on GitHub</a>.</p><p>Let’s try it…</p><h3>Authenticate against your instance of Jitsi Meet</h3><p>Open a browser and navigate to your URL of Jitsi Meet. The site should load as before and there are no obvious changes visible. Authentication is bound to the creation of a meeting room only.</p><p>Either you choose an existing meeting room or you enter a new name and click on GO to start the video conference session. If you are not authenticated the site will now place you in some kind of virtual lobby until a moderator or host arrives.</p><figure><img alt="Guests and non-authenticated users cannot create a meeting room" src="https://cdn-images-1.medium.com/max/952/1*CLb6meFEtVQVZTCANoDr_g.png" /><figcaption>Guests and non-authenticated users cannot create a meeting room</figcaption></figure><p>In case that you are the host of the meeting click on I am the host and you will be asked to enter your credentials. You can either enter just the user name without your domain or the fully qualified user name including the domain - both approaches will work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/952/1*-xLqOfdVDLYZlW1xjTH1Aw.png" /><figcaption>Enter your credentials to continue to your video conference</figcaption></figure><p>Enter your passphrase and click OK. With successful authentication against Prosody the Jitsi Meet component will grant you access to the meeting room and assign moderator permissions to your account.</p><p>Public access is still possible as soon as a moderator (host) is present in the meeting room.</p><figure><img alt="Guests can still access the meeting room, now that a moderator / host is present" src="https://cdn-images-1.medium.com/max/961/1*JhOe4Cpr80ImOldkN2OzFQ.png" /><figcaption>Guests can still access the meeting room, now that a moderator / host is present</figcaption></figure><p>As a moderator you will get additional options under Settings &gt; More which allow you to control what should happen when someone enters the meeting room, e.g. being automatically muted or not being visible to other participants.</p><figure><img alt="Additional settings to control access to the meeting space" src="https://cdn-images-1.medium.com/max/596/1*7pqbBgUHPdYOnhKtM63AXQ.png" /><figcaption>Additional settings to control access to the meeting space</figcaption></figure><p>Enjoy your next, secure video conference.</p><h3>Consider to set password per meeting room</h3><p>An additional level of protection against “<a href="https://en.wikipedia.org/wiki/Zoombombing">Zoom-bombing</a>” or unwanted intrusion into a video conference would be to activate the password of the meeting room.</p><p>Click on the i circle in the bottom right area and click on Add password in the popup dialog.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/662/1*Irc0x3-poxknonGCmD0Mig.png" /><figcaption>Set a room-specific password to avoid Zoom-bombing and unauthorised access</figcaption></figure><p>Enter your room-specific password and hit Enter to confirm your choice.</p><p><strong>Note:</strong> The password of a meeting room is not persistent and needs to set each time that you would join / start a conference call. You cannot launch a meeting room with an initial password already set.</p><h3>What’s Next?</h3><p>Perhaps you noticed that the visual appearance of the Jitsi Meet instance running for MSCC looks slightly different to the default installation.</p><p>Continue reading the next part of this series: <a href="https://jochen.kirstaetter.name/customise-jitsi-meet.html">Customise Your Instance of Jitsi Meet</a>, where we explore core feature configuration, visual branding, Google Calendar synchronisation, resilient Nginx upgrade persistence, and client endpoint setup across desktop and mobile devices.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77edc3f60cbd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Install Jitsi Meet on Compute Engine (GCP)]]></title>
            <link>https://medium.com/@jochen.kirstaetter/install-jitsi-meet-on-compute-engine-gcp-39253dbb2ca6?source=rss-63a3d7a84479------2</link>
            <guid isPermaLink="false">https://medium.com/p/39253dbb2ca6</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[jitsi]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Jochen Kirstätter]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 05:50:04 GMT</pubDate>
            <atom:updated>2026-09-07T05:50:04.536Z</atom:updated>
            <content:encoded><![CDATA[<p>Irrespective of the current situation I already had a look at the Jitsi Meet platform some time back last year. Due to a lack of necessity and organising most community meetings offline — both MSCC and GDG Mauritius — there was no motivation to look closer into any video conferencing platform.</p><p>This content been published <a href="https://jochen.kirstaetter.name/install-jitsi-meet-on-gcp">here</a> originally.</p><p>Inspired by the announcement that <a href="https://meet.mixp.org/">meet.mixp.org</a> offers free access to host video conferencing calls locally in Mauritius and the fact that past few meetings of the MSCC had been conducted virtually using <a href="https://meet.google.com/">Google Hangouts Meet</a>, I reserved some time to do a little research. The result is a series of tutorials on how to get started with <a href="https://jitsi.org/">Jitsi Meet</a>, how to customise it for your own branding, and how to enable more features beyond the basic installation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*NSZ3y4KNJkr0eAJxu2UUAg.png" /></figure><p>This first article describes the fundamental installation of Jitsi Meet on the <a href="https://cloud.google.com/">Google Cloud Platform</a>. Surely, the necessary steps shall be reproducible on other cloud computing platforms like Microsoft Azure or Amazon AWS.</p><h3>Prerequisites: Domain Name</h3><p>Before you start following the steps in this article you should consider to have a fully qualified domain name (FQDN) at hand. That domain will be used to access your Jitsi Meet server over the internet.</p><p>I’m going to use the subdomain meet.mscc.mu because the Jitsi Meet video conferencing system described here will be used for the <a href="https://www.mscc.mu/">Mauritius Software Craftsmanship Community (MSCC)</a> and associated user groups in Mauritius.</p><p>Ready?<br> Let’s log into <a href="https://console.cloud.google.com/">Google Cloud Console</a> and begin the installation.</p><h3>Define a permanent External IP address</h3><p>First, you reserve a static IP address. We are going to use this IP address for the DNS record of your FQDN and to attach it to the VM instance running Jitsi Meet server.</p><p>In Cloud Console navigate to <a href="https://console.cloud.google.com/networking/addresses/list">VPC network &gt; External IP addresses</a> and reserve a new static address. Although the IP address is not attached to anything yet we are going to use it shortly.</p><figure><img alt="Reserve a static external IP address" src="https://cdn-images-1.medium.com/max/820/1*NhOlozI15GnAXdEDmjskHA.png" /></figure><p>The result should look similar to this. Of course, your external IP address will be different.</p><figure><img alt="Overview of reserved external IP addresses" src="https://cdn-images-1.medium.com/max/953/1*xK5lmUgQG8zAn105DjaXpQ.png" /></figure><h3>Create a DNS entry</h3><p>Now, packed with the newly created IP address it is time to create a DNS record for the domain name you would like to use for the Jitsi Meet server. This step depends on your DNS nameserver provider.</p><p>I’m going to describe how it is done using <a href="https://dash.cloudflare.com/">Cloudflare</a>. Under DNS management create a new A record with the subdomain meet and the external IP address provided by Google Cloud Platform.</p><figure><img alt="Create an A record for your domain — here: Cloudflare DNS management" src="https://cdn-images-1.medium.com/max/1024/1*UXxIS75XkBDBXuQO3H_H9A.png" /></figure><p>The resulting DNS configuration should look similar to above. Global DNS propagation can take up to 24 hours and it is important to wait that your DNS record has been deployed successfully.</p><h3>Verify DNS configuration</h3><p>You can use any DNS query tool to verify this step. Depending on your OS either use dig or nslookup to check whether the DNS record has been distributed to the Cloudflare public DNS server.</p><pre>$ dig meet.mscc.mu @1.1.1.1<br><br>; &lt;&lt;&gt;&gt; DiG 9.11.3-1ubuntu1.11-Ubuntu &lt;&lt;&gt;&gt; meet.mscc.mu @1.1.1.1<br>;; global options: +cmd<br>;; Got answer:<br>;; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 43365<br>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1<br><br>;; OPT PSEUDOSECTION:<br>; EDNS: version: 0, flags:; udp: 1452<br>;; QUESTION SECTION:<br>;meet.mscc.mu.                  IN      A<br><br>;; ANSWER SECTION:<br>meet.mscc.mu.           300     IN      A       35.232.25.165</pre><pre>&gt; nslookup meet.mscc.mu 1.1.1.1<br>Server:  one.one.one.one<br>Address:  1.1.1.1<br><br>Non-authoritative answer:<br>Name:    meet.mscc.mu<br>Address:  35.232.25.165</pre><p>With proper DNS settings in place you are ready to continue with the installation of Jitsi Meet.</p><h3>Create a VM instance</h3><p>Log into Cloud Console and navigate to <a href="https://console.cloud.google.com/compute/instances">Compute Engine &gt; VM instances</a>. There click on Create instance and enter relevant information for your new VM instance.</p><p>The default values provided by GCP shall work just fine. However you might like to adjust region, zone and machine configuration according to your liking.</p><figure><img alt="Set up a VM instance to host Jitsi Meet server on GCP" src="https://cdn-images-1.medium.com/max/880/1*lWfdlqsvCAf6lMGXJRG_jg.png" /></figure><h3>Specify the hostname</h3><p><strong>Important:</strong> The initial configuration allows you to set a custom hostname for your instance and you should specify the prepared DNS name as such. This choice is permanent and cannot be changed later.</p><p>Click on Management, security, disks, networking, sole tenancy and enter your FQDN under Hostname.</p><figure><img alt="Enter your FQDN as hostname during creation of the VM" src="https://cdn-images-1.medium.com/max/524/1*YpgdFNORYyddHHosbv-2JA.png" /></figure><h3>Choose the External IP address</h3><p>While you are at the details of Networking click on the pen symbol of the Network interface and select the external IP address that we created earlier. The entry shall look like so.</p><figure><img alt="Attach the external IP address to the VM instance" src="https://cdn-images-1.medium.com/max/525/1*QX00FEzDBN2MqfhOyeIz4A.png" /></figure><p>Click Done when your networking options are complete.</p><p>If ever you missed the initial creation of an external IP address you can open the dropdown selection under External IP and choose to Create IP address. Give the new static IP address a name and click on Reserve.</p><figure><img alt="Late reservation of an external IP address is possible" src="https://cdn-images-1.medium.com/max/771/1*ASfEd5K9BmnuepFOUn73iQ.png" /></figure><p>However this still requires proper DNS configuration as described earlier.</p><h3>Configure firewall rules</h3><p>According to the quick install guide Jitsi Meet requires the following ports and protocols to allow traffic from the internet.</p><ul><li>80 TCP — aka HTTP traffic</li><li>443 TCP — aka HTTPS traffic</li><li>10000 UDP</li></ul><p>The first two ports can be configured during the creation of the VM instance. Tick the checkboxes in the Firewall section and the necessary rules will be applied during the creation of the virtual machine.</p><p>For the UDP port you are going to enter a Network tag for the moment. That tag is used to connect the VM instance to a (new) firewall rule.</p><figure><img alt="Allow HTTP/S traffic and enter a tag to link to another firewall rule" src="https://cdn-images-1.medium.com/max/529/1*tg0QwsoMnOt4zpw-Y2-bZg.png" /></figure><p>Finally, click on Create to complete your VM instance. This is going to take a few seconds and you will be notified as soon as the VM instance is ready.</p><figure><img alt="Overview of VM instances with External IP address and SSH access" src="https://cdn-images-1.medium.com/max/1024/1*Rzs5J93nFiwV2PdlgpWkhA.png" /></figure><h3>Create and verify firewall rules</h3><p>In order to create the third, remaining firewall rule you navigate to <a href="https://console.cloud.google.com/networking/firewalls/list">VPC network &gt; Firewall rules</a> and there you click on Create Firewall Rule to configure the missing information.</p><p>Under Target tags you enter the same value you used as Network tags during the configuration of the VM instance. This closes the link between the instance and this firewall rule.</p><p>The value for the Source IP ranges is 0.0.0.0/0 which represents any IP address from the internet.</p><p>Under Protocols and ports you tick UDP protocol and you enter the port number 10000.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*F2mKY9P41RPUtNwebgYT7Q.png" /></figure><p>Finally, click on Create to enable the firewall rule.</p><p>The result should look similar to the list of rules below.</p><figure><img alt="Partial list of firewall rules. The relevant rules for Jitsi Meet are shown" src="https://cdn-images-1.medium.com/max/910/1*PosWV8MczdGBzmd7H6b3Ig.png" /></figure><h3>Access the VM instance</h3><p>Navigate back to <a href="https://console.cloud.google.com/compute/instances">Compute Engine &gt; VM instances</a> and click on the SSH button of your instance. This should open a new browser window.</p><p><strong>Note:</strong> Eventually you have to allow Cloud Console to open popups first.</p><p>After a short initialisation the connection should be established and you are greeted by a bash prompt on Linux.</p><h3>Install Jitsi Meet software</h3><p>The following steps are based on the official <a href="https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md">Jitsi Meet quick install</a> guide on GitHub — with a few additional notes and modifications on my side.</p><h3>Check hostname</h3><p>First, verify the assignment of the Fully Qualified Domain Name (FQDN) with the following command:</p><pre>$ hostname -f<br>meet.mscc.mu</pre><p>At the same time check that the name resolution has been added to the hosts file.</p><pre>$ cat /etc/hosts<br>127.0.0.1       localhost<br>::1             localhost ip6-localhost ip6-loopback<br>ff02::1         ip6-allnodes<br>ff02::2         ip6-allrouters<br><br>10.128.0.2 meet.mscc.mu meet  # Added by Google<br>169.254.169.254 metadata.google.internal  # Added by Google</pre><h3>Run commands as user root</h3><p><strong>Note:</strong> Many of the installation steps require elevated privileges. If you are logged in using a regular user account, you may need to increase your permissions.</p><p>Either use sudo for individual commands or temporarily change user context and operate as user root.</p><pre>$ sudo -i</pre><p>Although not recommended it’s faster to complete the installation as root.</p><h3>Add the Jitsi package repository</h3><pre>echo &#39;deb https://download.jitsi.org stable/&#39; &gt;&gt; /etc/apt/sources.list.d/jitsi-stable.list <br>wget -qO -  https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -</pre><p>The Jitsi repository uses a secured URL which requires that you add the HTTPS transport option to apt, then you update the local repository cache, and finally you install the package of Jitsi Meet and all dependencies.</p><pre># Ensure support is available for apt repositories served via HTTPS<br>apt-get install -y apt-transport-https<br><br># Retrieve the latest package versions across all repositories<br>apt-get update<br><br># Perform jitsi-meet installation<br>apt-get install -y jitsi-meet</pre><p>During the process you will be asked to enter the FQDN or hostname of your instance of Jitsi Meet. Enter the hostname that we verified already and hit OK to continue the installation.</p><figure><img alt="Enter hostname used in Jitsi Videobridge" src="https://cdn-images-1.medium.com/max/908/1*YZ7lKf1O3LXcB0uPNZA6Hw.png" /></figure><p>Next, you will be ask to configure SSL certificate of your Jitsi Meet domain. Here keep the default selection to generate a self-signed certificate and hit OK.</p><figure><img alt="Choose the default option to generate an SSL certificate" src="https://cdn-images-1.medium.com/max/908/1*TEE1UqC4T4kxVcbP2c1d4Q.png" /></figure><p>We are going to generate an SSL certificate provided by <a href="https://letsencrypt.org/">Let’s Encrypt</a> in the next step.</p><h3>Install Let’s Encrypt certificate</h3><p><strong>Note:</strong> Verify that the DNS record has been assigned to your static external IP address and it has been distributed globally before you try to apply the Let’s Encrypt SSL certificate. See Verify DNS configuration above on how to do that.</p><p>At the time of writing there was a small issue running the script as described on GitHub: <a href="https://github.com/jitsi/jitsi-meet/issues/5929">Lets Encrypt setup error about missing file #5929</a>. The workaround is to create the expected deployment hook manually yourself <strong>before</strong> running the certificate installation script.</p><pre># Workaround for missing deployment script<br>mkdir -p /etc/letsencrypt/renewal-hooks/deploy/ <br>touch /etc/letsencrypt/renewal-hooks/deploy/0000-coturn-certbot-deploy.sh<br>chmod +x /etc/letsencrypt/renewal-hooks/deploy/0000-coturn-certbot-deploy.sh</pre><p>Now, run the following shell script as mentioned in the quick install guide.</p><pre>/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh</pre><p>The script is going to ask you for an email address to send notifications from Let’s Encrypt to. Then your terminal is going to provide you with tons of information and the outcome should look similar to below. Look for Congratulations! to be sure that the SSL certificate has been successfully requested from <a href="https://letsencrypt.org/">Let&#39;s Encrypt</a> and applied to your system.</p><figure><img alt="Successful generation and distribution of SSL certificate by Let’s Encrypt" src="https://cdn-images-1.medium.com/max/796/1*pUI7lXPbqzKnNvRvobH5tQ.png" /></figure><p>Basically your installation is complete now.<br> You shall be able to load your FQDN in your browser. In case you run into any trouble kindly repeat the steps above or refer to the official <a href="https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md">Jitsi Meet quick install</a> or the <a href="https://community.jitsi.org/">Jitsi Community Forum</a>.</p><p>However there are probably some additional considerations prior to operating your instance of Jitsi Meet server on the internet.</p><h3>Adjust nginx configuration file</h3><p>The default configuration of <a href="https://www.nginx.com/">nginx</a> created by the Jitsi Meet package is not optimal and you should make a few changes to it. Open the file with your preferred text editor</p><pre>nano /etc/nginx/sites-enabled/meet.mscc.mu.conf</pre><h3>Change the default protocol to HTTP/2</h3><p>Look for the listen directives and add the value http2 at the end of both. It shall look like so.</p><pre>server {<br>    listen 443 ssl http2;<br>    listen [::]:443 ssl http2;<br>...</pre><h3>Change SSL protocol versions and ciphers</h3><p>By default nginx is enabled to support TLS 1.0, TLS 1.1 and TLS 1.2. However the two former protocols are legacy protocol that shouldn’t be used. TLS v1.0 and TLS v1.1 have been deprecated in January 2020 by modern browsers. Hence you should change the ssl_protocols directive like so.</p><pre># ssl_protocols TLSv1 TLSv1.1 TLSv1.2;<br>    ssl_protocols TLSv1.2;</pre><p>Depending on the <a href="https://www.nginx.com/">nginx</a> version TLS 1.3 might be an additional option. You might consider to replace the existing directive of SSL ciphers with the following value.</p><pre>ssl_ciphers &#39;ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256&#39;;</pre><p>The <a href="https://ssl-config.mozilla.org/">Mozilla SSL Configuration Generator</a> is definitely worth a look. The Intermediate configuration would be the recommended choice. Perhaps you might like to read <a href="https://github.com/ssllabs/research/wiki/SSL-and-TLS-Deployment-Best-Practices">SSL and TLS Deployment Best Practices</a> for more background information.</p><h3>Add more HTTP headers</h3><p>Next, you should define a few more HTTP header directives to improve your default configuration. Open the nginx config file again and add the following lines right after the existing add_header directive related to <a href="https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security">HSTS</a>.</p><pre>add_header X-Content-Type-Options nosniff;<br>    # Don&#39;t use with iFrames, e.g. Jitsi Meet Desktop (Electron) app<br>    add_header X-Frame-Options SAMEORIGIN;<br>    add_header X-XSS-Protection &quot;1; mode=block&quot;;<br>    add_header Referrer-Policy no-referrer-when-downgrade;</pre><p><strong>Note:</strong> The Jitsi Meet Electron application for desktop systems cannot load your instance if the HTTP header X-Frame-Options has been set. Either comment or remove that directive if you are planning to use the application.</p><p>Save the configuration after each change and run a configtest.</p><pre>service nginx configtest<br>[ ok ] Testing nginx configuration:.</pre><p>If the result is OK restart nginx as usual. Otherwise, inspect the log file located at /var/log/nginx/error.log for any error entries.</p><pre>service nginx restart</pre><p>In case that you are interested to see the impact of your changes open the <a href="https://www.ssllabs.com/ssltest/index.html">Qualys SSL Server Test</a> and validate your domain.</p><h3>Increase number of processes and open files</h3><p>The quick install guide mentions that the default configuration of a system is good for less than 100 participants. To avoid running into any unexpected situations I suggest that you increase that value already now.</p><p>Open the file /etc/systemd/system.conf and add the following lines at the end.</p><pre>DefaultLimitNOFILE=65000<br>DefaultLimitNPROC=65000<br>DefaultTasksMax=65000</pre><p>Reload the systemd changes on a running system and restart your Jitsi instance with those two commands.</p><pre>systemctl daemon-reload<br>service jitsi-videobridge2 restart</pre><p>To verify that the settings have been applied run the following command and check the value of Tasks: XX (limit: 65000).</p><pre>service jitsi-videobridge2 status<br>● jitsi-videobridge2.service - Jitsi Videobridge<br>   Loaded: loaded (/lib/systemd/system/jitsi-videobridge2.service; enabled; vendor preset: enabled)<br>   Active: active (running) since Thu 2020-04-16 11:23:08 UTC; 14s ago<br>  Process: 7896 ExecStartPost=/bin/bash -c echo $MAINPID &gt; /var/run/jitsi-videobridge/jitsi-videobridge.pid (code=e<br>xited, status=0/SUCCESS)<br> Main PID: 7895 (java)<br>    Tasks: 38 (limit: 65000)<br>...</pre><h3>Confirm your installation is working</h3><p>Open a new browser tab or better an incognito window and navigate to the FQDN you specified during the installation. You shall be greeted by the Jitsi Meet default page.</p><figure><img alt="Welcome to your own Jitsi Meet video conferencing system" src="https://cdn-images-1.medium.com/max/950/1*uNZYYGKMd1e3Sipr-GEtzg.png" /></figure><h3>Congratulations!</h3><p>When you click on the gear symbol in the top right corner your browser should ask for permissions to access microphone and camera.</p><figure><img alt="Grant permissions to access your microphone and camera" src="https://cdn-images-1.medium.com/max/807/1*7M1mYtK4eLCk74bJ0o1DuA.png" /></figure><p>Click Allow in both cases and continue to configure your devices you would like to use in Jitsi Meet.</p><figure><img alt="It’s working — customise your attendee profile" src="https://cdn-images-1.medium.com/max/619/1*w00nj2BiZMyNHHXTlTs1-g.png" /></figure><p>Change to the tab Profile to provide more information like your displayed name in the meeting rooms. On the tab More you are able to configure your preferred language.</p><p>Finally, enter any value to start a new meeting and click on GO.</p><figure><img alt="Enter any meeting room in CamelCase writing" src="https://cdn-images-1.medium.com/max/757/1*xzc04s9k9mJ1oTS_IoHQrw.png" /></figure><p>The use of camel-case writing forms the URL to access the meeting and is automatically converted into blanks after you entered the meeting room.</p><figure><img alt="CamelCase is converted to blanks in the room name" src="https://cdn-images-1.medium.com/max/720/1*BfBhslro5nrEoyRQfjLhUg.png" /></figure><p>Enjoy your very own Jitsi Meet video conferencing system.</p><h3>Automate it with gcloud</h3><p>All steps above can be executed by using gcloud commands. Best might be to use your instance of Cloud Shell to create a VM instance and to install Jitsi Meet.</p><p>Make sure that you have a domain name prepared.</p><h3>Create the infrastructure</h3><p>You would probably adjust the environmental variables at the top to change region, zone, instance name and your DNS hostname.</p><pre># Define your preferences and values - to CHANGE!<br>export REGION=us-central1<br>export ZONE=us-central1-a<br>export VM_INSTANCE=mscc-jitsi-dummy<br>export FQDN=meet.mscc.mu<br><br># Enable Compute Engine<br>gcloud services enable compute.googleapis.com<br><br># Reserve and retrieve static IP address<br>gcloud compute addresses create $VM_INSTANCE-ip --project=$DEVSHELL_PROJECT_ID --description=&quot;Static external IP address for Jitsi Meet VM instance&quot; --region=$REGION<br>export IP=$(gcloud compute addresses describe $VM_INSTANCE-ip --region=$REGION --format=&#39;get(address)&#39;)<br><br># Create VM instance with hostname and attach IP address<br>gcloud beta compute --project=$DEVSHELL_PROJECT_ID instances create $VM_INSTANCE --hostname=$FQDN --zone=$ZONE --machine-type=n1-standard-1 --subnet=default --address=$IP --network-tier=PREMIUM --tags=jitsi,http-server,https-server --image=debian-9-stretch-v20200309 --image-project=debian-cloud --boot-disk-size=10GB --boot-disk-type=pd-standard --boot-disk-device-name=$VM_INSTANCE --reservation-affinity=any<br><br># Attach firewall rules (might be already present, no big deal)<br>gcloud compute --project=$DEVSHELL_PROJECT_ID firewall-rules create default-allow-http --direction=INGRESS --priority=1000 --network=default --action=ALLOW --rules=tcp:80 --source-ranges=0.0.0.0/0 --target-tags=http-server<br>gcloud compute --project=$DEVSHELL_PROJECT_ID firewall-rules create default-allow-https --direction=INGRESS --priority=1000 --network=default --action=ALLOW --rules=tcp:443 --source-ranges=0.0.0.0/0 --target-tags=https-server<br>gcloud compute --project=$DEVSHELL_PROJECT_ID firewall-rules create default-allow-10k --description=&quot;Allow UDP packets for VM instance running Jitsi Meet server&quot; --direction=INGRESS --priority=1000 --network=default --action=ALLOW --rules=udp:10000 --source-ranges=0.0.0.0/0 --target-tags=jitsi<br><br># Display external IP address and connect to instance using SSH<br>echo $IP<br>gcloud compute ssh $VM_INSTANCE --zone=$ZONE</pre><p>After execution you are going to see the external IP address in the Shell, and you should be connected to the new VM instance.</p><p>In case that the remote VM instance does not respond to the SSH connection or times out, wait a short while and repeat the last command to SSH into the instance.</p><p>Now is the right time to verify that your DNS record is up-to-date and matches the external IP address of your VM instance <strong>before</strong> you continue to install Jitsi Meet.</p><h3>Install Jitsi Meet server</h3><p>This paragraph summarizes the commands used above to install Jitsi Meet server. They should be run as user root. Change into an interactive session of user root first.</p><pre>sudo -i</pre><p>Then run the following to complete the basic installation of Jitsi Meet server on the VM instance.</p><pre># Increase number of processes and open files<br>cat &gt;&gt; /etc/systemd/system.conf &lt;&lt;EOF<br>DefaultLimitNOFILE=65000<br>DefaultLimitNPROC=65000<br>DefaultTasksMax=65000<br>EOF<br>systemctl daemon-reload<br><br># Add the package repository<br>echo &#39;deb https://download.jitsi.org stable/&#39; &gt;&gt; /etc/apt/sources.list.d/jitsi-stable.list <br>wget -qO -  https://download.jitsi.org/jitsi-key.gpg.key | sudo apt-key add -<br><br># Ensure support is available for apt repositories served via HTTPS<br>apt-get install -y apt-transport-https  <br># Retrieve the latest package versions across all repositories<br>apt-get update  <br># Perform jitsi-meet installation<br>apt-get install -y jitsi-meet</pre><p>Last, prepare the system for an SSL certificate provided by Let’s Encrypt by running the following commands.</p><p><strong>Note:</strong> Without properly configured DNS this is going to fail.</p><pre># Workaround for missing deployment script<br>mkdir -p /etc/letsencrypt/renewal-hooks/deploy/ <br>touch /etc/letsencrypt/renewal-hooks/deploy/0000-coturn-certbot-deploy.sh<br>chmod +x /etc/letsencrypt/renewal-hooks/deploy/0000-coturn-certbot-deploy.sh<br><br># Get SSL certificate from Let&#39;s Encrypt<br>/usr/share/jitsi-meet/scripts/install-letsencrypt-cert.sh</pre><p>You have to specify an email address to receive notifications regarding your certificates from Let’s Encrypt.</p><p>Congrats, your Jitsi Meet server is now operational. Maybe you like to review the nginx changes described above to improve your setup a little bit.</p><h3>Securing your Jitsi Meet server</h3><p>The default installation in this article is kind of basic and provides you a jumpstart to run your own video conferencing system. In the next article of this series I’m going to describe how you <a href="https://jochen.kirstaetter.name/authentication-jitsi-meet.html">enable authentication and secure your Jitsi Meet instance</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39253dbb2ca6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with SQL Server on GCP]]></title>
            <link>https://medium.com/google-cloud/getting-started-with-sql-server-on-gcp-692e4ac44cad?source=rss-63a3d7a84479------2</link>
            <guid isPermaLink="false">https://medium.com/p/692e4ac44cad</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <dc:creator><![CDATA[Jochen Kirstätter]]></dc:creator>
            <pubDate>Sat, 18 Jan 2020 00:39:56 GMT</pubDate>
            <atom:updated>2020-02-07T17:46:01.337Z</atom:updated>
            <cc:license>http://creativecommons.org/publicdomain/zero/1.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="Few settings and you have SQL Server running on Google Cloud Platform" src="https://cdn-images-1.medium.com/max/942/0*WmeRoa73RIBFeMM2.png" /><figcaption>Few settings and you have SQL Server running on Google Cloud Platform</figcaption></figure><p>When talking about Cloud SQL instances on the Google Cloud Platform usually it relates to flexible and convenient handling of MySQL. Eventually, and probably less common, someone might actually speak about PostgreSQL. However in recent times Google added a third option to the Cloud SQL service: Microsoft SQL Server.</p><p><a href="https://cloud.google.com/sql/">Cloud SQL</a> is a fully managed relational database service for MySQL, PostgreSQL, and SQL Server on the Google Cloud Platform (GCP).</p><blockquote><em>Cloud SQL is fully compatible with applications using MySQL, PostgreSQL, and SQL Server. You can connect with nearly any application, anywhere in the world. Cloud SQL automates backups, replication, and failover to ensure your database is reliable, highly available, and flexible to your performance needs.</em></blockquote><p>The described feature-set of SQL Server on GCP lists everything needed for secure, high-available, high performance, and scalable solutions. Cloud SQL instances can be easily reached from other GCP services, including App Engine, Compute Engine, Kubernetes Engine, as well as your workstation. BigQuery is capable to query directly an existing Cloud SQL database.</p><p>There is an interesting read on the Google Cloud blog: <a href="https://cloud.google.com/blog/products/databases/leave-no-database-behind-with-cloud-sql-for-sql-server">Leave no database behind with Cloud SQL for SQL Server</a> that gives a bit more insight information of the new service and what features are coming soon.</p><h3>Create a Cloud SQL instance of SQL Server</h3><p>Log into the Cloud Console and choose the menu entry SQL in the navigation bar on the side. In case your selected project does not have any instances you click on Create Instance to continue.</p><figure><img alt="Microsoft SQL Server is offered as Cloud SQL instance" src="https://cdn-images-1.medium.com/max/949/1*nEd9FwKuYi4xMPe-ejU9DA.png" /><figcaption>Microsoft SQL Server is offered as Cloud SQL instance</figcaption></figure><p>Next, select the SQL Server option on the right-hand side to begin the configuration of SQL Server.</p><figure><img alt="Although marked as beta it’s ready to use (as time of writing)" src="https://cdn-images-1.medium.com/max/951/1*4CMOw3P3801P0coO9rN7Aw.png" /><figcaption>Although marked as beta it&#39;s ready to use (as time of writing)</figcaption></figure><p>There are just a few parameters to enter and you are literally good to go, read: Click on the Create button at the bottom of the page. Most probably it is interesting to review each single configuration setting to gain more familiarity with Cloud SQL in the first place.</p><p>Give your instance a unique identifier, either set or generate a password for your administrative user.</p><figure><img alt="Wide range of options to configure a SQL Server based Cloud SQL instance" src="https://cdn-images-1.medium.com/max/955/1*2aa6E3F2F-lfzJnbfUdnqg.png" /><figcaption>Wide range of options to configure a SQL Server based Cloud SQL instance</figcaption></figure><p><strong>Note:</strong> Your default service admin username is sqlserver. Instead of the common sa username. A generated password would look something like this: d3Ptgz30EAiygtMn</p><p>Then choose from the available editions of SQL Server 2017. If you are familiar with SQL Server and its licensing you know that the various editions have different features, limitations and cost factors. The cost calculation of SQL Server is neatly described here: <a href="https://cloud.google.com/sql/pricing#sql-server">Cloud SQL Pricing</a>.</p><figure><img alt="Various editions of SQL Server 2017 are available. More versions to be expected (soon)" src="https://cdn-images-1.medium.com/max/942/1*SsMJEvwjkAbDTIgCAhkXDA.png" /><figcaption>Various editions of SQL Server 2017 are available. More versions to be expected (soon)</figcaption></figure><p>You can activate automatic backups and high availability of your Cloud SQL instance, if needed. However this might incur additional cost.</p><figure><img alt="Easy to configure backup and high availability" src="https://cdn-images-1.medium.com/max/941/1*YFpaT-kfmZSQDmpVXWq-yQ.png" /><figcaption>Easy to configure backup and high availability</figcaption></figure><p>The configuration of Cloud SQL for SQL Server offers a section called Flags and parameters that allows you to go deep down into the nuts and bolts of SQL Server configuration as it might be needed for a production system.</p><figure><img alt="If needed, you can configure a SQL Server instance with all kind of flags" src="https://cdn-images-1.medium.com/max/504/1*SvHahd9tPHeRGxIu8TXiuw.png" /><figcaption>If needed, you can configure a SQL Server instance with all kind of flags</figcaption></figure><p>This list of flags is exhaustive and advanced settings shall be known to an experienced database administrator. For testing or development purpose you might skip this area.</p><p>Similarly the section on Maintenance allows you to define your preferred window of downtime.</p><figure><img alt="Define the maintenance period according to your conveniences" src="https://cdn-images-1.medium.com/max/486/1*SJJOREYgi57dp-nybrcoGQ.png" /><figcaption>Define the maintenance period according to your conveniences</figcaption></figure><p>Lastly, hit the Create button at the bottom of the page to create an instance of Cloud SQL for SQL Server. It takes a few minutes to deploy. Perhaps time for a little stretch and a sip of fluids.</p><p>After completion you see the instance on the overview page of Cloud SQL.</p><figure><img alt="Cloud SQL instance running SQL Server: Ready to rumble" src="https://cdn-images-1.medium.com/max/951/1*AuxDiDZyHFo_fZg1DKrwoA.png" /><figcaption>Cloud SQL instance running SQL Server: Ready to rumble</figcaption></figure><p>The instance connection information is the essential information you would need to connect your client applications to the instance. Click on the instance identifier to access the overview and dashboard of SQL Server.</p><figure><img alt="Easy access to connect to a Cloud SQL instance" src="https://cdn-images-1.medium.com/max/334/1*e4qwLlbiRuJo-k66y1imsQ.png" /><figcaption>Easy access to connect to a Cloud SQL instance</figcaption></figure><p>Copy the information and use any client application to connect to your newly created instance of SQL Server.</p><p><strong>Note:</strong> The identifier of an instance is blocked for a certain time. Thus after deleting a Cloud SQL instance you won’t be able to use the same identifier instantly.</p><h3>Using gcloud to create an instance</h3><p>Make sure that your gcloud SDK environment has the beta component installed before trying to create an instance of Cloud SQL for SQL Server. You can verify this with the following command.</p><pre>&gt; gcloud components list </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*_bobpZLHeWH-tiKJ1Y0tfQ.png" /></figure><p><strong>Note: </strong>You must use gcloud version 243.0.0 or later.</p><p>With beta component installed you can run this command to create a new instance of Cloud SQL for SQL Server.</p><pre>&gt; gcloud beta sql instances create gcp-sqlserver `<br> --database-version=SQLSERVER_2017_STANDARD `<br> --cpu=2 `<br> --memory=7680MiB `<br> --root-password=d3Ptgz30EAiygtMn</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*q4K73UyWB4QK3tFz0GQfVw.png" /></figure><p>The new instance is created in the active GCP project using its pre-configured region and zone settings. If needed, you could also add the command switches --project, --region, and --zone to assign different values than the default ones.</p><p>After successful creation you have to set the password for the user sqlserver. That password should be different than the root password previously given to create the Cloud SQL instance itself.</p><pre>&gt; gcloud beta sql users set-password sqlserver `<br> --instance=gcp-sqlserver `<br> --password=d3Ptgz30EAiygtMn</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*IK4OE_HTAxIU2De4QHBiOw.png" /></figure><p>Using the command above enables you also to re-set the password of the user at a later stage. For example, in case you forgot it.</p><p>The documentation about <a href="https://cloud.google.com/sql/docs/sqlserver/create-instance">Creating instances</a> goes into more details and provides information on all command switches. It describes a few constraints regarding the configuration of the underlying machine types.</p><h3>Connect to Cloud SQL instance</h3><p>You will be able to connect to your newly created instance of SQL Server using the public IP address in familiar fashion as you would connect to an on-premise instance. Provided that you whitelisted your IP address.</p><p>Following are a few screenshots of various client applications, like SQL Server Management Studio, Azure Data Studio and Visual Studio 2019. Other client applications should work as expected.</p><figure><img alt="Using various client applications to connect to Cloud SQL instance" src="https://cdn-images-1.medium.com/max/1024/1*LS-oRvObcgqWplmZsyBztQ.png" /><figcaption>Using various client applications to connect to Cloud SQL instance</figcaption></figure><p>Connecting to the Cloud SQL instance using ODBC driver works perfectly well, too.</p><h3>Considerations for public access to Cloud SQL</h3><p>During the creation steps of a Cloud SQL instance you might have seen the section on Connectivity. By default the option of assigning a Public IP is checked.</p><p>GCP recommends the use of <a href="https://cloud.google.com/sql/docs/sqlserver/sql-proxy">Cloud SQL Proxy</a> instead of whitelisting IP address ranges to enable external applications to connect to the instance.</p><figure><img alt="Default access to Cloud SQL suggests use of Cloud SQL Proxy" src="https://cdn-images-1.medium.com/max/478/1*529B36Ucxq7PNqEy9uj0Kg.png" /><figcaption>Default access to Cloud SQL suggests use of Cloud SQL Proxy</figcaption></figure><p><strong>Note: </strong>Using the Cloud SQL Proxy requires that the <a href="https://console.cloud.google.com/flows/enableapi?apiid=sqladmin&amp;redirect=https://console.cloud.google.com&amp;_ga=2.205742355.-1649613044.1542902327">Cloud SQL Admin API is enabled</a> in your GCP project.</p><figure><img alt="Verify that the Cloud SQL Admin API is enabled in your GCP project" src="https://cdn-images-1.medium.com/max/695/1*LneOBYnE3HsqMq0i1YB_EQ.png" /><figcaption>Verify that the Cloud SQL Admin API is enabled in your GCP project</figcaption></figure><p>The following diagram shows how the proxy connects to Cloud SQL:</p><figure><img alt="Image courtesy of Google Cloud documentation: Cloud SQL Proxy" src="https://cdn-images-1.medium.com/max/725/1*DDVFrrT4VsZzt2J8Xd8iQA.png" /><figcaption>Image courtesy of Google Cloud documentation: <a href="https://cloud.google.com/sql/docs/sqlserver/sql-proxy">Cloud SQL Proxy</a></figcaption></figure><p>Download the Cloud SQL Proxy to your machine. Open a console or terminal window and navigate to the folder you stored the downloaded file. Eventually rename the binary to cloud_sql_proxy (depending on your OS). More details are described in <a href="https://cloud.google.com/sql/docs/sqlserver/connect-admin-proxy">Connecting a client using the Cloud SQL Proxy</a>.</p><p>The following command establishes the remote connection and listens for incoming connections on localhost.</p><pre>&gt; .\cloud_sql_proxy.exe -instances=gcp-sql-server:us-central1:gcp-sqlserver=tcp:1433</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*2-12iC0KHD96ohd3OA2kmw.png" /></figure><p>As soon as Cloud SQL Proxy is ready for new connections you can configure your client application to use localhost or simply . to connect to your instance.</p><p>Press Ctrl+C to stop the execution of Cloud SQL Proxy and close connections to your instance.</p><p>You should explicitly specify the TCP port to connect to your Cloud SQL instance. Otherwise you might get an unsupported network: unix error.</p><pre>&gt; .\cloud_sql_proxy.exe -instances=gcp-sql-server:us-central1:gcp-sqlserver</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/851/1*jjGL_MyA1D1XEHxiVhR4sQ.png" /></figure><p>On a machine with active Hyper-V you might observe another problem.</p><pre>&gt; .\cloud_sql_proxy.exe -instances=gcp-sql-server:us-central1:gcp-sqlserver2=tcp:1433</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*DPK_ZEV2SQJvB48cCHmQjw.png" /></figure><p>The reason here is that port 1433 is managed by Hyper-V and not accessible by other applications. You can check the list of reserved TCP ports using the following command.</p><pre>&gt; netsh int ipv4 show excludedportrange protocol=tcp</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*DwFqvp9JkehEtfaOw5_7IA.png" /></figure><p>The solution is either to reserve TCP port 1433 while Hyper-V has been temporarily disabled.</p><pre>&gt; # Disable Hyper-V <br>&gt; dism.exe /Online /Disable-Feature:Microsoft-Hyper-V </pre><pre>&gt; # Reserve the port 1433 <br>&gt; netsh int ipv4 add excludedportrange protocol=tcp startport=1433 numberofports=1 </pre><pre>&gt; # Re-enable Hyper-V <br>&gt; dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*01xinPw1_BAbFfNn53K0JQ.png" /></figure><p>Or to use a non-reserved TCP port instead.</p><pre>&gt; .\cloud_sql_proxy.exe -instances=gcp-sql-server:us-central1:gcp-sqlserver=tcp:1470</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*zKWx7_lXUc9lrQM1pN_LWA.png" /></figure><figure><img alt="Connecting to local Cloud SQL Proxy and custom TCP port" src="https://cdn-images-1.medium.com/max/1024/1*rR1H0OT5JR1Yd3YR9Zl7gA.png" /><figcaption>Connecting to local Cloud SQL Proxy and custom TCP port</figcaption></figure><p>The later approach provides better flexibility without <em>messing up</em> the local machine with permanent changes. You might not remember this change in a few weeks time.</p><p>However Cloud SQL Proxy requires the installation of an agent on every client that connects to the instance. There are a few steps necessary to enable proper invocation of Cloud SQL Proxy in a production environment. And in some cases this might also not be possible for various reasons.</p><p>For more information about Cloud SQL Proxy options and connection strings, see the <a href="https://github.com/GoogleCloudPlatform/cloudsql-proxy">Cloud SQL Proxy GitHub page</a>.</p><p>Alternatively authorisation for any external networks is possible. You would specify at least one network in <a href="https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation">CIDR notation</a> (Classless Inter-Domain Routing) to allow access to your instance.</p><figure><img alt="Whitelist your host or network using CIDR notation" src="https://cdn-images-1.medium.com/max/500/1*_NDRGD-55nOVv6liAncZEg.png" /><figcaption>Whitelist your host or network using CIDR notation</figcaption></figure><p>Authorising external hosts or networks is the easier option and my current choice for Cloud SQL instances used for development or staging environments. Nonetheless, Cloud SQL Proxy is more secure and with a little practice shall be your preferred way to connect to an instance.</p><p>Your mileage might differ. Maybe you give me your reasoning in the comment section below.</p><h3>Thoughts about Cloud SQL for SQL Server</h3><p>Using the SQL Server option of Cloud SQL instances does come without major surprises and you should be up and running in shortest time.</p><p>GCP’s managed relational database service offers the full range of features available in SQL Server. By choosing the edition of SQL Server you have full control over functionality and pricing.</p><p>Compared to Microsoft’s Azure SQL Database it shall be noted that SQL Server on GCP currently runs as virtual machine, read: using predefined images of Compute Engine, under the hood.</p><figure><img alt="Cloud SQL of SQL Server seems to run as a VM" src="https://cdn-images-1.medium.com/max/386/1*A05IdXcJJ7mN6bYc8Q9hxg.png" /><figcaption>Cloud SQL of SQL Server seems to run as a VM</figcaption></figure><p>However your Cloud SQL instances are not visible under VM instances of your Compute Engine area.</p><p>Your instance of Cloud SQL for SQL Server unsurprisingly runs on a Linux VM, precisely on Ubuntu 16.04 LTS (64-bit; at the time of writing). You can check the environment executing the following query in any SQL client application.</p><pre>Select @@version;</pre><p>The text response should look similar to this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*lj4lkQAd6BoqpnPbwhU_DQ.png" /></figure><p>Given the underlying Linux operating system there are also a number of <a href="https://cloud.google.com/sql/docs/sqlserver/features#sqlserver-unavailable">SQL Server features unavailable for Cloud SQL</a>. Always consult with the official documentation before migrating your on-premise databases to GCP shall be part of the assessment and evaluation phase.</p><p>Although the Cloud SQL for SQL Server instance <a href="https://cloud.google.com/sql/docs/sqlserver/configure-ssl-instance#server-certs">is configured with a custom TLS certificate out of the box</a> it would <a href="https://cloud.google.com/sql/docs/sqlserver/connect-admin-ip#connect-ssl">require to register the certificate authority (CA) on the client</a> to enable encrypted connectivity. In case that you set the Encrypt=yes ODBC connection string value on your client the connection will not be established and quits with an error message.</p><p>Instead, according to documentation, Cloud SQL for SQL Server can be connected using a <a href="https://cloud.google.com/sql/docs/sqlserver/connect-admin-proxy">Cloud SQL Proxy</a>, which will establish secured connection using an ephemeral TLS certificate that’s automatically rotated.</p><p>Investigating how both options work is beyond the scope of this article. Maybe I will look into that in the future.</p><p>Creating a new instance of Cloud SQL for SQL Server, restoring an existing database backup (not documented above) and connecting any client application to Cloud SQL is done with a few steps and might take you a few minutes only.</p><p>My impression of Cloud SQL for SQL Server is quite positive. I like the idea to run SQL Server databases on GCP together with other services like Compute Engine, App Engine, Kubernetes Engine, or even BigQuery to analyse data.</p><p>Let’s see when this managed service reaches GA. SQL Server 2019 should be an additional choice next to the current SQL Server 2017. And whether there will be a connector for Cloud SQL for SQL Server in <a href="https://datastudio.google.com/">Google Data Studio</a> in the (near) future.</p><p><em>Originally published at </em><a href="https://jochen.kirstaetter.name/sql-server-on-gcp/"><em>https://jochen.kirstaetter.name</em></a><em> on January 18, 2020.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=692e4ac44cad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-cloud/getting-started-with-sql-server-on-gcp-692e4ac44cad">Getting Started with SQL Server on GCP</a> was originally published in <a href="https://medium.com/google-cloud">Google Cloud - Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Essentials for software developer or any computer job]]></title>
            <link>https://medium.com/@jochen.kirstaetter/essentials-for-software-developer-or-any-computer-job-15ccae9c616d?source=rss-63a3d7a84479------2</link>
            <guid isPermaLink="false">https://medium.com/p/15ccae9c616d</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Jochen Kirstätter]]></dc:creator>
            <pubDate>Mon, 21 Jan 2019 11:57:03 GMT</pubDate>
            <atom:updated>2019-01-21T12:43:46.358Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBP6sZnMI6fBvEpqtiIKnA.jpeg" /><figcaption>Take care of yourself first, and then do your job as requested</figcaption></figure><p>I have been talking about the following on many occasions during the last years already. Actually, it is always part of my consulting services when companies ask for advice on what they should do to improve the overall satisfaction of their software developers. But in general, it’s pretty simple: The following are my essentials for any software developer or craftsman that is taking her or his profession seriously.</p><p>Originally, I started my list with the first four topics only but experience taught me that there is more to this. And even nowadays, I would clearly say that this overview scratches the surface only.</p><h3>Touch-typing</h3><p>After being introduced to a team of software developers and/or testers by project or company management, I really enjoy myself to ask this particular question at a very early stage:</p><blockquote><strong><em>“Do you touch-type?”</em></strong></blockquote><p>I can tell you the expressions of their faces says more than any written book I’ve read so far. It’s absolutely amazing how such a simple question puts everyone in the room into a dazzling state and gets them to look, uhm sometimes even to gaze at me with a touch of glare in their eyes, as if I just spoke in an unknown language. The reactions are mixed but usually the responses are similar to this short selection:</p><ul><li>“What?”</li><li>“Sorry, I don’t understand.”</li><li>“What do mean by touch-typing?”</li><li>“No… ?”</li></ul><p>Honestly, I have to admit that I totally understand this kind of answer based on the fact that absolutely nowhere young programmers or developers are educated and trained in an efficient way to use their daily tools of future work. Seriously, that question would be comparable to ask an architect whether she uses a calculator on her job. Only, that her reply would be more like this: “Of course.”</p><p>So what is the actual problem about the fact that most developers I meet here on the island are not capable to touch-type, or sometimes don’t even know what I’m actually talking about? Sincerely, I have no straight answer to this but it seems obvious to all of them that working 6+ hours per day at the PC, using the keyboard to get the work done, doesn’t necessarily require to be fast and efficient.</p><blockquote><em>Definition of TOUCH-TYPE</em></blockquote><blockquote><em>: to type by the touch system<br> — touch typist </em>noun</blockquote><blockquote><em>Source: Definition taken from Merriam-Webster — </em><a href="https://www.merriam-webster.com/dictionary/touch-type"><em>https://www.merriam-webster.com/dictionary/touch-type</em></a></blockquote><p>Know your tools… well, getting a glimpse at the various curriculum at the tertiary educational institutes reveals a little bit more. Touch-typing isn’t part of the education and therefore ignored. Any software developer without touch-type capability would have difficulties with my equipment — <a href="https://www.amazon.com/gp/product/B003F7WXTG/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B003F7WXTG&amp;linkCode=as2&amp;tag=geblbyjo-20">das keyboard</a> Ultimate:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*2iK_Tujp1Cdd68SK" /><figcaption><em>das keyboard Ultimate is a keyboard with blank keys and the ultimate experience of touch-typing</em></figcaption></figure><p>Most people really don’t understand the consequences. It’s not only about time, effort and cost but also plays a great role in daily motivation. I know that developers want to <strong>write</strong> code first, uhm, maybe I should say to <strong>type</strong> code first. But what’s the purpose of creating wonderful code when your physical capabilities are far behind your mental ones? It’s like producing a lot of output that gets finally stuck in the I/O buffers of your body.</p><h3>Latest generation of hardware and software</h3><p>Obviously this should be a no-brainer but reality bites and quite often developers’ machines are not top-notch. There are various reasons for that and hundreds of excuses made by an employer but frankly speaking at least every two to three years latest it is necessary to upgrade the work equipment. Again, this is also something I clearly advice to other companies: Faster machine, less time-consuming and more efficiency of their developers and software testers. When I begin to work with new teams I like to get a better understanding of their opinion about their work, and as you might have guessed already… The computer they are using is usually part of those conversations. Either because I ask about it or they already tell me that they are not happy about their PC. Usually, they have more powerful machines at home, either for gaming or to develop on private projects. Imagine the frustration they have coming to work and only finding a dead-slow machine. The pain of waiting until the IDE has started and loaded the recent projects finally. Some of them even switch on the machine, wait to login and then go for their cup of coffee until auto-started software applications enter a state of readiness.</p><p>In rare cases I witnessed that they even brought in their own laptop and left alone the hardware provided by their employer. How embarrassing this might be…</p><p>Anyway, latest hardware means faster processing, lower latency and higher productivity of each single employee. Or at least it is plausible to cut off that argument that a job couldn’t be done due to hardware-related limitations, etc. blah blah.</p><p>Oh before I forget to write about that one: Get yourself at least a second screen!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*zgvPHL8zvWbG-A_O.png" /><figcaption><em>Working with multiple screens increases a software developers productivity</em></figcaption></figure><p>No matter the screen size, okay at least 19&quot; should do, put an additional screen on your desk. If you are working on a laptop, use the VGA or HDMI output for the better. In worst case you could use an older machine and <a href="https://jochen.kirstaetter.name/synergy-easy-share-of-keyboard-and-mouse-between-multiple-computers/">install Synergy on both of them</a>.</p><p>The rise in your productivity using a second screen compared to switching applications is outstanding. And the return of investment (ROI) is incredible fast. I really wonder how archaic certain software companies are when they don’t provide a second screen to their employees. Here is a little anecdote from the past: It was on my explicit request that my former employer started to introduce additional screens at work desks after I simply demonstrated to the manager that it is more efficient and productive to work on multiple screens. At that time I was used to work on three screens since years on my private machine at home, and it was absolutely frustrating to go to work. A couple of days later, I got a new graphics card, a second screen and my boss was overly happy with his own dual-screen machine. ;-)</p><p>Next, let’s talk about software. Once again, stay on top of the game and work with the latest and greatest version that is currently on the market. Not only to show your commitment to your job but also to have access to the state-of-the-art on productivity. Just recently, I worked as consultant for a local company here in Mauritius and honestly I was shocked to see the numerous installations of Visual Studio 2005 on their Windows 7 machines. And to make things even worse, team leaders had either Visual Studio 2008 or 2010 on their machines. Taking into consideration that Visual Studio 2012 was in the final stages to hit the market, I urged them to plan and run a general upgrade on all machines.</p><p>Eventually, you might ask for the reason. Well, there were several of them and I’m going to discuss them in no preferential order.</p><h3>Cost of licenses</h3><p>True, software licenses do cost money and unfortunately it isn’t obvious to some people that you have to take expenses on licenses into your annual budget planning. So no money planned, no upgrades available. Interestingly, while addressing this dilemma to my clients they are not aware of certain subsidizes programmes offered by the software producers. For example, as <a href="https://partner.microsoft.com/">Registered Microsoft Partner</a> you can purchase tailor-made variations of MSDN at an affordable price.</p><p>I’m always working on the latest available version of <a href="https://microsoft.com/vstudio">Microsoft Visual Studio</a>, Microsoft SQL Server or <a href="https://xamarin.com/">Xamarin Studio</a>. And if time allows even on the beta versions…</p><h3>Project circumstances</h3><p>The project is targeted to version X of the operating system and has to work with version Y of that product. Well, software changes and so should your development environment. There have been rare cases that a newer operating system simply sucked but in general go for the latest. Simply to leverage the improvements, read: bug fixes, and the new features that those software packages are offering. And to be prepared just in case that the client is going to ask you:</p><blockquote><em>“Is (y)our software working properly on the upcoming OS?”</em></blockquote><p>It’s always better to say something like this</p><blockquote><em>“Yes, it does (with some minor modifications). We already tested it some weeks/months ago while in beta stage.”</em></blockquote><p>than to shrug your shoulders and respond something like that “We don’t know.”</p><h3>Maintenance of deployed applications</h3><p>Oh yes, the crux with legacy code and the demons from the past. Well, in that case do yourself a big big favour and virtualise the environment. Simple as that, get a copy of either Microsoft Hyper-V, <a href="https://www.virtualbox.org/">Oracle VirtualBox</a> or <a href="https://www.vmware.com/">VMware Workstation or Player</a>, and move that old-fashioned piece of code over there. I’m going to write more on software virtualisation later in this article.</p><h3>Proper chair</h3><p>Remember what I wrote about touch typing? As a software developer you are likely to sit between six and eight hours every day at your workplace. Okay, there are these ‘unpleasant’ interruptions to either have a break or to attend a meeting but at the end of the day you are sitting most of the time at your desk. Either to code, to test or to read about your active tasks. Again, I think it is absolutely essential that you have an ergonomic chair that is well-suited for your body. Don’t save money on your health! In case that you’re employed and not comfortable with your chair or desk, speak to your manager or superior and evaluate possible solutions. It will be in their interest that you are confident and happy to come to work instead of having that annoying tension in your right shoulder or aches in your spine after an intensive coding session.</p><p>You will be surprised what a difference a good chair can make compared to one of those standard office chairs that you get for cheap. and it doesn’t have to be expensive but at least there should be a couple of decent features:</p><ul><li>Height adjustable</li><li>Adjustable back shield</li><li>Support for your lower spine and pelvis</li><li>Adjustable arm rests</li><li>Mesh fabrics</li></ul><p>Well, you might think that I can easily speak of that being self-employed. But hey, no wait a second… even being an employer I took care of the well-being of my employees at their work space. As said, it is crucial that you feel comfortable at work.</p><blockquote><strong><em>Comfort = happiness = motivation = results</em></strong></blockquote><p>It’s that simple!</p><p>Again, when consulting companies I usually ask them whether they have an initial budget for each new employee or even an annual allowance for the existing ones that could be used for the working environment. Of course, there is none… What would be the benefit of this? Hm, isn’t it obvious that if an employee is allowed to ‘design and implement’ her work desk based on her choices is eventually higher bonded emotionally to this environment and therefore less likely to change later on? No?</p><h3>Virtualisation and isolated project environments</h3><p>This might not be applicable in all cases but nonetheless I think it is worth to mention and discuss it here, too. Frankly speaking, I use virtualisation of software since more than a decade. If I remember correctly, I used to have an early copy of VMware Workstation at that time, and it was quite an experimental experience to run multiple copies of Windows on the same computer. But it was absolutely delightful to be able to work on Windows 2000 and to test the software on Windows 98 or Windows NT 4.0 without the necessity of having another physical machine. Actually, virtualisation software is always one of the first software packages that I install on a new (or re-installed) machine.</p><p>Furthermore, as soon as you are working on multiple projects or for a number of clients, virtualisation always provides me with a clean development environment. Do you remember the old days of DLL hell? Yes? Well, I don’t! ;-)</p><p>When I was assigned to work a new project I either asked the responsible project manager to give me a virtual machine, or if not available I created a master image which I put an the company’s file server for all my team mates. The purpose of the virtualised environment is simply to avoid any kind of unpredictable behaviour of your development conditions. Furthermore, I am able to design and create the virtual image exactly to the likings of one of the customer machines. Later on, I used to run VMware Converter in order to virtualise one of the client’s computer into a virtual one. This way, I was able to develop, run and test the software under more ‘real’ conditions.</p><p>And compared to my colleagues I had absolutely no trouble to install patches, upgrades and newer versions of software packages that are involved in the development process of a particular project. If it happened that it didn’t work for the better, revert to latest snapshot and tada I’m back on track without any serious delays or whatsoever. Again, this also allows any developer to install and experience new versions of their IDE or additional software packages. Well, at that time it was mainly about incompatibility of different ActiveX controls or versions of Microsoft Office.</p><p>In case that you have to provide support for older operating systems for your customers. No problem, put that old-faggot in a VM and enjoy the latest OS you can get on your amazing hardware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*CF57nNomhIW1TizG.png" /><figcaption><em>Virtualise your work environment to ease your life</em></figcaption></figure><p>Need to test your latest web project with various browsers on another operating system or older versions of a particular browser, use a virtual machine and be happy!</p><p>Don’t forget that this also shows your expertise and knowledge towards your clients. If it runs on your machine doesn’t necessarilty mean that it runs on any machine. So be prepared and test it as much as you can. I recently had the situation that one of my clients had their website designed and implemented by another web designer. Fair enough everything was displayed and working as expected until I started to run my usual cross-OS and cross-browser tests in order to check my modifications in the code behind. You can’t imagine the visual differences on various browsers on Mac OS X, Linux, Android or an iOS-based device. ‘Unfortunately’, it was a real eye-opener for the client and more work for the web designer to improve the site.</p><h3>Ergonomic desk and working environment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/358/0*rRinkgwsqOEixGMU.jpg" /><figcaption><em>Source:imgur.com</em></figcaption></figure><p>Well, this chapter is related to your proper choice of chair but goes a little bit beyond that. I’m going to leave my point of view on the working desk, on some accessories and constraints on your surrounding. You should pay some attention to your work desk, mainly on the height of the surface which is supposed to align properly with the position of your arms, especially your wrists. In case that you don’t have access to a height-adjustable desk, you might be surprised what wonders a couple of bricks can do…</p><p>Talking about elevation, last year I saw a couple of alternatives to the conventional sitting position. Personally, I was mainly impressed by the concepts of the standing desk and the treadmill desk. The first one comes in quite handy and could be realised easily with only a few additional items whereas the latter might not be the best choice for your surrounding after all. But in case that you are working in your noise-reduced cubicle or even in your own office room. Yes, why not work-out while pouring those challenging software requirements into lines of code and test cases.</p><p>Next, take care that you spend some bucks on the keyboard, mouse, touch pad or trackball that you are using all day long. Based on my own experience I can tell you to take this dead-serious. At the beginning of my programmer’s career I was always wondering about a tensed neck and shoulder. Finally, I found out that this was caused by hand movements on the mouse! And as soon as I replaced the mouse with a trackball I never had any issues of that kind anymore. There are serious, chronically injuries reported for any kind of typing work. Don’t ruin your health because you (or rather your employer) saved some bucks on a proper keyboard. It’s absolutely not worth it. The problem here is that the symptoms are not visible at the beginning but slowly sneak in after some months or even years of working at the desk. Listen to your body and change your equipment in case of problems. Just give it a try and see how it works.</p><p>Also, take care that your surrounding is calm and quiet. Put your maximum effort into your working comfort. If there’s a problem, address it — ad hoc. Do not ignore it or push it away from you. Again, if you are not happy with your workspace your motivation will start to decay. Treat yourself with a professional environment and also don’t be afraid of talking to your manager. It is very simple to describe your show-case and to proof that the circumstance might have a negative impact on your ability to focus, to concentrate and to deliver proper results as expected.</p><p>A quick and cheap solution to ‘dis-connect’ yourself from your surrounding is to put on headphones or earplugs. Not only do you block any disturbing sounds but you also visualise to your colleagues a simple yet effective ‘Do not disturb’. Again, I can tell you out of my own experience it works incredible well. I used to yell (and sometimes even swear) at my mates when they came to my desk and talked to me out of the blue. Guys, my apologies for that but we found a solution. After I discussed this with my boss, we came up with a simple system that in case of questions or issues to speak about to notify each other through an instant message. It worked flawlessly from day one on, and was quickly adapted by all colleagues.</p><p>This paragraph might be restricted to offices in Mauritius only but you never know… Comfortable temperature!</p><p>I cannot recall how many times I went into a freezer instead of an office for software developers here over the island. It is sheer insanity of some companies on how they set the temperature of their air conditioning. As a rule of thumb the inside temperature should not exceed a difference of 5 degrees Celsius compared to the outdoor temperature. Anything else is not healthy and will get you sick. Can you imagine to see computer workers sitting in long-sleeves or even cardigans at their PC while everything else outside is literally melting away and daring for water? No? Then you should come to Mauritius…</p><h3>Clean desk policy</h3><p>Another hot topic that you should pay some attention to are those ‘unnecessary extras’ on your work desk.</p><blockquote><em>Golden rule #1:</em><strong><em> No food on or near the desk!</em></strong></blockquote><p>Seriously, do not keep any kind of food or snacks or whatsoever edible in the reachable surrounding of your work desk. It is not only disgusting to have crumbs of bread between the keys of a keyboard but also unhealthy for your body as you tend to eat mindless and unconsciousness. And leaving your desk to have a drink or to have a snack gives you the ability to chat and exchange with your co-workers, too.</p><p>Please, feel free and tell me in the comment section about how your desktop currently looks like. If you’d like to, take a picture and send it to me via email. I would be glad to write a follow-up article on this one with your contributions, seriously. Looking at my desk at the moment, I’m not too happy either. And as a matter of fact I just interrupted my work on this article, cleared up my desk and took a picture for you:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*TpB2jMtI8o8c-m8J.png" /><figcaption><em>Keep your desk as clean as possible to avoid any kind of distraction</em></figcaption></figure><p>Now, I’m feeling more comfortable and more important: Less distracted!</p><blockquote><em>Golden rule #2: </em><strong><em>Divide your daily tasks into chunks!</em></strong></blockquote><p>You don’t have to monitor your email inbox every minute, don’t need those nasty notification popups, or check your buddies’ status on any social network. Instead, just have your instant messaging software up and running minimized, and focus on your main work: Coding.</p><p>Same as you are off from your desk occasionally, take care of this kind of tasks on specific times or bind them to other activities. For example, my mail client is usually closed during the day and only on certain activities, like ie. going to the tea kitchen to drink some water or to have my lunch break, etc. I check my mails and reply to them immediately. Don’t forget, email is actually an asynchronous way of communication and you might assume that your communication partner is <strong>not</strong> expecting an answer within a couple of minutes. If they do, sorry then the choice of medium is rather poor; in such cases it would be better to use either instant messaging or pick up the phone and call the person.</p><blockquote><em>Golden rule #3: </em><strong><em>Put your mobile away!</em></strong></blockquote><p>If your (personal) cellular or your smartphone isn’t involved into your development process, simply do yourself a favour and put it out of your sight. Best would be to switch it into ‘Meeting’ profile and simply leave it in your bag. Please don’t forget that you are at work, and not somewhere at a cafe or in a pub.</p><p>But there might be some kind of emergency case, you might argue. True but honestly, everyone is (or should be) aware of that you are actually at work and that they should call at the office in order to reach you. And let’s not forget that the battery could be down, you forgot your mobile at home, etc. So, in case of an emergency it is way safer to call at the office.</p><h3>Access to literature and training</h3><p>Apart from writing software it is absolutely compulsory for any serious software developer to read books, blog articles and technical advisories, to watch tutorials or even to attend conferences on the technology you are working in. Actually, this is common to any kind of profession! Maybe I might be wrong here but for example doctors have to document their annual progress on latest research and products in the medical field. And so should software developers, too.</p><ul><li>When was the last time that you read a book on a specific technology?</li><li>Do you know how many software-related books you read during a year?</li><li>Did you read any book since you left university?</li></ul><p>Again, these are some of my standard questions when working with a new team of software developers. As for my part, I read approximately 5 to 6 technical titles in one year. Sometimes, I don’t even need the content on an active project but the title did attract my attention and therefore I go for it. Interestingly, there had been occasions where that non-related title gave me an advantage on future work.</p><p>Nowadays, there are endless possibilities to gain access to high-quality material, especially in the field of software development. If you are a Windows developer go and check out <a href="https://msdn.microsoft.com/">MSDN</a> and <a href="https://technet.microsoft.com/">TechNet</a>. Microsoft’s latest achievement is called <a href="https://jochen.kirstaetter.name/microsoft-virtual-academy/">Microsoft Virtual Academy</a> which provides online material and video courses on specific topics — for free! The recorded material is top-notch and you are able to download it for latter reference. Furthermore, I highly recommend you to get a subscription to one of the many eLearning platforms like <a href="https://pluralsight.com/training">Pluralsight</a>, <a href="https://www.lynda.com/">Lynda</a>, <a href="https://tekpub.com/">TekPub</a>, etc. just to name a few. And not to forget, check out the online tutorials from tool and libraries; ie. <a href="https://tv.telerik.com/">Telerik TV</a> is a great resource in case you are working with their products.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CBP6sZnMI6fBvEpqtiIKnA.jpeg" /><figcaption>Allocate designated time in yor weekly schedule to learn and advance your career</figcaption></figure><h3>Prepare for professional certifications</h3><p>Pick up the challenge and <a href="https://jochen.kirstaetter.name/learning-content-for-mcsds-web-applications-and-windows-store-apps-using-html5/">go for certifications</a>. Yes, certifications will help you massively to know where you are standing with your knowledge, how to isolate blank spots and give you a deeper insight on the technologies you are dealing with on a daily base. Depending on your position, you should classify certifications as an investment into your future and to be able to stand out against other competitors on the market.</p><p>As an employee you might like to discuss certifications as being part of your annual performance report. Not only do you show your employer clearly that you care for your job but it also increases your value for your employer. And honestly, it is a simple win-win situation for both parties. You get the chance to proof your knowledge and the certifications are personal, and your employer knows that you are able to deliver high quality results at a certain standard.</p><p>Learning on the job or during your spare time is essential as a <a href="https://manifesto.softwarecraftsmanship.org/">software craftsman</a>. Keep yourself educated and valuable to yourself, your employer and your clients.</p><p><em>This article was originally posted here: </em><a href="http://jochen.kirstaetter.name/blog/development/essentials-for-software-developer.html"><em>Get Blogged by JoKi</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15ccae9c616d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Impressions from DevFest Mauritius 2018]]></title>
            <link>https://medium.com/@jochen.kirstaetter/impressions-from-devfest-mauritius-2018-83874bb956b4?source=rss-63a3d7a84479------2</link>
            <guid isPermaLink="false">https://medium.com/p/83874bb956b4</guid>
            <category><![CDATA[devfeststories]]></category>
            <category><![CDATA[gdg]]></category>
            <category><![CDATA[google-developer]]></category>
            <category><![CDATA[devfest18]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[Jochen Kirstätter]]></dc:creator>
            <pubDate>Thu, 13 Dec 2018 08:16:53 GMT</pubDate>
            <atom:updated>2018-12-13T08:16:53.880Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jcEB5EuU2ymgOS11FrOMjg.png" /><figcaption>Fantastic vibes and lots of excitement during DevFest Mauritius 2018 — image credit: Hayley Kirstätter</figcaption></figure><p>In the spirit of continuous learning all your life the GDG Mauritius organised their first full day conference. It is called a DevFest and is fully supported by Google Developers and the Google Developers Group programs. We teamed up with the Developer Students Club (DSC) at the African Leadership Campus to offer multiple tracks of technical presentations and workshops/codelabs to interested attendees.</p><h3>A few statistics of DevFest Mauritius</h3><p>Being the GDG Mauritius’ first ever DevFest we are really happy about the outcome of the event and would like to share a few figures with you.</p><ul><li>20 Sessions (2 workshops/codelabs)</li><li>15 Speakers (1 Female)</li><li>110 Attendees (30 Females)</li><li>Over 500 pictures in our <a href="https://photos.app.goo.gl/T5H2NbkY5QyrsXKz9">Photos album</a></li></ul><p>Some snapshots below which can hardly carry the excitement of attendees at DevFest. Please check out the album on Photos, place your Likes and leave a comment or two for us. And in case that you were part of DevFest Mauritius please upload your own pictures and videos to the album. Much appreciated!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*McJglzJiuTAa6zkK4jukqg.jpeg" /><figcaption>having a great time at DevFest Mauritius 2018</figcaption></figure><h3>What was going on at DevFest?</h3><p>Of course, there had been technical talks on various topics. Let me give you a brief summary of what has been addressed:</p><ul><li>Angular — lots of Angular actually</li><li>Flutter in all variations</li><li>Vue.js</li><li>Progressive Web Apps (PWAs)</li><li>Google APIs and Google Local Guides</li><li>Kubernetes</li><li>Digital Accessibility</li><li>Tips &amp; tricks on Searchability and gRPC communication</li></ul><p>Surely, we are going to elaborate more on those topics during the upcoming months. Attendees had way more questions to answer than time was available for some speakers to address each and every one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hz2dMhEYzROAbzjnRYoimQ.jpeg" /><figcaption>Attendees during one of the codelabs run at DevFest Mauritius</figcaption></figure><h3>An empty stomach doesn’t like to study…</h3><p>We had an absolutely tasty and rich buffet of dishes — veg and non-veg -, great variety of salads and a selection of juices provided by the canteen of the African Leadership Campus.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xPUnuMRTJnUbFYxFqD05wQ.jpeg" /><figcaption>Gourmet cuisine for DevFest attendees. And lots of conversations and networking…</figcaption></figure><p>We noticed that there were second rounds…</p><h3>Welcome to VueVixens Mauritius</h3><p>Only a few weeks earlier I had an exchange on Twitter with Humeira about the possibility to speak about Vue.js during DevFest Mauritius. What started with a relatively small request of proposals quickly turned into the creation of a new IT community — VueVixens Mauritius — as a local chapter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*X1QnpaMllJ4sfsG4jVsfTA.jpeg" /><figcaption>First presentation and workshop on Vue.js by VueVixens lead Humeira</figcaption></figure><h3>A Big Win for GDG Mauritius as a community</h3><p>We were able to extend our reach into new areas and to attract new interested parties to come and attend the sessions. Particularly we worked together with the DSC ALU which helped us with the formal aspects of the event, like registration desk, badges, hand out of t-shirts and guiding attendees in general. Also, we are happy to have reached approx. 25% female participation (attendees) but are worried about our single female presenter who did an amazing job — both her talk and her workshop were well-received. Overall it was a great networking experience, and so far we got solely positive feedback from all sides.</p><h3>Shout out and Thanks!</h3><p>Our gratitude to everyone behind this campaign at Google Developers and GDG world wide. Thank you so much to enable us to bring more Google technology to the local IT geeks. And thanks to your detailed style guides and the provided material it was a breeze for us to organise.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FIlv3W2OURVc%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DIlv3W2OURVc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FIlv3W2OURVc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/07316ab8c70df5eeafa4875042dffb2c/href">https://medium.com/media/07316ab8c70df5eeafa4875042dffb2c/href</a></iframe><h3>Interested to read more?</h3><p>This article was originally published here: <a href="https://www.mscc.mu/devfest-mauritius-2018/">https://www.mscc.mu/devfest-mauritius-2018/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qih2JUULvUrYlZmRo8Qixg.jpeg" /><figcaption>Registration desk to hand out badges and swag during DevFest Mauritius</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83874bb956b4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>