Let's do it the manual way, so you learn how to work with Dokku.
Here's an SSH config for dokku.autonomic.zone.
Host dokku.autonomic.zone
Hostname dokku.autonomic.zone
User kawaiipunk
Port 222
IdentityFile ~/.ssh/{yourprivatekey}
SSH to the Dokku server with ssh dokku.autonomic.zone. Your sudo password is in the pass store which you'll need to interact with the dokku command.
Now, create an application with dokku apps:create kawaiipunk.xyz. Then set the domain for that application with dokku domains:add kawaiipunk.xyz kawaiipunk.xyz.
Make sure you have your kawaiipunk.xyz DNS A record pointed at the dokku.autonomic.zone machine which is 94.130.105.60. You can check quickly with sudo apt install dnsutils && dig +short dokku.autonomic.zone. It has to already be switched over for lets encrypt certificates to be configured properly.
In your local git clone of this repository, run git remote add dokku dokku@dokku.autonomic.zone:kawaiipunk.xyz
Let's do it the manual way, so you learn how to work with Dokku.
Here's an SSH config for `dokku.autonomic.zone`.
```
Host dokku.autonomic.zone
Hostname dokku.autonomic.zone
User kawaiipunk
Port 222
IdentityFile ~/.ssh/{yourprivatekey}
```
1. SSH to the Dokku server with `ssh dokku.autonomic.zone`. Your sudo password is in the pass store which you'll need to interact with the dokku command.
1. Now, create an application with `dokku apps:create kawaiipunk.xyz`. Then set the domain for that application with `dokku domains:add kawaiipunk.xyz kawaiipunk.xyz`.
1. Make sure you have your `kawaiipunk.xyz` DNS A record pointed at the `dokku.autonomic.zone` machine which is `94.130.105.60`. You can check quickly with `sudo apt install dnsutils && dig +short dokku.autonomic.zone`. It has to already be switched over for lets encrypt certificates to be configured properly.
1. In your local git clone of this repository, run `git remote add dokku dokku@dokku.autonomic.zone:kawaiipunk.xyz`
1. Run `git push dokku`. Your site should be live at https://kawaiipunk.xyz.
If you have issues, post 'em here!
Hmm ok, so I followed those steps. It all went as expected but we're missing two steps from the instructions.
Creating a .drone.yml file and manually activating the repo on drone.
Hmm ok, so I followed those steps. It all went as expected but we're missing two steps from the instructions.
Creating a .drone.yml file and manually activating the repo on drone.
First one for the .drone.yml file is:
```
---
kind: pipeline
name: default
steps:
- name: Deploy wiki with Dokku
image: appleboy/drone-git-push:0.2.0-linux-amd64
settings:
remote: ssh://dokku@dokku.autonomic.zone:222/kawaiipunk.xyz
ssh_key:
from_secret: drone_deploy_key
trigger:
branch:
- master
```
So you just need to do pass show deploy_key/drone | xclip and then add that as "drone_deploy_key" in the drone settings config
And the other missing step was:
> So you just need to do `pass show deploy_key/drone | xclip` and then add that as "drone_deploy_key" in the drone settings config
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Let's do it the manual way, so you learn how to work with Dokku.
Here's an SSH config for
dokku.autonomic.zone.ssh dokku.autonomic.zone. Your sudo password is in the pass store which you'll need to interact with the dokku command.dokku apps:create kawaiipunk.xyz. Then set the domain for that application withdokku domains:add kawaiipunk.xyz kawaiipunk.xyz.kawaiipunk.xyzDNS A record pointed at thedokku.autonomic.zonemachine which is94.130.105.60. You can check quickly withsudo apt install dnsutils && dig +short dokku.autonomic.zone. It has to already be switched over for lets encrypt certificates to be configured properly.git remote add dokku dokku@dokku.autonomic.zone:kawaiipunk.xyzgit push dokku. Your site should be live at https://kawaiipunk.xyz.If you have issues, post 'em here!
Hmm ok, so I followed those steps. It all went as expected but we're missing two steps from the instructions.
Creating a .drone.yml file and manually activating the repo on drone.
First one for the .drone.yml file is:
And the other missing step was:
Everything done broke
Sorted, closing!