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.
This commit is contained in:
Cristian Ditaputratama 2024-04-10 19:29:54 +07:00 committed by mergify[bot]
parent 5c22571406
commit 1fd5b345ec
4 changed files with 7 additions and 15 deletions

View file

@ -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:
<script id="asciicast-14" src="https://asciinema.ditatompel.com/a/14.js" async></script>
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/)
* [https://docs.joinmastodon.org/admin/install/](https://docs.joinmastodon.org/admin/install/)

View file

@ -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)
<script id="asciicast-14" src="https://asciinema.ditatompel.com/a/14.js" async></script>
Or the whole YouTube video:
The video below is the whole process I install Mastodon instance (for reference)
{{< youtube eBUr7JFiGMo >}}

View file

@ -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.
<!--more-->
@ -147,4 +147,4 @@ docker exec -it <DOCKER_CONTAINER_ID> 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.
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.

View file

@ -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.
<!--more-->
@ -153,4 +153,4 @@ docker exec -it <DOCKER_CONTAINER_ID> 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.
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.