Fluffy/WebsiteFluffy
1
0
Fork 0
mirror of https://github.com/Fluffy-Bean/website.git synced 2025-05-14 08:02:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

style: format code with Prettier

Browse source 
This commit fixes the style issues introduced in 9429fd2 according to the output
from Prettier.

Details: None
This commit is contained in:
deepsource-autofix[bot] 2025-03-30 22:51:45 +00:00 • committed by GitHub
parent 9429fd2a94
commit eaad25cca6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 13 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
.woodpecker/build.yaml
View file

@ -1,10 +1,10 @@
when: when:
- event: push - event: push
branch: main branch: main
steps: steps:
- name: build - name: build
image: node:23-alpine3.20 image: node:23-alpine3.20
commands: commands:
- npm install - npm install
- npm run build - npm run build

9
src/content/posts/2024_11_07-umami.mdx
View file

@ -17,8 +17,8 @@ import Note from "../../components/Note.astro";
This little blog post thang will be about umami, and why I went with it over fixing my Plausible install. While the This little blog post thang will be about umami, and why I went with it over fixing my Plausible install. While the
reason is pretty simple, really and can be summed up in two points. reason is pretty simple, really and can be summed up in two points.
- Its resource usage is low - Its resource usage is low
- Has (nearly) all the features I used in Plausible - Has (nearly) all the features I used in Plausible
I want to talk a bit about how I got to the point where I chosen it, and the steps I've taken to actually install and I want to talk a bit about how I got to the point where I chosen it, and the steps I've taken to actually install and
setup an Alpine CT with itttt setup an Alpine CT with itttt
@ -60,7 +60,7 @@ Maybe I could pick it up in the future, and bring it back to life again
<Note text="Blank sections are due to me not being able to find information on the feature" /> <Note text="Blank sections are due to me not being able to find information on the feature" />
| | Matomo | PostHog | umami | Fathom lite | Plausible | | | Matomo | PostHog | umami | Fathom lite | Plausible |
|-------------------------------|--------|----------------------------|-----------------------------|------------------------------|----------------------------| | ----------------------------- | ------ | -------------------------- | --------------------------- | ---------------------------- | -------------------------- |
| Self-Hostable | Yes | Yes | Yes | Yes [^fathom-self-host] | Yes | | Self-Hostable | Yes | Yes | Yes | Yes [^fathom-self-host] | Yes |
| Hosting method | PHP | Docker | Node or Docker | Go [^fathom-language] | Docker | | Hosting method | PHP | Docker | Node or Docker | Go [^fathom-language] | Docker |
| GDPR compliant | Yes | Yes | Yes | No [^fathom-gdpr-compliance] | Yes | | GDPR compliant | Yes | Yes | Yes | No [^fathom-gdpr-compliance] | Yes |
@ -118,6 +118,7 @@ apk add vim git
I didn't reaaaaaly need caddy for this, as it would mean the service would be behind two proxies, but I wanted to setup I didn't reaaaaaly need caddy for this, as it would mean the service would be behind two proxies, but I wanted to setup
caddy anyway. It was quite simple really caddy anyway. It was quite simple really
```bash ```bash
apk add caddy apk add caddy
rc-update add caddy rc-update add caddy
@ -129,10 +130,12 @@ mkdir /var/www/html
Then, in `/etc/caddy`, we edit the `Caddyfile`, use your favorite editor for this, but I like vim, so for me I would run Then, in `/etc/caddy`, we edit the `Caddyfile`, use your favorite editor for this, but I like vim, so for me I would run
`vim Caddyfile`. Then set the contents to the following `vim Caddyfile`. Then set the contents to the following
```caddyfile ```caddyfile
:8080 :8080
reverse_proxy localhost:3000 reverse_proxy localhost:3000
``` ```
<Note text="3000 is the default port for yarn, but adjust for your needs" /> <Note text="3000 is the default port for yarn, but adjust for your needs" />
And finally we just need to reload the service, still within `/etc/caddy`, with `caddy reload`! And finally we just need to reload the service, still within `/etc/caddy`, with `caddy reload`!