Categories
Finance Samuel

Thanking Triple M

This post is about saying thanks to Pete. I wanted to float the idea of doing something on a recurring basis to thank Pete for creating his website. I love the concept that “we are the sum of the 5 people we spend the most time around”. By writing his blog Pete has allowed us to be around him virtually and soak up so many amazing, life altering principals. For that I’m extremely grateful to Pete. Trying to think of the best way to say thanks I’m reminded of another great quote “give me a big enough lever and I can move the world”. With that in mind it seems like the best gift we could give Pete is the power to amplify the leverage of his website. I’d love if other people would weigh in with hopefully bigger and better ideas but my brainstorm on this has surfaced the following idea:

The best way to increase the visibility and usefulness of the MMM site is to improve the forum. The forum scales, whereas Pete is one human, the forum is a collective of people and ideas, capable of generating amazing content at scale. If the forum was able to automatically bubble up the best content, and display it to users this would maximize the usefulness of the MMM site. Due to the nature of the current forum with repeat posts and hard to navigate threads we end up with a never ending train of advice for each subject which is not as beneficial as the best advice bubbled up to the surface by a voting algorithm (think stack overflow but for the FI world). If we could take all the content currently on the forum and put it inside of a stack overflow type system where the best answers are eventually bubbled to the top via user ratings, then the forum would potentially benefit countless more people, and Pete’s secrete mission would be 1 step closer to fruition https://www.mrmoneymustache.com/2013/02/16/weekend-edition-why-are-you-writing-this-blog-anyway/

Categories
Samuel Voluntary Discomfort

4th Voluntary Discomfort

For this months discomfort Ellen and I have decided on a “low information diet”. This is slightly different for both of us. For me this will mean that I can’t read any news websites, and I can’t check on any stock market investments for 30 days. For Ellen this will mean she is going to delete her Facebook/Instagram and Twitter accounts. Since I technically don’t have any of these accounts I felt like it was too easy for me to simply say that I wouldn’t do any social media haha

I’m really excited about this challenge because its one that I have been wanting to try for a long time. I’ve also been really excited about Ellen trying this out because I really believe that I’m much happier since I quit all social media ~2 years ago, so I’m really interested to see if she gains any of the same benefits that I feel during this 30 day hiatus.

Categories
Samuel Voluntary Discomfort

3rd Voluntary Discomfort of 2018

For this months voluntary discomfort we are going to be exercising every day. I’ll post the results of the monthly here once we complete:

Ellen:
Sam:

Categories
Fixing Stuff Samuel

Creating Google Group For Server Notifications

This covers setting up a Google Group:

1.) Login to Google Apps Console and hit More Controls > Groups

2.) Hit the create new button (currently a yellow + icon in the lower right of the screen)

3.) Create the group using the onscreen tutorial

4.) click on the newly created group name and then click role and permissions

5.) Select Custom with the options “anyone” can send email to the group and owners can view member list

Categories
Fixing Stuff Laravel Samuel

Class PDO Not Found Laravel 5.6

When trying to deploy a commit on a Laravel 5.6 install we ran into the following error:

Class PDO not Found

In our particular case this is on a brand new site that was recently setup. This is only the second commit for the whole project. To fix this issue we ran through the following steps:

1.) Update composer (to do so we needed to to allow f_open)

2.) Delete the current vendor directory (please note this current vendor directory had been previously installed with f_open disabled and it appears to have caused some vendor files to load incorrectly)

3.) Run Composer Install

4.) Enable PDO (https://github.com/snipe/snipe-it/issues/1210)

5.) Run php artisan migrate

6.) Run php artisan db:seed

7.) Fire up our APP and enjoy no errors 🙂

Categories
Fixing Stuff Laravel Samuel

Updating Composer

We ran into an issue today trying to run composer update. The following error message was displayed:

[Composer\Downloader\TransportException]
The "https://packagist.org/packages.json" file could not be downloaded: allow_url_fopen must be enabled in php.ini (https:// wrapper is disabled in the server configuration by allow_url_fopen=0
failed to open stream: no suitable wrapper could be found)

TO fix this we completed the following steps:

1.) Opening WHM > MultiPHP INI Editor

2.) Select the version of PHP that is active for our specific account (you can look at MultiPHP manager to find your active version of PHP for each account)

3.) Find allow_url_fopen and set it to enabled.

4.) Run composer update again, once it completes turn allow_url_fopen back to disabled as its a security risk to leave this enabled long term.