4 ms·

Write on your phone, commit to git, have some CI build it and deploy. Simples :)

• jedberg 6y ago
  > Write on your phone, Ok that part's easy. > commit to git How? I've never seen a good git client for the phone > have some CI build it and deploy. Step one, draw a circle. Step two, draw the rest of the owl. :) While this might be a fun exercise, it's more involved than deploying some code to Lambda.
  • darkteflon 6y ago
    Fwiw, Working Copy on iOS is a good git client.
  • mbreese 6y ago
    I don’t know... I have a Github actions workflow that on a commit, it builds a site (mkdocs) and upload it to a gh-pages branch for hosting on Github. You could also push the generated html to S3. That coupled with Working Copy could be a pretty good mobile workflow. For me, this was much easier than deploying Lambda code and managing How all of that worked together. Using Github Actions wasn’t much more than setting up a deploy script.
• asiachick 6y ago
  Have that. It sucks. UI on github sucks (need something I can access anywhere, not just my desktop, thought github might cut it, it doesn't). Uploading images sucks. No preview sucks. I suppose I could trigger to staging but that means I have to commit just to see a preview then wait for the entire process vs say wordpress which has instant preview. Managing posts also sucks. I can pre-date posts but I can't at a glance get a list of posts with data about each one. Instead I just get a file listing and have to open each file and read its headers to see its metadata (date, title). Publish vs unpublished also suck. I have folders for my posts and another folder for drafts but moving something from one to the other is no fun compared to just checking a box in wordpress.