Author: Tom (Page 123 of 427)

Sharing Visual Studio Code Settings in Dropbox

February 15, 2017 / Tom

Yesterday, I walked through the process of sharing databases in Dropbox so it makes sense to follow that up with how to go about sharing Visual Studio Code settings in Dropbox.

That is if you use Visual Studio Code (and I’ve had some people ask Twitter how to do this).

Sharing Visual Studio Code Settings: The Editor

As the same is in the previous post, the same disclaimer that I work on macOS. So this dictates the commands I use, how I create symbolic links, and how I go about sharing settings among machines.

Since this is following up a similar post, why not jump right in?

Sharing Databases in Dropbox (For MAMP Pro)

February 14, 2017 / Tom

Sharing databases is something that’s convenient to do within your local development environment especially if you’re working with multiple machines.

If for whatever reason you’re looking to do this with a staging environment or production environment, then this is not the way to do it. There are strategies like database replication and the like that are meant for that, and that are far beyond the scope of this post.

Instead, this is primarily intended for systems that you have, likely on the same network, and that you swap between during the day.

What Am I Doing to Move Forward?

February 13, 2017 / Tom

“What am I doing to move forward?” This question has been rattling around my mind since the beginning of this year. And much of it has to do with the amount of change and tension that I’m feeling for some things going on various things happening in a professional capacity (versus a personal capacity 🙂).

There are some [good] changes that have happened to Pressware. All the while, I’m doing what I can to make sure I’m investing not only in myself but the business, as well.

Move Forward: Working on Building Blogging Plugins

Still working on continuing to build a marketplace of plugins specifically for bloggers.

Of course, nothing I’m going to say is unique to web development, technology, or a software business in general.

This just happens to be the industry I know.

Here’s the challenge, though: There are more than a handful of things on which we can focus. But if we pick too many things on which to focus, it’s hard to really focus on anything to the degree that’s going to have any meaningful benefit.

That’s not revolutionary. It’s common sense, right?

WordPress Batch Processing with Locomotive

February 10, 2017 / Tom

WordPress batch processing doesn’t exactly sound like the most exciting aspect of programming (regardless of the platform, really). And working with large sets of data in WordPress usually comes down to one of two solutions:

using WP-CLI,
performing migrations with WP Migrate DB Pro.

Both of these solutions are great, and they do their job well; however, there are times when you’re working with large sets of data within the WordPress administration area that could be manipulated with a simple batch process.

This isn’t to say that using the command-line is bad, but sometimes toggling a few options to work with posts, comments, or other data types would be nice.

And that’s what Locomotive from Reaktiv Studios allow us to do.

WordPress Metadata Association: Relating Entities

February 9, 2017 / Tom / 0 Comments

At this point, we’ve covered how to create the entities within the plugin (which, as we’ve said, is just a fancy word for another concrete idea). Namely, we’ve got a user and a custom post type, or a book. And here’s where we start to take the two separate entities and combine and work with what we’ll call WordPress metadata association.

But before doing so, it’s important to understand the two types of metadata with which we’ll be working and the two ways (or three ways, depending on how you look at it) in how we can associate the metadata.

As with the rest of the posts in the series, this isn’t meant to be a deep-dive into understanding each of the tables or a deep-dive into each of API functions. Instead, we’re going to survey what’s available, put them to use, and leave finer details for future posts (or perhaps discussions in the comments).