From 1fd5b345eca01e9f76bf3ee3c3f04aada2c13bf8 Mon Sep 17 00:00:00 2001 From: ditatompel Date: Wed, 10 Apr 2024 19:29:54 +0700 Subject: [PATCH] Remove my asciinema instance link and script My self-hosted asciinema is sunsetting. So I remove all videos and js link to my asciinema server. --- .../index.id.md | 8 ++------ .../install-mastodon-without-docker-ubuntu-20-04/index.md | 6 +----- .../index.id.md | 4 ++-- .../index.md | 4 ++-- 4 files changed, 7 insertions(+), 15 deletions(-) diff --git a/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.id.md b/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.id.md index 9186fd3..95f3d0a 100644 --- a/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.id.md +++ b/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.id.md @@ -44,14 +44,10 @@ Artikel ini membahas mengenai cara menginstal Mastodon di Ubuntu 20.04 beserta d Catatan: saya menggunakan *self-signed* SSL *certificate* karena *instance* yang akan saya jalankan akan berada dibalik **Cloudflare** *reverse proxy*. -Video **asciinema** saat proses installasi dan konfigurasi Mastodon dapat dilihat dibawah ini: +Video saat proses installasi dan konfigurasi Mastodon dapat dilihat dibawah ini: - - -Atau full YouTube Video: {{< youtube eBUr7JFiGMo >}} - ## Pre-requisites Sebelum memulai, ada beberapa syarat yang harus dipenuhi untuk dapat menjalankan Mastodon, yaitu: @@ -243,4 +239,4 @@ systemctl enable --now mastodon-web mastodon-sidekiq mastodon-streaming Tunggu beberapa menit dan coba akses Mastodon dari web broser dan selamat menikmati! ## Resources -* [https://docs.joinmastodon.org/admin/install/](https://docs.joinmastodon.org/admin/install/) \ No newline at end of file +* [https://docs.joinmastodon.org/admin/install/](https://docs.joinmastodon.org/admin/install/) diff --git a/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.md b/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.md index 24eb4da..84456c6 100644 --- a/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.md +++ b/content/tutorials/install-mastodon-without-docker-ubuntu-20-04/index.md @@ -41,11 +41,7 @@ authors: This article is my personal snippet for running Mastodon instance on Ubuntu 20.04 from source. I use *self-signed* certificate instead of **cerbot** because the instance will be run behind **Cloudflare** reverse proxy. -The **asciinema** video below is the whole process I install Mastodon instance (for reference) - - - -Or the whole YouTube video: +The video below is the whole process I install Mastodon instance (for reference) {{< youtube eBUr7JFiGMo >}} diff --git a/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.id.md b/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.id.md index acc237e..3bb6b29 100644 --- a/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.id.md +++ b/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.id.md @@ -34,7 +34,7 @@ authors: - ditatompel --- -Hari ini, saya menemui kendala saat melakukan upgrade [self-hosted asciinema-server](https://asciinema.ditatompel.com/) milik saya. Setelah [mengikuti proses upgrade sesuai dokumentasi asciinema-server di GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide#upgrading), *container* `phoenix` dan `postgres` gagal berjalan dan selalu restart. +Hari ini, saya menemui kendala saat melakukan upgrade _self-hosted_ **asciinema server** milik saya. Setelah [mengikuti proses upgrade sesuai dokumentasi asciinema-server di GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide#upgrading), *container* `phoenix` dan `postgres` gagal berjalan dan selalu restart. @@ -147,4 +147,4 @@ docker exec -it psql -d postgres -U postgres -f /var/lib/p > **Catatan**: `DOCKER_CONTAINER_ID` Anda akan berbeda dengan `DOCKER_CONTAINER_ID` yang sebelumnya. Pastikan gunakan *docker container ID* yang benar. ### Jalankan asciinema-server seperti biasa -Setelah itu, jalankan semua service asciinema-server seperti biasa dengan menjalankan perintah `docker-compose up -d`. Seharusnya Anda sudah dapat menggakses **self-hosted asciinema-server** Anda kembali. \ No newline at end of file +Setelah itu, jalankan semua service asciinema-server seperti biasa dengan menjalankan perintah `docker-compose up -d`. Seharusnya Anda sudah dapat menggakses **self-hosted asciinema-server** Anda kembali. diff --git a/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.md b/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.md index 828b0b0..c28bcc3 100644 --- a/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.md +++ b/content/tutorials/rescue-broken-asciinema-server-upgrade-postgresql-14/index.md @@ -34,7 +34,7 @@ authors: - ditatompel --- -Today, I'm experiencing some problem with my recent [self-hosted asciinema-server](https://asciinema.ditatompel.com/) upgrade. After following the upgrade process according to the [asciinema-server documentation page on GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide), the `phoenix` and `postgresql` containers failed to run and kept restarting. +Today, I'm experiencing some problem with my recent self-hosted asciinema server upgrade. After following the upgrade process according to the [asciinema-server documentation page on GitHub](https://github.com/asciinema/asciinema-server/wiki/Installation-guide), the `phoenix` and `postgresql` containers failed to run and kept restarting. @@ -153,4 +153,4 @@ docker exec -it psql -d postgres -U postgres -f /var/lib/p > _**Note**: Your `DOCKER_CONTAINER_ID` will be different from the previous `DOCKER_CONTAINER_ID`. Make sure to use the correct docker container ID._ ### 4. Run asciinema-server as usual -After that, run all the `asciinema-server` services as usual (`docker-compose up -d`), and you should be able to **access your self-hosted asciinema-server** again. \ No newline at end of file +After that, run all the `asciinema-server` services as usual (`docker-compose up -d`), and you should be able to **access your self-hosted asciinema-server** again.