#Textastic working copy mac#

Here are some third-party guides that have been written up to assist: Most mobile apps do not have git support. This just received experimental Dendron support so worth trying out. Some popular options are listed below, based on feedback in the Dendron community: There are numerous mobile Markdown editors that can be used to view and edit Dendron notes. For a more in-depth comparison of text editors focusing on iOS devices, also take a look at this iOS Text Editor roundup by Brett Terpstra.ĭendron does not have a dedicated mobile client at this time. I plan on looking into the URL scheme in more detail soon, as I’d like to have a workflow that takes a blog post, creates the necessary text file, then commits and pushes the changes.A comparison of mobile apps for Markdown can be found on the Dendron blog: Best Mobile Note-Taking Apps for Markdown. The URL scheme is extremely powerful and not only can new files be created or edited, but commits and push actions can be performed as well. Push the changes to live (my server) so the site is then automatically updated using a Git Hook.įinally, Working Copy has a comprehensive URL scheme and supports x-callback-url, making it possible to create powerful workflows and actions with apps like Workflow and Drafts.

Commit and push the changes back to origin.

Make any necessary changes, such as adding a new blog post or editing the site’s layout.

Fetch and pull any changes from the remote origin repository (GitHub).

On the server, a Git Hook 4 listens for any changes that are received, which happens when a push has been completed to the live remote, and runs script that updates the files in /var/Thanks to Working Copy and automatic deployment, whether I’m on my iPad, iPhone or Mac, I perform the same steps to make changes to my website and deploy them: In a nutshell, I’ve configured a remote repository located on my server as a secondary remote for within Working Copy, and on my Mac, named live. To set this up, I followed Digital Ocean’s guide on setting up automatic deployment with Git. This has eliminated my need for Dropbox syncing and even publishing site changes via SFTP from my Mac, replacing them both with a process that pushes changes to a secondary remote repository – my server.

Since Working Copy supports many of Git’s standard features, I’ve been able to take advantage of another common use for Git – automatic website deployment. Once I’m done, I commit and push the changes back to the default remote origin repository on GitHub. Just like on my Mac, I’ve cloned my site’s repository (named, unimaginatively, ) from GitHub to make whatever changes or additions I want (either a new blog post or a tweak to the source code), locally. Working Copy is a fully featured Git client that brings with it a range of supported Git features and makes use of some great features of iOS that are often overlooked, such as Document Provider 3.

#Textastic working copy mac#

But thanks to the iOS Git client Working Copy, however, I’ve been able to use Git on my iPad and iPhone in the same way I would on my Mac and even deploy those changes to my server. I’ve never been fully happy with this workflow, despite it working successfully, because it doesn’t easily fit in with how I develop and version control the site’s source code, and content 2, with Git. As soon as I finished a new post, I’d remove the draft tag and it would appear on the site. This has been especially useful in the past twelve months as the iPad became my primary computing device, so I was able to use any Dropbox-enabled iOS writing app, such as 1Writer, to write and publish blog posts. Instead of the site’s content being stored in a database, Kirby uses Markdown-formatted plain text files, so publishing a new blog post is as simple as adding a new text file to the content directory, after which it’s immediately available on the site.įor a few years now, I’ve had Dropbox running on my server to sync the site’s content directory so that I can easily publish or edit content on any device 1 without needing to directly upload any files to the server.

This website is powered by Kirby, a file-based CMS, running on a VPS with Digital Ocean.