How did I set up blog.sh on my shared hosting
pavelchcepsat.cz
Pavel přestěhoval WordPressový blog ze sdíleného hostingu na blog.sh, a to přes obyčejné FTP. Postup popisuje krok za krokem: export WXR, import, rclone, zkušební běh, nasazení.
Stojí za přečtení, pokud tvůj web běží na hostingu, který nabízí FTP a nic víc.
#blogsh #wordpress #staticsite
./blog.sh 1.7 is out. The page that writes a post on a phone now publishes it too, and it finds out what happened rather than being told: it mints a receipt before sending and asks the site for it every three seconds until the answer comes.
Beside it, the other half of the same idea — changing what a post is without opening what it says: its series, its tags, its type and three flags, from a screen. Then a link card written in the front matter, about fifty drawings a tag can wear, a video repacked on the way in so the reader does not wait for the whole file, and seventeen fixes.
#blogsh #ruby #staticsite
./blog.sh 1.6 is out.
The build stopped rebuilding what nobody changed: a rebuild that changes nothing costs a seventh of what it did, an ordinary publish about two fifths. A post can be handed over as a file — by a script, a cron job, or the new page at /write/ on the blog itself, which sends from a phone over the SSH the server already has. Nothing new listens on the network.
Around those: a row of share controls under a post, an icon a tag can carry, a way out of the trash and the versions, and a photograph stored once instead of twice.
#blogsh #ruby #staticsite
./blog.sh 1.3 is out.
Dressing a site no longer means editing the engine: your own stylesheet, menu, sidebar and lead images are settings now. Posts group into series, pages step out of the stream, and every edit keeps the version before it.
And three commands that read the whole archive: check reports what's broken, stats counts what's there, and export packs it all into Jekyll's layout. The way out ships with it.
#blogsh #ruby #staticsite
./blog.sh 1.2.1 is out.
A phone records where you were standing in every photo it takes. Social networks strip that on upload; a static site has nobody to do it. Now the engine does, on the way into the archive — and the doctor will clean the ones you saved before.
The bio, the footer, and the banner's claim are now Markdown. They were the only texts on a Markdown blog that had to be HTML.
./blog.sh 1.2 is out — the import release.
Eight import sources became twenty-two: every social network you are likely to have posted to, the blog platforms, and the Wayback Machine for blogs whose platform no longer exists.
Setting a site up is a conversation now. So is how it looks, with the candidate palette rendered on your own site before you keep it.
And a screen for walking an archive that got too big to scroll.
./blog.sh 1.1 is out.
Pin a post to the top. Schedule into publishing slots that queue instead of colliding. Attach files as download cards. Rename a slug without breaking a link — the old URL redirects forever. One dialogue for everything you can do to a post.
And deploy guards that measure the build against the build, so a failed upload can't quietly switch them off.
./blog.sh 1.0.1 is out — eighteen fixes, none of them reported by a user.
They came out of an independent verification pass over the release: a failed write could leave a post without a file, one bad post could stop the whole build, a missing media file could delete the copy that was already live.
There's now a CHANGELOG a clone can read, and ./blog.sh version tells you what you're running.
./blog.sh 1.0 is out.
A blog engine that's a folder and a shell script. Ruby stdlib and bash — no database, no gems, no admin. Comments live on the Fediverse. Eight importers, so your Tumblr and Twitter archives have somewhere to go. MIT licensed.
The site you're reading is the engine running itself.
The one way to contribute to ./blog.sh without writing a line of Ruby is to translate it — and it's a single YAML file.
Everything the reader sees — navigation, dates, archive headings, the search box, the comments prompt — comes from a locale file. The whole guide lives here:
docs/localization.md — adding a language to ./blog.sh
Three things make it genuinely easy:
en.yml, rename it, translate values. No templates touched, no Ruby read.en.yml must be complete. Yours can grow at whatever pace your weekends allow.English, Czech and German are already in. Yours would make four.