Extracted for the benefit of non-Tightenites.
Class "things" should be ordered as follows:
- Statics properties
- Instance properties
So, you might be asking yourself, what is GistLog?
GistLog is a blogging "platform" for people who want to quickly write and publish content, in Markdown, and don't want to bother with yet another platform and yet another login and yet another group hoarding their content. With GistLog, you use your pre-existing GitHub login, you store the data in your own GitHub account, and you can publish with a single click.
I was hoping to sell my Blue Yeti & shock mount, and maybe throw a little bit more money at it, which means I'm definitely looking at under $200. Trying to find the best fit for a sub-$200 podcasting mic, XLR-based. I would love any new recommendations or votes for against any of these mics. Thanks!
MXL V67G - $88.95 - Amazon
Shure SM58 -
It's great that Gistlog makes it easy to write Gist-powered, Markdown-formatted, blog posts. But what if you want to use it as your entire blogging platform? We're working on it, and here's a first step: user landing pages.
Any Github user that has any public gists that contain a file named
gistlog.yml now have a landing page on Gistlog at
http://gistlog.co/your-user-name. So, since I have (more than) one, you can view my landing page at gistlog.co/mattstauffer. It's very simple right now, but we have a ton of ideas to improve it over time. So go check it out.
How do you get your own Gistlog landing page?
blog.mdfor the name) and one for the Gistlog settings (which must be named
gistlog.ymlyet, just create it with the fol
Note: This expects that you've enabled Xdebug in a specific file:
Add this function to your
.zshrc or similar file.
On the command line, type
xdebug and hit enter. This will toggle whether or not Xdebug is running.
Note: Most of these are applicable to the ages older than I have listed, but I've put them where they were when my kids first started really enjoying them.
Really, anything in the "toddlers" section will be fine for these kids. But there aren't a ton of baby-focused books I know.
(just a test, this is written by @rtablada not me)
After working with a lot of node modules I'm a bit angered by the fact that for a lot of these packages you have to pass around and keep track of a single shared instance throughout your application.
This works fine for small proxy servers and apps where the whole thing fits into a single
app.js or maybe a handful of route files.
But as things start to grow this model really breaks down and becomes cumbersome.
Just think about a resource file for
app/resources/users.js which needs the current Redis or RabbitMQ connection to publish events like user registration, a database connection to persist things, and probably a Socket.io instance because it's Real Time: it's so hot right now!
If you export a function that allows these to be injected, your resource has boilerplate.
I checked with Jason & Jack at Statamic, and they told me three things:
.envfile effects the behavior of its Laravel core, you can change the cache driver that your Statamic app is using just like you would in any Laravel app. Just add a
.envfile and set it to any of the options:
'file', the default;