#TEXTASTIC WITH GIT MAC#

I chose to simply copy & paste content from Textastic to Ulysses and publish as usual, using Nova on the Mac. At the time I was ready to publish, I found out that the git push feature of Working Copy is only available to paying users. This post wasn’t published from the iPad, after all. My mobile needs are quite low as the pandemic continues and limit our travel possibilities. I’m still undecided about what to do to enable my iPad for editing this blog. I didn’t find a way to do this with the official GitHub client. Blot, on which Numeric Citizen I/O is hosted, uses its Git server, which requires me to use a Git client capable of connecting to it. One last thing, Working Copy wouldn’t be needed if my Git usage was limited to GitHub.

#TEXTASTIC WITH GIT MAC#

Having to sit in front of the Mac for final posting isn’t a big deal. It’s not a big deal, Numeric Citizen I/O is not a place where I’ll publish as often as on, say, Micro.blog. Maybe I should focus on using Ulysses everywhere for my writing needs, and use the Mac for pushing content on my Blot blog. If I don’t redo my setup on the iPad 5, compared to using Nova on the Mac, I find this to be much less intuitive. In that case, I would use Ulysses to edit files as usual and Working Copy you see them as uncommitted changes. After re-reading their review of Working Copy 3, I found out that, in fact, I could have replicated a similar setup to the one on my Mac: using Working Copy to edit the local repo of this blog sitting on iCloud Drive (instead of Working Copy’s sandbox) 4.

Working Copy can work in conjonction with Textastic. Sounds overkill for me, since I’m alone editing my website. MacStories likes it because it enables better group collaboration. Read this excellent review from MacStories instead. Make no mistake, this isn’t a review of Working Copy. Textastic on the left, Working Copy on the right The former is more directed to developers while the latter are for writers. Textastic is good but not as a writing application like Ulysses. I need to remember that after pushing this article on Blot, I’ll have to do a fetch when I go back editing on the Mac. It is geeky because I have to think about what I’m doing in regard to my local repo being up to date with the remote one. Writing with Textastic and publishing with Working Copy feels geeky compared to a workflow based solely on Ulysses. Only Textastic can edit files with Working Copy sandbox. Ulysses uses external folders, so I can point it to my iCloud Drive where I stored the cloned repo with Nova.

When cloning the Blot repo locally, files were placed in the application’s sandbox, which is not accessible outside the iPad 2. The file was initially created within Working Copy’s sandbox, but I made sure to fetch content from the Blot Git repo first, to have the most recent changes locally stored on my iPad.Īs every app on the iPad, Working Copy runs within its sandbox. I started writing this post using my iPad, Working Copy and Textastic 1. 07:00 Using the iPad for Editing Blot Posts With a Git Client

Textastic with git