Skip to content

Commit 526d9ac

Browse files
authored
Update README.md for more clear data of how this repo works
1 parent 81934e3 commit 526d9ac

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,16 @@
11
# Pixelfed Glitch Docker Images
22

3-
Forked from the [in-repo Dockerfiles](https://github.com/pixelfed-glitch/pixelfed/tree/dev/contrib/docker) primarily because I wanted nginx as the web daemon and something to publish to use in a Helm chart.
3+
Forked from the [pixelfed-glitch Dockerfiles](https://github.com/pixelfed-glitch/pixelfed/tree/main/docker) primarily because I wanted nginx as the web daemon and something to publish to use in a Helm chart.
44

55
Tags are rebuilt daily so you should use the SHA hash if mutability concerns you.
66

7-
Images at docker.io/jessebot/pixelfed-glitch
7+
Images at [docker.io/jessebot/pixelfed-glitch](https://hub.docker.com/r/jessebot/pixelfed-glitch/tags).
88

99
Available tags:
10-
- dev-nginx
10+
- develop-nginx (built from the develop branch)
11+
- main-nginx (built from the main branch)
12+
- latest pixelfed-glitch release (repo checked daily for new releases)
1113

1214
## Attribution
1315

14-
This repo is a fork of the a repo managed by Matt Kulka <matt@lqx.net>, so that we can use pixelfed-glitch. Check out their chart upstream if you want to use vanilla pixelfed, as it's great! :)
16+
This repo is a fork of the repo managed by Matt Kulka <matt@lqx.net>, so that we can use the pixelfed-glitch fork. Check out their repo upstream if you want to use vanilla pixelfed, as it's great and they are friendly! :)

0 commit comments

Comments
 (0)