<?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[Monitive — Once Upon A Site - Medium]]></title>
        <description><![CDATA[Adventures in the path of shaping a brighter, better Internet - one site at a time. - Medium]]></description>
        <link>https://medium.com/once-upon-a-site?source=rss----1a1fe0429be0---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Monitive — Once Upon A Site - Medium</title>
            <link>https://medium.com/once-upon-a-site?source=rss----1a1fe0429be0---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:22:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/once-upon-a-site" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Migrating our Blog back to our website]]></title>
            <link>https://medium.com/once-upon-a-site/migrating-our-blog-back-to-our-website-bfc078410aff?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/bfc078410aff</guid>
            <category><![CDATA[monitive]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Thu, 04 Mar 2021 20:09:48 GMT</pubDate>
            <atom:updated>2021-03-04T20:09:48.830Z</atom:updated>
            <content:encoded><![CDATA[<p>Two years ago I decided to migrate our Monitive blog to a Medium publication called Once Upon A Site. This happened for several reasons, including the fact that we are getting more readers on Medium than we were getting on our blog at the time.</p><p>Of course, all while ignoring all there is to SEO.</p><p>This was a good call at the time. Since then I’ve learned a whole lot about content, publishing platforms, proprietary software, and especially about actively contributing to creating content on other platforms.</p><p>This includes content on social media.</p><p>And since almost nothing is forever in this world, I decided to move it back to our website. This includes all the articles already published on Medium. I hope I find a backup of our old website so that I can also migrate the articles that we had before we migrated to Medium.</p><p>The important part here is that you can set a canonical URL to a story on Medium. This tells Google that the story has been originally published on a different website, so we don’t have to take down the posts already published there.</p><p>It’s been over 10 years now since Monitive exists and I find it somehow romantic to have the whole trail of adventures and challenges laid out in a single, public place.</p><p>Another challenge is promoting the blog. But that’s for another day.</p><p><strong>Read our blog (from now on) at </strong><a href="https://monitive.com/blog/"><strong>monitive.com/blog</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfc078410aff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/migrating-our-blog-back-to-our-website-bfc078410aff">Migrating our Blog back to our website</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why we ditched Lumen PHP]]></title>
            <link>https://medium.com/once-upon-a-site/why-we-ditched-lumen-php-b7ab2bcefff9?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/b7ab2bcefff9</guid>
            <category><![CDATA[freyja]]></category>
            <category><![CDATA[laravel]]></category>
            <category><![CDATA[lumen]]></category>
            <category><![CDATA[migration]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Fri, 08 Jan 2021 09:14:52 GMT</pubDate>
            <atom:updated>2021-01-08T09:14:52.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S_x7QiQf2jJ2JO0C" /><figcaption>Photo by <a href="https://unsplash.com/@naletu?utm_source=medium&amp;utm_medium=referral">Natalya Letunova</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Lumen is a stripped down version of the powerful and now very popular Laravel PHP framework, focused on performance and serving stateless requests. I doesn’t have all the bells and whistles of Laravel, but it also doesn’t need them when serving API requests. For example, sessions, cookies and views are not a part of Lumen. It’s not intended for serving websites so everything around that got ditched.</p><p>This also is why we ditched Laravel Spark in 2018 and migrated to Lumen PHP, as I already mentioned in <a href="https://medium.com/once-upon-a-site/why-we-chose-laravel-spark-and-later-dropped-it-55552309d7bd?source=collection_home---------25----------------------------">a previous article</a>. Because Lumen PHP it a perfect candidate for building scalable and high-performance APIs.</p><p><strong>Until it doesn’t.</strong></p><p>After we migrated to Lumen PHP, we did get all the benefits from it. The API was completely separated from the client web app, the performance was amazing, and everything seemed fine.</p><p>The main wall that we hit were the libraries. Such as Laravel Horizon for Redis queue management, Laravel Passport for oAuth. We were able to use this with some hacks and third party packages that found ways to make the work with Lumen.</p><p>Then we needed Laravel Cashier, to integrate the payments processor.</p><p><strong>And that was the last straw.</strong></p><p>I realized that we were way behind on many packages, because there was no up-to-date hacks available. Especially when we tried to migrate to the latest Lumen 7.x, as we were on Lumen 5.6.</p><p>After a ton of research and listening to <a href="https://blog.laravel.com/laravel-snippet-14">a podcast</a> by <a href="https://medium.com/Taylor%20Otwell">Taylor Otwell</a> who said the bootstrap is about 5 ms, which is insignificant, we embarked on an adventure to migrate the API into a brand new Laravel application. Some people said that for a blank application, Lumen has a 20% boost over Laravel,, due to the routing library. They also said that this only applies to “Hello World” benchmarks, where most of the work is the actual routing, and that for real live applications, that percent is much lower. Anyway, my personal take on this is that for the 20% performance difference, it’s not worth wasting time with Lumen.</p><p>So, it was time to skip hacking ancient versions of Lumen and switch to Laravel for the core application. It has a lot of features that we need for development speed, and the (allegedly) 20% boost in performance is not worth wasting time with hacks, vulnerable and obsolete libraries, and our sanity.</p><p>The process of migrating went pretty smooth and it took about one full week.</p><p>Step 1 — was to create a new Laravel application.</p><p>Step 2 — was to copy all the tests from Lumen and update phpunit.xml to use the new folders in tests.</p><p>Then, run phpunit and see which is the first running and failing test, and run just that test.</p><p>Finally, make each test pass:</p><ul><li>change extends \TestCase to extends TestCase and add use Tests\TestCase; as Laravel&#39;s test are better namespaced.</li><li>change use DatabaseTransactions to use RefreshDatabase to refresh the migrations on each run.</li><li>add the migrations and model factories required for the data structures.</li><li>integrate the helpers.</li><li>run tests and fix whatever fails.</li></ul><p>After days of red test results, we were finally able to migrate all the code to the latest Laravel version.</p><p>From then on, we’re updating the packages every week, because the complete test suite allows us to confidently apply updates and ship the API to production.</p><p>I’m curious if you have undergone such a migration, as well as the challenges and benefits that came with it.</p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7ab2bcefff9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/why-we-ditched-lumen-php-b7ab2bcefff9">Why we ditched Lumen PHP</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Close to wrapping up 2020]]></title>
            <link>https://medium.com/once-upon-a-site/close-to-wrapping-up-2020-de0fe5a7d4c9?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/de0fe5a7d4c9</guid>
            <category><![CDATA[monitive]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[freyja]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Fri, 20 Nov 2020 10:51:15 GMT</pubDate>
            <atom:updated>2020-11-20T10:51:15.031Z</atom:updated>
            <content:encoded><![CDATA[<p>There are 6 weeks left of 2020, which means it’s about time we wrap this year up, focus on what’s most important, and leave the nice-to-have endeavors for next year. For Monitive, that means finalizing all the features that our users need to completely migrate from the (now old) Monitive Classic to the new and shiny Monitive.</p><p>We’re sunsetting Monitive Classic just before Christmas, so my number one goal is to ensure that every user only has downtime that they know about. As it is our duty, and many users rely on us for letting them know, we just cannot afford to let them down.</p><p>That’s why I crafted a list of what we’ll be focusing towards the end of 2020:</p><ul><li><strong>Bug fixing</strong> — this is always a priority, any bugs get squashed first.</li><li><strong>PING Monitoring</strong> — this one is ready and tested, will be released this weekend.</li><li><strong>TCP Port Monitoring </strong>— almost ready, still needs some testing and updates.</li><li><strong>PagerDuty Integration</strong> — our core business is not incident management and escalation, but PagerDuty’s is. And since we have customers that rely on it, we’ll migrate it to the new Monitive as well.</li><li><strong>HTTP POST Alerts</strong> — Allows users to configure their very own scripts which get called when an outage occurs. From alerting to restarting services, you can do pretty much anything with a HTTP POST Alert webhook.</li><li><strong>Multi-user Accounts</strong> — This is in development, and it allows multiple users to manage the same account (team), get notified of outages, get reports etc.</li><li><strong>Marketing Flow</strong> — For years we were lousy at communicated what we’re doing, how we’re doing it, and why. I’m looking forward to changing that.</li><li><strong>Lead Generation </strong>— “Making the Internet a better place — one site at a time” sounds great, but we also need to pay our rent, buy food and live. Which is only sustainable as long as customers find out about us.</li><li><strong>PDF Reports</strong> — this is must, requested by users and also will help Lead Generation, so it’s on our shortlist.</li><li><strong>Quick Tests </strong>— it seems many users are still searching for a way to do a quick-test for a website. This was available in the old Monitive Classic, and I’m looking forward to providing it in the new one.</li><li><strong>Promotion</strong> — Involves trying out various ad networks such as Google Ads, Twitter, Quora, LinkedIn, Facebook and others.</li><li><strong>Status Page </strong>— A single place that any customer’s visitor can quickly look up if there’s something going on with the website. Again, this was available in the old Monitive, and I’m looking into providing this in the new one.</li><li><strong>Sunsetting Monitive Classic</strong> — This involves accurate and complete communication, as this should not be a surprise for any of our users.</li></ul><p>This is pretty much it for this year. Due to the limited time, the new features might not have all the bells and whistles in the first iteration, but I’m very happy that the new Monitive is very stable, with a full test-suite and accurate reporting. More about this in the posts to come.</p><p><strong>And by the way, if you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de0fe5a7d4c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/close-to-wrapping-up-2020-de0fe5a7d4c9">Close to wrapping up 2020</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do you make your customers feel?]]></title>
            <link>https://medium.com/once-upon-a-site/how-do-you-make-your-customers-feel-dc8bbe0c4e70?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/dc8bbe0c4e70</guid>
            <category><![CDATA[feelings]]></category>
            <category><![CDATA[monitive]]></category>
            <category><![CDATA[together]]></category>
            <category><![CDATA[mindset]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Thu, 15 Oct 2020 13:21:11 GMT</pubDate>
            <atom:updated>2020-10-15T13:21:10.998Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ibJ_DsFpWVbMEuHBrt7hUg.jpeg" /><figcaption>Photo by <a href="https://medium.com/u/54f9e2cd93fa">Lucian Daniliuc</a> Model Elena P.</figcaption></figure><p>There are a lot of tools, apps and services. If you’ve been following Product Hunt, you already know that startups and new apps are being launched every single day. A startup these days is so common that even high-school kids are doing it. There are endless rivers of guides, books and knowhow on how to do it, and since most startups have some sort of product or service, there might be an app for pretty much anything you might think of. And if there isn’t, well, it’s a great moment to build it yourself.</p><p>However…</p><p>The general theory about building a tool is that it should service a specific need. This can be either a pain, or just the need for entertainment (ergo, games). I won’t dive into the gaming industry since I rarely play games (usually around Christmas, when it’s too cold do to anything outdoors).</p><p>But regarding a tool, there are plenty. And whatever you’re doing, you might be surprised that there are potentially multiple tools out there which can make your work easier.</p><h4>The end goal</h4><p>I had a nice chat with an old friend recently, and he made a point that sticked with me.</p><p>He said… “It’s not enough to provide a tool to a customer. You have to do as much as possible in solving his pain.”</p><p>That really made sense. For example, if the user wants his furniture assembled, it’s not enough to provide him with a screwdriver. The greatest thing you could do for him is help him assemble his furniture.</p><p>Nobody said “Hey, I have a friend who has screwdrivers, I can call him if you need one”, but people remember when you help them:</p><p>“I have a friend who helped my assemble by living room furniture, let me see if he’s available to help you out.” or even “Let me help you assemble your furniture.”</p><p>And all this happens because…</p><blockquote>People forget what you said, what you did, but they never forget how you made them feel.</blockquote><p>Even after years passed by, I still remember people that made me feel in certain way. I also remember people that made me feel miserable. So it can go both ways.</p><h4>Be memorable…</h4><p>It’s the little things that count, but we already knew that. We just got on about our life and while trying to go ahead of the game, we might have lost our way.</p><p>Just like a thousand years ago, when some neighbour in a village needed someone to help him fix his roof after a storm, he had nowhere to go but to his neighbour to help him out. And they did, because helping out your neighbour when he’s in pain was the only way to make a living.</p><p>As centuries passed and technology emerged, we now have plenty of “neighbours” and a lot of tools, but nothing beats good ol’ “help out a friend” or even “help out a stranger”.</p><p><strong>Stay humble!</strong></p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc8bbe0c4e70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/how-do-you-make-your-customers-feel-dc8bbe0c4e70">How do you make your customers feel?</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GitHub Action to Cloudflare Workers Sites]]></title>
            <link>https://medium.com/once-upon-a-site/github-action-to-cloudflare-workers-sites-7e1b5f8d212e?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e1b5f8d212e</guid>
            <category><![CDATA[freyja]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[cloudflare]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Thu, 08 Oct 2020 11:35:39 GMT</pubDate>
            <atom:updated>2020-10-08T11:36:20.037Z</atom:updated>
            <content:encoded><![CDATA[<h3>GitHub Actions to Cloudflare Workers Sites</h3><p>As time goes by, I’m looking for solutions that require as little maintenance as possible. One of those is deploying our <a href="https://app.monitive.com/">client web app</a> and <a href="https://monitive.com/">our homepage</a> directly on the CDN edge, with GitHub Actions.</p><p>Not only we don’t need a server to host the app, but the deployment script is also serverless and maintenance-less. This allows me to focus on important tasks, knowing that deployment and serving of the app is always blazing fast.</p><p><a href="https://workers.cloudflare.com/sites">Cloudflare Workers Sites</a> allows us to serve the app from Cloudflare’s network of CDN servers without any actual origin. The site is out there, in the cloud, being served faster than any regular website would be. It literally takes milliseconds for the site to load in your browser, wherever you are in the world. And that goes a long way for user experience.</p><p><a href="https://github.com/features/actions">GitHub Actions</a> enables us to build simple (or complicated) deployment flows, building the app and deploying it to the corresponding location.</p><p>As of the writing of this article, I don’t think there’s a faster delivery system than hosting your website directly on the CDN edge.</p><p>I won’t go into the details of how Cloudflare Workers Sites works, since there’s <a href="https://developers.cloudflare.com/workers/">a lot of documentation</a> for that, however here’s our wrangler.toml file, used by Cloudflare to deploy the website into “the cloud”:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cd9affa8f37603aa5aab4c3137622fa0/href">https://medium.com/media/cd9affa8f37603aa5aab4c3137622fa0/href</a></iframe><p>This is pretty much it. Publishing the app from the local command line is just a matter of running:</p><pre>$ wrangler publish --env staging</pre><p>Now, for the automation part, here comes GitHub Actions. Our development flow involves pushing to staging any merge into the master branch, and pushing to production any new release published. For this to work, we have two workflow files, release.yml and staging.yml, the main differences between these is when it’s run and deployment keys.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7680d49570b9ae62052e545a8664b37e/href">https://medium.com/media/7680d49570b9ae62052e545a8664b37e/href</a></iframe><p>As for the releases, we want those deployed only when a release is published, so the workflow file begins with:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b81bb1f9115ec7a18a8a9f36da55ec2c/href">https://medium.com/media/b81bb1f9115ec7a18a8a9f36da55ec2c/href</a></iframe><p>And that’s pretty much it. Now, whenever code is pushed to master, a PR to master is created or a new Release is published, GitHub actions builds the app and deploys it to the corresponding environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i83md7eGRobsPGLaQ-ouGA.png" /><figcaption>Our web app GitHub Actions</figcaption></figure><p>I hope you found this article useful.</p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/"><strong>Monitive.com</strong></a><strong> </strong>(also deployed by GitHub Actions &amp; Cloudflare Workers Sites).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e1b5f8d212e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/github-action-to-cloudflare-workers-sites-7e1b5f8d212e">GitHub Action to Cloudflare Workers Sites</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet the new Monitive]]></title>
            <link>https://medium.com/once-upon-a-site/launching-monitive-freyja-53adb09adabd?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/53adb09adabd</guid>
            <category><![CDATA[launch]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[freyja]]></category>
            <category><![CDATA[uptime-monitoring]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Thu, 18 Jun 2020 11:18:05 GMT</pubDate>
            <atom:updated>2020-10-21T08:42:37.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Ejn34Fi_Q7AfC31gRH_Pw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@gianviphotos?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Gianandrea Villa</a> on <a href="https://medium.com/collections/608426/spring-reset-?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The day has come. After 10 years of running an uptime monitoring service, of which three years we spent in rewriting of the service. The new Monitive codename “Freyja” is ready for the world to use.</p><h3>What is it?</h3><p><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=launch">Monitive</a> is an uptime monitoring service, which means it checks your websites and other online services every minute, from all around the world and instantly notifies you if they go down, for whatever reason.</p><p>It’s like a doorman to your online presence, watching the front door from the street and ensures that people can “go inside” and learn about you, buy something from you or use your services.</p><p>Big companies, who have an entire Ops department are still using Monitive just to get that “street view” assurance that it’s all good from the outside world, even though they have their own “doorman team” inside the building, making sure all the electrical, pipelines and other system are running smooth to best serve their visitors or customers.</p><h3>Why would you use it?</h3><p>Because <em>all</em> websites go down eventually. Big and small, popular or forgotten, the “nothing lasts forever” rule applies. Many of them are going down much more often than others. And if your website matters to you, keeping an eye on its uptime is critical, for a variety of reasons, as downtime:</p><ul><li>hurts your reputation</li><li>damages business</li><li>renders marketing efforts useless</li><li>negatively affects SEO</li></ul><p>And it also brings collateral damage, such as handling angry customers that couldn’t complete their task using your website, which you then need to make happy again.</p><h3>Introducing the new Monitive</h3><p>The new Monitive, codenamed “Freyja” is the foundation for years to come. It does one thing and it does it well: <strong>notifies you if you website goes down.</strong></p><p>We’ve been focusing on simplicity, so that you don’t need a User’s Manual, you don’t need an engineering degree to use it, it just works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xrQV8QpIbNwHT3cMyqbogA.png" /></figure><h4>Alerting rules</h4><p>By default, when your website goes down, you’ll instantly receive an email alert. If it’s still down for 3 minutes, you’ll get an SMS alert. And if it’s still down after 10 minutes, we’re calling you!</p><h4>À-la-carte features</h4><p>One thing that we did differently is that you only turn on features that you need. So there’s no overcrowding the interface with switches and options that you’ll never ever use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e024g-SQdLuKoFF98wl4yQ.png" /></figure><h3>Why not keep using the old one?</h3><p>The old Monitive is now called Monitive Classic and is still available at <a href="https://classic.monitive.com/">https://classic.monitive.com</a> and it will be up and working until <strong>Friday December 18th, 2020</strong> when we’re going to “pull the plug” and let it rest. That’s exactly six months from today’s launch date, plenty of time for our customers to migrate to the new Monitive.</p><h3>Thank you!</h3><p>As a conclusion, I want to send a big warm thank you to the thousands of users that have been using Monitive in the past. Each and every one of them helped us craft the Monitive that launched today.</p><p><strong>Please visit our new service homepage at </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=launch"><strong>monitive.com</strong></a><strong> and let us know what you think!</strong></p><p>We’re also on ProductHunt, please come by and take a look: <a href="https://www.producthunt.com/posts/monitive">https://www.producthunt.com/posts/monitive</a></p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53adb09adabd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/launching-monitive-freyja-53adb09adabd">Meet the new Monitive</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Launching the new Monitive]]></title>
            <link>https://medium.com/once-upon-a-site/launching-the-new-monitive-aae75a0f9b0c?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/aae75a0f9b0c</guid>
            <category><![CDATA[uptime]]></category>
            <category><![CDATA[uptime-monitoring]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[monitoring]]></category>
            <category><![CDATA[freyja]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Thu, 04 Jun 2020 10:59:19 GMT</pubDate>
            <atom:updated>2020-10-21T08:40:41.322Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hbhmR2MEYgS9EhqiUlbi1w.jpeg" /></figure><p>It’s been a long journey since I decided that the current version of Monitive is just not good enough for our customers.</p><p>That it doesn’t scale how it should.</p><p>That its interface isn’t responsive or suitable for mobile devices.</p><p>That the inner workings are not flexible enough to allow further extensions and features.</p><p>All this, because it was the very first usable iteration of Monitive, crafted around 2011.</p><p>That’s why on February 2017 I decided to start rewriting everything from scratch. The first git commit for the new Monitive was on March 7th, 2017. And thousands of code commits followed, none of which were yet public to our customers.</p><p>Until now…</p><h3>2020 Picnic Day</h3><p>On <strong>June 18th</strong>, the 25th Thursday of 2020, and the International Picnic Day, the <em>new</em> <strong>Monitive will be officially launched</strong>.</p><figure><img alt="New Monitive landing page screenshot" src="https://cdn-images-1.medium.com/max/1024/1*ppTf3xTW7yacVfQEipffXg.png" /><figcaption>New Monitive homepage to-be</figcaption></figure><p>It’s been a wild ride, with all kinds of challenges, excitement, some despair, but nevertheless, resilience to see it through and send it into the world.</p><p>It doesn’t have all the bells and whistles, as the main purpose was to lay the foundation for the next ten years.</p><p>I am honored to have loyal customers that are with us for more than 8 years, and I am not going to get in front of them with anything less than awesome.</p><p>The main reason that I started Monitive ten year ago is that there wasn’t an uptime monitoring solution that would provide both simplicity and freedom to the users.</p><p>And, while chasing customers and growth, even I got lost along the way.</p><p>Therefore, the main purpose of this new Monitive is to provide a service that’s blazing fast, easy to use for everyone and a stepping ground towards contributing to a better, brighter Internet — one site a time.</p><h3>But why?</h3><p>To be more specific, the main reasons for the rewriting from scratch are because the old system, even if very useful and working great, has some shortcomings:</p><ul><li>Even though it works great, and has been for 10 years, <strong>it doesn’t scale</strong> — if tomorrow 1000 users sign up, it’s going to all go down in flames.</li><li><strong>It’s fragile</strong> — meaning it has no automated unit tests behind it. Adding new features is very difficult, because something might break and all that decade-long trust can go in flames in a couple of hours.</li><li><strong>It’s old</strong> — some of the technologies and frameworks used to build it are now extinct. Meaning that even if we’d extend it as is, it would never be able to compete with newer services.</li></ul><p>And why it took 3 years?</p><ul><li>Because life always has its own plans,</li><li>Because I refused to compromise, and</li><li>Because there was no real urgency to ship it.</li></ul><h3>What should you expect?</h3><p>Expect simplicity.</p><p>Expect transparency.</p><p>Expect it to do one thing and do it good.</p><p>I am a man who tries to avoid expectations, because expectations include assumptions, and assumptions are usually wrong.</p><p>On the launch date, we’ll also announce the sunsetting date for the old system. We will not rush all the users to migrate to the new system, each user can switch whenever they are ready.</p><h3>“But… what’s in it for me?”</h3><p>You’ll want <em>in</em> on the new Monitive for three reasons:</p><ul><li><strong>Focus and peace of mind</strong><br>You can focus on what’s on your plate, whenever your site goes down we’ll send you a notification, but if it’s serious (down for 10 minutes) and you don’t react in any way, we’ll call you. <br>So no more checking your notifications every 5 minutes. <br>If it’s important, we’ll call.</li><li><strong>Simplicity is the ultimate sophistication</strong> (also know as à-la-carte features)<br>Turn on only the features you want, no cluttering, no complications, no extra buttons and settings. <br>Like picking lunch from the menu.</li><li><strong>Support the next generation uptime monitoring service </strong><br>If the last one we built is running for 10 years straight, executing 8 billion checks for over 4600 users, detecting 2,200,000+ outages, imagine what the next generation will do. <br><a href="https://new.monitive.com/?utm_source=medium&amp;utm_medium=ouas&amp;utm_campaign=pre_launch">Join us</a> in the new adventure.</li></ul><h3>What’s next?</h3><p>If you’re curious as to what’s this all about, I encourage you to head out to the <a href="https://new.monitive.com/?utm_source=medium&amp;utm_medium=ouas&amp;utm_campaign=pre_launch">new landing page</a> (which will become the main domain site on the launch date) and <strong>subscribe to get notified</strong>.</p><p>We’ll send out at most one newsletter every two weeks with tips and updates on the new system, including the one on the day we launch it.</p><p>Please <strong>let your friends or colleagues know about the upcoming launch</strong>, we’re going to gradually let people into the new system, so the people that subscribed for updates are going to have priority (based on their email address).</p><p>Since we focused on the product for the last period of time, it’s time we focus on traction. Getting it out there, helping people get a better uptime of their online presence and helping us focus 100% on the service provided.</p><p>In the meantime,<strong> check out </strong><a href="https://new.monitive.com/?utm_source=medium&amp;utm_medium=ouas&amp;utm_campaign=pre_launch"><strong>new.monitive.com</strong></a><strong> and subscribe to the newsletter</strong> to get notified about updates.</p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aae75a0f9b0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/launching-the-new-monitive-aae75a0f9b0c">Launching the new Monitive</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Slow and steady]]></title>
            <link>https://medium.com/once-upon-a-site/slow-and-steady-6f2162c032e9?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/6f2162c032e9</guid>
            <category><![CDATA[freyja]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Fri, 27 Mar 2020 15:42:55 GMT</pubDate>
            <atom:updated>2020-10-21T08:39:43.345Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Two women looking over the mountains" src="https://cdn-images-1.medium.com/max/1024/1*I9nPEedS7Mcbc63zssWs5A.jpeg" /></figure><blockquote>“Remember that guy that gave up? Neither does anybody else.”</blockquote><p>Progress on the new Monitive has been slow as a snail in a marathon, but nevertheless the progress was there. Since the last update last year, a lot has been going on, and one day I woke up and just decided to write, even if small updates. Not only because Monitive is about transparency, but because I love writing. I love putting myself out there with the good and the bad, I love writing articles that I’ll be embarrassed about in a few years. Because growth and progress is a significant part of life, and there’s no shame in hiding it.</p><p>The beta that’s already been running and checking sites is up and live for about a year, during which roughly 52 million checks were executed, plenty of alerts were sent, confirming that it’s a working product.</p><p>But it’s not the new Monitive, it’s merely an iteration of what you’ll see live in short while. The frontend web app was completely rewritten and reorganized (yes, again), we added new screens and also improved the internal monitoring engine.</p><p>And what’s more important, all this was possible because there was no pressure to launch the wrong product. No quarterly sales targets, no EBITA, and no profit margin. The rewriting process has officially been taking 3 years now, and I have no regrets for the long time that passed.</p><p>As the first, currently in production for roughly 10 years version of Monitive is still running smooth and helping customers keep a high uptime, the new generation of uptime monitoring service can take it’s time to ensure it will be there for another 10 good years.</p><p>The original version of Monitive ran close to 8 billion checks, crunching data, crafting reports and sending alerts. And it will still be around to see this year’s Christmas, because even after the official launch of the new Monitive codenamed “Freyja”, the old one, soon to be called “Monitive Classic” will be slowly phased out when there’s not a single customer using it.</p><p>Oh, and since I have photography as hobby, I decided to stop using stock photos for my stories and use photos I took instead.</p><p>Stay safe!</p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f2162c032e9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/slow-and-steady-6f2162c032e9">Slow and steady</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week #20 Freyja Updates]]></title>
            <link>https://medium.com/once-upon-a-site/week-20-freyja-updates-139dfe1b7413?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/139dfe1b7413</guid>
            <category><![CDATA[freyja]]></category>
            <category><![CDATA[vuetify]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Lucian Daniliuc]]></dc:creator>
            <pubDate>Fri, 17 May 2019 14:08:33 GMT</pubDate>
            <atom:updated>2020-10-21T08:38:56.437Z</atom:updated>
            <content:encoded><![CDATA[<h4>Monitoring engine, Braintree subscriptions and Vuetify</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y9uM6V24LWYRDFNbVi5gGQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/xNOueH62E4E?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">CHU TAI</a> on <a href="https://unsplash.com/search/photos/dirt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It’s been a while since the new Monitive codename “Freyja” was launched in private beta, and even though a lot of things have happened, development is moving forward a bit slow than I’ve hoped.</p><p>Nevertheless, I’m happy that the core monitoring engine is running smoothly and it’s a great foundation for the years to come.</p><p>I’ve decided to write a short post each week about our progress, so this would be the first one. Week 20 refers to this year’s week number, as I use it personally each week when I’m doing all my planning.</p><p>Long story short (remember I mentioned it will be short?), the biggest things are these:</p><p><strong>First</strong> and foremost, the monitoring engine is great. It’s a custom Go + InfluxDB + Lumen PHP monitoring engine that seems to be working in harmony. I still want to run another load test to see where it breaks, but it should be good to monitor thousands of sites every minute.</p><p><strong>Second</strong>, we’ve started implementing the subscriptions component of the web app, as it’s a key component allowing us to publicly launch it. We’ll integrate with Braintree for recurring payments, and hopefully it will be the simplest subscription system for a monitoring service there is. I’m aiming at having a pay-as-you-go system, based on the number of monitors, with everything included. Meaning no Bronze, Platinum, Gold, Pro, Silver, Premium stuff. It’s one plan. But this project got a bit hijacked, because…</p><p>Our frontend UI library we were relying on, <a href="https://github.com/stasson/vue-mdc-adapter">vue-mdc-adapter</a>, is now dead. Deprecated. Yes, I made a poor choice of fronted UI framework, I know. Therefore, we have to migrate it to another one. And I chose <a href="https://vuetifyjs.com/">Vuetify</a>, which is great and has a big community behind it, but we’re right in the middle of the migration process, so this sets us back a bit.</p><p>This is a lesson in spending time polishing the design on an app before launch. So, never again. No more spending time polishing a beta product, unless it launches immediately.</p><p>That it’s for this week’s updates, have a great weekend! 🍺</p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=139dfe1b7413" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/week-20-freyja-updates-139dfe1b7413">Week #20 Freyja Updates</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beta Testing For Dummies]]></title>
            <link>https://medium.com/once-upon-a-site/beta-testing-for-dummies-f5fd1b8b0acf?source=rss----1a1fe0429be0---4</link>
            <guid isPermaLink="false">https://medium.com/p/f5fd1b8b0acf</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[testing]]></category>
            <category><![CDATA[beta]]></category>
            <category><![CDATA[beta-testing]]></category>
            <category><![CDATA[freyja]]></category>
            <dc:creator><![CDATA[Lauren Senger (Detweiler)]]></dc:creator>
            <pubDate>Mon, 08 Apr 2019 13:58:36 GMT</pubDate>
            <atom:updated>2020-10-21T08:38:19.427Z</atom:updated>
            <content:encoded><![CDATA[<h4>Written by a self-proclaimed beta testing dummy.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T7PwnCt8WqkguHJR_-Bg2Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/PTdZzOcTEA8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Aykut Kaya</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Don’t worry, this isn’t an article where someone extremely adept at software testing and well-versed in industry terms is going to talk down to you.</p><p>I’m a marketer first and a writer second, and no part of my career has ever involved the nitty gritty parts of building out a tech product or service to prepare it for real-life users.</p><p>So if you’re completely clueless in this area, don’t worry — I’m right there with you.</p><p>That being said, I’ve had to jump into the deep end and start learning all about beta testing in recent months as our team at Monitive prepared to roll out our completely rewritten (not by me!) uptime monitoring service.</p><p>While the original Monitive has been around for over nine years, changing demands from users and other transformations across the industry prompted our CEO, <a href="https://medium.com/u/54f9e2cd93fa">Lucian Daniliuc</a>, to start from scratch to create something fresh and crazy simple. (You can read an interview I did with him for <a href="http://opsmatters.com/">OpsMatters.com</a> <a href="https://medium.com/opsmatters/the-evolution-of-the-monitoring-industry-and-why-customers-should-run-the-show-our-interview-with-8b906c0b0bfb">here</a>!)</p><p>What comes next after a new product is built? <strong>Beta testing.</strong> For me, this phase meant figuring out what beta testing actually is and how I could be a part of making it successful.</p><p>Here’s what I’ve learned:</p><h3>It’s extremely important.</h3><p><a href="https://www.360logica.com/blog/types-of-software-testing-for-dummies/">Software testing</a> in general is “a process of verifying product needs and validating specified requirements.” There are many different types of testing, but they all come down to checking the quality of the product and providing information about the product under testing.</p><p>For many products and services, the most important thing is to actually see how a product does when it’s used (tested) by real people. There are other types of testing that go down before the product is ever seen by a user (for instance, <a href="https://www.guru99.com/alpha-testing.html">Alpha testing</a>), but <strong>beta testing</strong> is when the product is tried by the client side. They then provide feedback before the system is “finalized” (is the work ever really done?) and rolled out to other customers.</p><h3>Feedback is invaluable for the development team.</h3><p>Without user feedback from beta testers, the creators of whatever product or service is being tested would be entering the market completely blind to the thoughts of consumers.</p><p><em>They would have no idea how users would respond to the product.</em></p><p><em>They wouldn’t have caught any bugs on the user side.</em></p><p><em>They wouldn’t even know if the product was commercially viable.</em></p><p>Feedback across the board — from additional desired features to broken links to “How much would you pay for this?” — is absolutely essential for teams to create the best possible product before their official launch.</p><h3>There are many ways to find beta testers.</h3><p>It’s one thing to set up a beta test and feedback channels, but then it’s time to build a pool of beta testers. While this can seem like a daunting task — especially if your team is shooting for high numbers — there are many different places to look for testers.</p><p>I’ll use Monitive as an example, as we’ve seen received signups from all of these channels.</p><h4>Old users</h4><p>If your product is a rewrite like Monitive, or an off-shoot of an existing product, you can invite your old/current users to become beta testers for the new product.</p><h4>Other contacts</h4><p>Work that network! Odds are that people on your team 1) have worked in industries full of potential beta testers in the past, 2) know of other techies or non-techies who could be interested, or 3) have friends.</p><p>Okay, I kid. But seriously, ask your friends!</p><p>Various members of the team invited their colleagues, friends, and even family members to be beta testers. As long as you trust them to be impartial and give legitimate feedback, go for it.</p><h4>Beta listings</h4><p>This is a big part of the world I didn’t know existed. There are <em>tons</em> of websites solely devoted to helping companies list their new products and find beta testers — and people often sign up just for fun! Who knew!</p><p>In the case of Monitive, we chose to list our test on <a href="https://www.betafy.co/startup/monitive-1">Betafy</a> and <a href="https://www.betabound.com/monitive-private-beta/">Betabound</a>, and submitted to a few others that we’re waiting to hear back from. I would advise doing your research to see which sites are the best fit for your specific needs, and then consider whether you’re willing to pay for the more premium platforms.</p><h4>Social media</h4><p>If you have any sort of following on social media, this can be another great way to find testers who may not have been on any of your mailing lists. You can even promote your posts to try and get in front of people who don’t follow you yet.</p><p>A few tips: Post more than once in case some people miss the first one, include a link to the landing page for your beta test and any incentives you’re offering (if applicable), and make separate posts for any links to beta listing sites you get featured on.</p><h3>If you build it, they will come.</h3><p>I’ve been pleasantly surprised at how many testers we’ve had sign up simply because they’re interested in the product and like being a part of the pre-launch phase. Sure, some have joined because they’re excited about the incentives — one free year of the new Monitive for each tester and Amazon gift cards for the top feedback-givers, in case you were wondering! — but quite a few <strong>just enjoy being beta testers</strong>.</p><p>It’s a cool community of like-minded people (with widely varied mindsets and feedback to offer) that I didn’t even know existed pre-Monitive.</p><p>Great news: we are still looking for more testers to join our private beta! If you’re interested in joining our <em>super fun </em>beta club, please apply <a href="https://new.monitive.com/">here</a>. We can’t wait to hear what you think about the new Monitive.</p><p><strong>If you’re looking for a simple solution to detect downtime before your customers do, check out </strong><a href="https://monitive.com/?utm_source=medium&amp;utm_medium=post&amp;utm_campaign=blog&amp;utm_content=footnote"><strong>Monitive.com</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5fd1b8b0acf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/once-upon-a-site/beta-testing-for-dummies-f5fd1b8b0acf">Beta Testing For Dummies</a> was originally published in <a href="https://medium.com/once-upon-a-site">Monitive — Once Upon A Site</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>