like I'm glad they're not a thing here xD otherwise we wouldn't be having as much conversations going on in here. but I get it, and do appreciate it. 🙏
like I'm glad they're not a thing here xD otherwise we wouldn't be having as much conversations going on in here. but I get it, and do appreciate it. 🙏
Termux same thing @doesnm uses and it worked 👍 
Termux same thing @doesnm uses and it worked 👍
Termux same thing @doesnm uses and it worked 👍
Pizza Hut's tavern style "ultimate" pizza
https://www.youtube.com/watch?v=ZYp7EmEgxg0
e
FROM golang:alpine as builder
ARG version
ENV HTWTXT_VERSION=$version
WORKDIR $GOPATH/pkg/
RUN wget -O htwtxt.tar.gz https://github.com/plomlompom/htwtxt/archive/refs/tags/${HTWTXT_VERSION}.tar.gz
RUN tar xf htwtxt.tar.gz && cd htwtxt-${HTWTXT_VERSION} && go mod init htwtxt && go mod tidy && go install htwtxt
FROM alpine
ARG version
ENV HTWTXT_VERSION=$version
RUN mkdir -p /srv/htwtxt
COPY --from=builder /go/bin/htwtxt /usr/bin/
COPY --from=builder /go/pkg/htwtxt-${HTWTXT_VERSION}/templates/* /srv/htwtxt/templates/
WORKDIR /srv/htwtxt
VOLUME /srv/htwtxt
EXPOSE 8000
ENTRYPOINT ["htwtxt", "-dir", "/srv/htwtxt", "-templates", "/srv/htwtxt/templates"]
Don't forget the
--build-arg version="1.0.7" for example when building this one, although there isn't much difference between the couple last versions.P.S: I may have effed up changing htwtxt's files directory to
/srv/htwtxt when the command itself defaults to /root/htwtxt so you'll have to throw in a -dir whenever you issue an htwtxt command (i.e: htwtxt -adduser somename:somepwd -dir /srv/htwtxt ... etc)
e
FROM golang:alpine as builder
ARG version
ENV HTWTXT_VERSION=$version
WORKDIR $GOPATH/pkg/
RUN wget -O htwtxt.tar.gz https://github.com/plomlompom/htwtxt/archive/refs/tags/${HTWTXT_VERSION}.tar.gz
RUN tar xf htwtxt.tar.gz && cd htwtxt-${HTWTXT_VERSION} && go mod init htwtxt && go mod tidy && go install htwtxt
FROM alpine
ARG version
ENV HTWTXT_VERSION=$version
RUN mkdir -p /srv/htwtxt
COPY --from=builder /go/bin/htwtxt /usr/bin/
COPY --from=builder /go/pkg/htwtxt-${HTWTXT_VERSION}/templates/* /srv/htwtxt/templates/
WORKDIR /srv/htwtxt
VOLUME /srv/htwtxt
EXPOSE 8000
ENTRYPOINT ["htwtxt", "-dir", "/srv/htwtxt", "-templates", "/srv/htwtxt/templates"]
Don't forget the
--build-arg version="1.0.7" for example when building this one, although there isn't much difference between the couple last versions.P.S: I may have effed up changing htwtxt's files directory to
/srv/htwtxt when the command itself defaults to /root/htwtxt so you'll have to throw in a -dir whenever you issue an htwtxt command (i.e: htwtxt -adduser somename:somepwd -dir /srv/htwtxt ... etc)
e
FROM golang:alpine as builder
ARG version
ENV HTWTXT_VERSION=$version
WORKDIR $GOPATH/pkg/
RUN wget -O htwtxt.tar.gz https://github.com/plomlompom/htwtxt/archive/refs/tags/${HTWTXT_VERSION}.tar.gz
RUN tar xf htwtxt.tar.gz && cd htwtxt-${HTWTXT_VERSION} && go mod init htwtxt && go mod tidy && go install htwtxt
FROM alpine
ARG version
ENV HTWTXT_VERSION=$version
RUN mkdir -p /srv/htwtxt
COPY --from=builder /go/bin/htwtxt /usr/bin/
COPY --from=builder /go/pkg/htwtxt-${HTWTXT_VERSION}/templates/* /srv/htwtxt/templates/
WORKDIR /srv/htwtxt
VOLUME /srv/htwtxt
EXPOSE 8000
ENTRYPOINT ["htwtxt", "-dir", "/srv/htwtxt", "-templates", "/srv/htwtxt/templates"]
Don't forget the
--build-arg version="1.0.7" for example when building this one, although there isn't much difference between the couple last versions.P.S: I may have effed up changing htwtxt's files directory to
/srv/htwtxt when the command itself defaults to /root/htwtxt so you'll have to throw in a -dir whenever you issue an htwtxt command (i.e: htwtxt -adduser somename:somepwd -dir /srv/htwtxt ... etc)
h
~/remote/htwtxt » podman image list htwtxt the@wks
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/htwtxt 1.0.5-alpine 13610a37e347 3 hours ago 20.1 MB
localhost/htwtxt 1.0.7-alpine 2a5c560ee6b7 3 hours ago 20.1 MB
docker.io/buckket/htwtxt latest c0e33b2913c6 8 years ago 778 MB
h
~/remote/htwtxt » podman image list htwtxt the@wks
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/htwtxt 1.0.5-alpine 13610a37e347 3 hours ago 20.1 MB
localhost/htwtxt 1.0.7-alpine 2a5c560ee6b7 3 hours ago 20.1 MB
docker.io/buckket/htwtxt latest c0e33b2913c6 8 years ago 778 MB
h
~/remote/htwtxt » podman image list htwtxt the@wks
REPOSITORY TAG IMAGE ID CREATED SIZE
localhost/htwtxt 1.0.5-alpine 13610a37e347 3 hours ago 20.1 MB
localhost/htwtxt 1.0.7-alpine 2a5c560ee6b7 3 hours ago 20.1 MB
docker.io/buckket/htwtxt latest c0e33b2913c6 8 years ago 778 MB
go install github.com/plomlompom/htwtxt@1.0.7 as well as h
# this is snippet from what I used for the Dockerfile but I guess it should work just fine.
cd ~/go/pkg && wget -O htwtxt.tar.gz https://github.com/plomlompom/htwtxt/archive/refs/tags/1.0.7.tar.gz
tar xf htwtxt.tar.gz && cd htwtxt-1.0.7 && go mod init htwtxt && go mod tidy && go install htwtxt
both worked just fine...
go install github.com/plomlompom/htwtxt@1.0.7 as well as h
# this is snippet from what I used for the Dockerfile but I guess it should work just fine.
cd ~/go/pkg && wget -O htwtxt.tar.gz https://github.com/plomlompom/htwtxt/archive/refs/tags/1.0.7.tar.gz
tar xf htwtxt.tar.gz && cd htwtxt-1.0.7 && go mod init htwtxt && go mod tidy && go install htwtxt
both worked just fine...
go install github.com/plomlompom/htwtxt@1.0.7 as well as h
# this is snippet from what I used for the Dockerfile but I guess it should work just fine.
cd ~/go/pkg && wget -O htwtxt.tar.gz https://github.com/plomlompom/htwtxt/archive/refs/tags/1.0.7.tar.gz
tar xf htwtxt.tar.gz && cd htwtxt-1.0.7 && go mod init htwtxt && go mod tidy && go install htwtxt
both worked just fine...
Yeah, metadata is an extension, and not part of the original spec.
- I don't see a way to follow others, all I can do is go to the /feeds URI for a list of the server's users/feeds.
- I still couldn't figure out how to get a direct link to a user's twtxt file, curling /feeds/usernick spits out a list of the user usernick twts, so I guess you could use that to follow them.
- no way to add in your
# nick = usernick / # url = proto://domain.ltd/path/to/twtxt.txt ...etc. Probably because that wasn't part of the spec back then?So yeah, it would make for a nice project while learning Go. :P
- I don't see a way to follow others, all I can do is go to the /feeds URI for a list of the server's users/feeds.
- I still couldn't figure out how to get a direct link to a user's twtxt file, curling /feeds/usernick spits out a list of the user usernick twts, so I guess you could use that to follow them.
- no way to add in your
# nick = usernick / # url = proto://domain.ltd/path/to/twtxt.txt ...etc. Probably because that wasn't part of the spec back then?So yeah, it would make for a nice project while learning Go. :P
- I don't see a way to follow others, all I can do is go to the /feeds URI for a list of the server's users/feeds.
- I still couldn't figure out how to get a direct link to a user's twtxt file, curling /feeds/usernick spits out a list of the user usernick twts, so I guess you could use that to follow them.
- no way to add in your
# nick = usernick / # url = proto://domain.ltd/path/to/twtxt.txt ...etc. Probably because that wasn't part of the spec back then?So yeah, it would make for a nice project while learning Go. :P
>
I didn't mean as if I was perceiving the use of Yarn to be malicious, but rather not accurate, and perhaps misleading, or confussing. But I got it when Soren explained it. He used yarn (lower case) after twtxt, because at some point there were considerations to call the "evolved" twtxt, with the several additions/enhancements, "yarn". After all, current twtxt/yarn has moved beyond the original twtxt.
Single user Twtxt "Yarn Pod **Like**" software help you sleep better at night? And just in case things are not clear here, I'm being sarcastic (well, kinda...) and not trying to gaslight anyone. Think of my comment as Bromance or something like that LOL.But seriously, Just like any UNIX-Like system to Unix™, as in non of them are UNIX™, but each of them is providing more or less similar experience and re-implementing what once was parts of "UNIX™ software" their own (more or less better) ways. Timeline is Yarn™ Pod like, (my personal take on the word pod is: "an instance of XYZ software acting an _escape POD_ from X-BS for... ABC reasons.") providing more or less of a similar experience, implementing some of Yarn.social Extensions, trying to add in some more ...etc.
Otherwise, I don't see the
Yarn pod mention as some kind of malicious manoeuvre, but more of a tribute to what (might have) sparked inspiration for creating Timeline? Also, our friend @sorenpeter here has got a valid reason for using PHP (#tms7aka) so let's let's put our unease towards the language itself aside and maybe just help however/as much as we can in order to make internet (the World?) a better place.