Source Code Control (git)

Hello, everyone. I am new to this community and I intend to run my capsule 
in a kubernetes cluster on my existing rpi4 infra. As part of the CI/CD 
process for my production launch, I need a mechanism (like git) for source code control.

Before I recreate the wheel, does such a thing exist already?
-sba

[sailboat-anon](https://github.com/sailboat-anon) @ gh | 
gemini://sailboat-anon.space/ (launching tomorrow!)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210213/c234
f2b8/attachment.htm>

Am Sa, 13. Feb 2021, um 22:34, schrieb sailboatanon:
> Hello, everyone.  I am new to this community and I intend to run my 
capsule in a kubernetes cluster on my existing rpi4 infra.  As part of the 
CI/CD process for my production launch, I need a mechanism (like git) for 
source code control.
> 
> Before I recreate the wheel, does such a thing exist already?
> -sba

Why not use git?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210213/a0de
ebdc/attachment.htm>

Indeed, we just had a helpful thread on this, and here's what I 
implemented a moment ago on my capsule - it's simple:

- Gemini server (agate, in my case) running in Docker
- Static mount in the container at run-time to /var/capsule on my host, 
which is actually a cloned git repo folder.
- Cronjob on the host to pull the main branch every five minutes or 
whatever to keep the /var/capsule directory up to date.

You can use post receive hooks too, that would be basically the same.
>> Link to the container definition for the Agage 
docker:?https://github.com/davidemerson/nnix.com-gemini

Regards,
David
Feb 13, 2021, 17:05 by louis at brauer.family:

> Am Sa, 13. Feb 2021, um 22:34, schrieb sailboatanon:
>
>> Hello, everyone.? I am new to this community and I intend to run my 
capsule in a kubernetes cluster on my existing rpi4 infra.? As part of the 
CI/CD process for my production launch, I  need a mechanism (like git) for 
source code control.
>>
>> Before I recreate the wheel, does such a thing exist already?
>> -sba
>>
>
> Why not use git?
>

On Sat, Feb 13, 2021 at 09:34:25PM +0000,
 sailboatanon <sailboatanon at protonmail.com> wrote 
 a message of 39 lines which said:

> I intend to run my capsule in a kubernetes cluster on my existing
> rpi4 infra.

It is interesting to see Gemini, intended to be a simple and
lightweight protocol, running on such a humongous beast like
Kubernetes.

On Feb 13, 2021, 23:36, Stephane Bortzmeyer < stephane at sources.org> wrote:
> It is interesting to see Gemini, intended to be a simple and lightweight 
protocol, running on such a humongous beast like Kubernetes.

Gemini is a toy protocol. There are two things nerds do with toy 
protocols: port them to ever smaller hardware, and perform a reductio ad 
absurdam of overengineering a deployment. Gemini on Kubernetes (and 
Kubernetes on Raspberry Pis in general!) is a joke, in the fine tradition 
of Enterprise Grade Fizzbuzz.

Personally, I can't wait for some crazy bastard to write a Gemini server 
in Motorola 68000 assembly for the Amiga.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210214/ed62
7c63/attachment.htm>

On Sun, Feb 14, 2021 at 07:48:53AM +0000,
 Jonathan Lane <jon at dorsal.tk> wrote 
 a message of 38 lines which said:

> Personally, I can't wait for some crazy bastard to write a Gemini
> server in Motorola 68000 assembly for the Amiga.

TLS will certainly create interesting challenges. (Unicode, too.)

This is exactly the reason I chose this project :) Gemini is simple, 
small-scale. K8s is unfathomable enterprise-scale. I have a 'personal 
cloud' at home - 4 RPis running clusters of DNS, DHCP, SMTP, and now Gemini.

If anyone is interested, it's open source (but WIP): 
https://github.com/sailboat-anon/mintranet/wiki/Features---Toolset

I'll be releasing the Docker buildfiles and source for my gemini server to 
this community in the coming days.

Sent with [ProtonMail](https://protonmail.com) Secure Email.

??????? Original Message ???????
On Saturday, February 13, 2021 11:48 PM, Jonathan Lane <jon at dorsal.tk> wrote:

> On Feb 13, 2021, 23:36, Stephane Bortzmeyer < stephane at sources.org> wrote:
>> It is interesting to see Gemini, intended to be a simple and 
lightweight protocol, running on such a humongous beast like Kubernetes.
>
> Gemini is a toy protocol. There are two things nerds do with toy 
protocols: port them to ever smaller hardware, and perform a reductio ad 
absurdam of overengineering a deployment. Gemini on Kubernetes (and 
Kubernetes on Raspberry Pis in general!) is a joke, in the fine tradition 
of Enterprise Grade Fizzbuzz.
>
> Personally, I can't wait for some crazy bastard to write a Gemini server 
in Motorola 68000 assembly for the Amiga.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210214/8c5e
769c/attachment.htm>

Stephane Bortzmeyer <stephane at sources.org> wrote:

> On Sun, Feb 14, 2021 at 07:48:53AM +0000,
>  Jonathan Lane <jon at dorsal.tk> wrote
>  a message of 38 lines which said:
>
> > Personally, I can't wait for some crazy bastard to write a Gemini
> > server in Motorola 68000 assembly for the Amiga.
>
> TLS will certainly create interesting challenges. (Unicode, too.)
>

AmiSSL[1] has full compatibility with the latest OpenSSL, requires 68020 or
higher and AmigaOS 3 or higher. The crypto itself would still take a long
time.

There also exist a unicode library called Ucode[2]. But since I discovered
it when writing this email, I don't know if it's usable for such a project.
Keeping up with the new Unicode versions is a project of itself.

While on the Amiga programming topic, I've been spending one or two hours
every Saturday evening (just a few weeks in a row) teaching myself Amiga E.

Inspired by Amiga E's 32 bit chars and AmiSSL for Amiga E[3], I've started
to write a gemtext parser (ASCII only at first, then Latin1 characters in
UTF-8) in the hope I can add enough features to eventually call it a gemini
client.

I wouldn't attempt doing it in M68k assembly, though.

[1] http://aminet.net/package/util/libs/AmiSSL-4.7

[2] http://aminet.net/package/text/show/Ucode

[3] http://aminet.net/package/dev/e/AmiSSL_in_E

-- 
Katarina . o O (we might have strayed a bit from the topic)

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210215/5c17
209e/attachment-0001.htm>

You'd only need Ucode if you were writing a client; a server doesn't have
to display anything.  And Unicode only grows by adding new characters:
existing ones never get removed and most of their properties don't change
either, so keeping up actually isn't that hard.


On Sun, Feb 14, 2021 at 9:15 PM Katarina Eriksson <gmym at coopdot.com> wrote:

> Stephane Bortzmeyer <stephane at sources.org> wrote:
>
>> On Sun, Feb 14, 2021 at 07:48:53AM +0000,
>>  Jonathan Lane <jon at dorsal.tk> wrote
>>  a message of 38 lines which said:
>>
>> > Personally, I can't wait for some crazy bastard to write a Gemini
>> > server in Motorola 68000 assembly for the Amiga.
>>
>> TLS will certainly create interesting challenges. (Unicode, too.)
>>
>
> AmiSSL[1] has full compatibility with the latest OpenSSL, requires 68020
> or higher and AmigaOS 3 or higher. The crypto itself would still take a
> long time.
>
> There also exist a unicode library called Ucode[2]. But since I discovered
> it when writing this email, I don't know if it's usable for such a project.
> Keeping up with the new Unicode versions is a project of itself.
>
> While on the Amiga programming topic, I've been spending one or two hours
> every Saturday evening (just a few weeks in a row) teaching myself Amiga E.
>
> Inspired by Amiga E's 32 bit chars and AmiSSL for Amiga E[3], I've started
> to write a gemtext parser (ASCII only at first, then Latin1 characters in
> UTF-8) in the hope I can add enough features to eventually call it a gemini
> client.
>
> I wouldn't attempt doing it in M68k assembly, though.
>
> [1] http://aminet.net/package/util/libs/AmiSSL-4.7
>
> [2] http://aminet.net/package/text/show/Ucode
>
> [3] http://aminet.net/package/dev/e/AmiSSL_in_E
>
> --
> Katarina . o O (we might have strayed a bit from the topic)
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210214/acc5
7c61/attachment.htm>