1# Soft Serve
  2
  3<p>
  4    <img style="width: 451px" src="https://stuff.charm.sh/soft-serve/soft-serve-header.png?0" alt="A nice rendering of some melting ice cream with the words ‘Charm Soft Serve’ next to it"><br>
  5    <a href="https://github.com/charmbracelet/soft-serve/releases"><img src="https://img.shields.io/github/release/charmbracelet/soft-serve.svg" alt="Latest Release"></a>
  6    <a href="https://pkg.go.dev/github.com/charmbracelet/soft-serve?tab=doc"><img src="https://godoc.org/github.com/golang/gddo?status.svg" alt="GoDoc"></a>
  7    <a href="https://github.com/charmbracelet/soft-serve/actions"><img src="https://github.com/charmbracelet/soft-serve/workflows/build/badge.svg" alt="Build Status"></a>
  8    <a href="https://nightly.link/charmbracelet/soft-serve/workflows/nightly/main"><img src="https://shields.io/badge/-Nightly%20Builds-orange?logo=hackthebox&logoColor=fff&style=appveyor"/></a>
  9</p>
 10
 11A tasty, self-hostable Git server for the command line. 🍦
 12
 13<picture>
 14  <source media="(max-width: 750px)" srcset="https://github.com/charmbracelet/soft-serve/assets/42545625/c754c746-dc4c-44a6-9c39-28649264cbf2">
 15  <source media="(min-width: 750px)" width="750" srcset="https://github.com/charmbracelet/soft-serve/assets/42545625/c754c746-dc4c-44a6-9c39-28649264cbf2">
 16  <img src="https://github.com/charmbracelet/soft-serve/assets/42545625/c754c746-dc4c-44a6-9c39-28649264cbf2" alt="Soft Serve screencast">
 17</picture>
 18
 19- Easy to navigate TUI available over SSH
 20- Clone repos over SSH, HTTP, or Git protocol
 21- Git LFS support with both HTTP and SSH backends
 22- Manage repos with SSH
 23- Create repos on demand with SSH or `git push`
 24- Browse repos, files and commits with SSH-accessible UI
 25- Print files over SSH with or without syntax highlighting and line numbers
 26- Easy access control
 27  - SSH authentication using public keys
 28  - Allow/disallow anonymous access
 29  - Add collaborators with SSH public keys
 30  - Repos can be public or private
 31  - User access tokens
 32
 33## Where can I see it?
 34
 35Just run `ssh git.charm.sh` for an example. You can also try some of the following commands:
 36
 37```bash
 38# Jump directly to a repo in the TUI
 39ssh git.charm.sh -t soft-serve
 40
 41# Print out a directory tree for a repo
 42ssh git.charm.sh repo tree soft-serve
 43
 44# Print a specific file
 45ssh git.charm.sh repo blob soft-serve cmd/soft/root.go
 46
 47# Print a file with syntax highlighting and line numbers
 48ssh git.charm.sh repo blob soft-serve cmd/soft/root.go -c -l
 49```
 50
 51## Installation
 52
 53Soft Serve is a single binary called `soft`. You can get it from a package
 54manager:
 55
 56```bash
 57# macOS or Linux
 58brew tap charmbracelet/tap && brew install charmbracelet/tap/soft-serve
 59
 60# Arch Linux
 61pacman -S soft-serve
 62
 63# Nix
 64nix-env -iA nixpkgs.soft-serve
 65
 66# Debian/Ubuntu
 67sudo mkdir -p /etc/apt/keyrings
 68curl -fsSL https://repo.charm.sh/apt/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/charm.gpg
 69echo "deb [signed-by=/etc/apt/keyrings/charm.gpg] https://repo.charm.sh/apt/ * *" | sudo tee /etc/apt/sources.list.d/charm.list
 70sudo apt update && sudo apt install soft-serve
 71
 72# Fedora/RHEL
 73echo '[charm]
 74name=Charm
 75baseurl=https://repo.charm.sh/yum/
 76enabled=1
 77gpgcheck=1
 78gpgkey=https://repo.charm.sh/yum/gpg.key' | sudo tee /etc/yum.repos.d/charm.repo
 79sudo yum install soft-serve
 80```
 81
 82You can also download a binary from the [releases][releases] page. Packages are
 83available in Alpine, Debian, and RPM formats. Binaries are available for Linux,
 84macOS, and Windows.
 85
 86[releases]: https://github.com/charmbracelet/soft-serve/releases
 87
 88Or just install it with `go`:
 89
 90```bash
 91go install github.com/charmbracelet/soft-serve/cmd/soft@latest
 92```
 93
 94A [Docker image][docker] is also available.
 95
 96[docker]: https://github.com/charmbracelet/soft-serve/blob/main/docker.md
 97
 98## Setting up a server
 99
100Make sure `git` is installed, then run `soft serve`. That’s it.
101
102This will create a `data` directory that will store all the repos, ssh keys,
103and database.
104
105To change the default data path use `SOFT_SERVE_DATA_PATH` environment variable.
106
107```sh
108SOFT_SERVE_DATA_PATH=/var/lib/soft-serve soft serve
109```
110
111When you run Soft Serve for the first time, make sure you have the
112`SOFT_SERVE_INITIAL_ADMIN_KEYS` environment variable is set to your ssh
113authorized key. Any added key to this variable will be treated as admin with
114full privileges.
115
116Using this environment variable, Soft Serve will create a new `admin` user that
117has full privileges. You can rename and change the user settings later.
118
119Check out [Systemd][systemd] on how to run Soft Serve as a service using
120Systemd. Soft Serve packages in our Apt/Yum repositories come with Systemd
121service units.
122
123[systemd]: https://github.com/charmbracelet/soft-serve/blob/main/systemd.md
124
125### Server Configuration
126
127Once you start the server for the first time, the settings will be in
128`config.yaml` under your data directory. The default `config.yaml` is
129self-explanatory and will look like this:
130
131```yaml
132# Soft Serve Server configurations
133
134# The name of the server.
135# This is the name that will be displayed in the UI.
136name: "Soft Serve"
137
138# Log format to use. Valid values are "json", "logfmt", and "text".
139log_format: "text"
140
141# The SSH server configuration.
142ssh:
143  # The address on which the SSH server will listen.
144  listen_addr: ":23231"
145
146  # The public URL of the SSH server.
147  # This is the address that will be used to clone repositories.
148  public_url: "ssh://localhost:23231"
149
150  # The path to the SSH server's private key.
151  key_path: "ssh/soft_serve_host"
152
153  # The path to the SSH server's client private key.
154  # This key will be used to authenticate the server to make git requests to
155  # ssh remotes.
156  client_key_path: "ssh/soft_serve_client"
157
158  # The maximum number of seconds a connection can take.
159  # A value of 0 means no timeout.
160  max_timeout: 0
161
162  # The number of seconds a connection can be idle before it is closed.
163  idle_timeout: 120
164
165# The Git daemon configuration.
166git:
167  # The address on which the Git daemon will listen.
168  listen_addr: ":9418"
169
170  # The maximum number of seconds a connection can take.
171  # A value of 0 means no timeout.
172  max_timeout: 0
173
174  # The number of seconds a connection can be idle before it is closed.
175  idle_timeout: 3
176
177  # The maximum number of concurrent connections.
178  max_connections: 32
179
180# The HTTP server configuration.
181http:
182  # The address on which the HTTP server will listen.
183  listen_addr: ":23232"
184
185  # The path to the TLS private key.
186  tls_key_path: ""
187
188  # The path to the TLS certificate.
189  tls_cert_path: ""
190
191  # The public URL of the HTTP server.
192  # This is the address that will be used to clone repositories.
193  # Make sure to use https:// if you are using TLS.
194  public_url: "http://localhost:23232"
195
196# The database configuration.
197db:
198  # The database driver to use.
199  # Valid values are "sqlite" and "postgres".
200  driver: "sqlite"
201  # The database data source name.
202  # This is driver specific and can be a file path or connection string.
203  # Make sure foreign key support is enabled when using SQLite.
204  data_source: "soft-serve.db?_pragma=busy_timeout(5000)&_pragma=foreign_keys(1)"
205
206# Git LFS configuration.
207lfs:
208  # Enable Git LFS.
209  enabled: true
210  # Enable Git SSH transfer.
211  ssh_enabled: true
212
213# Cron job configuration
214jobs:
215  mirror_pull: "@every 10m"
216
217# The stats server configuration.
218stats:
219  # The address on which the stats server will listen.
220  listen_addr: ":23233"
221# Additional admin keys.
222#initial_admin_keys:
223#  - "ssh-rsa AAAAB3NzaC1yc2..."
224```
225
226You can also use environment variables, to override these settings. All server
227settings environment variables start with `SOFT_SERVE_` followed by the setting
228name all in uppercase. Here are some examples:
229
230- `SOFT_SERVE_NAME`: The name of the server that will appear in the TUI
231- `SOFT_SERVE_SSH_LISTEN_ADDR`: SSH listen address
232- `SOFT_SERVE_SSH_KEY_PATH`: SSH host key-pair path
233- `SOFT_SERVE_HTTP_LISTEN_ADDR`: HTTP listen address
234- `SOFT_SERVE_HTTP_PUBLIC_URL`: HTTP public URL used for cloning
235- `SOFT_SERVE_GIT_MAX_CONNECTIONS`: The number of simultaneous connections to git daemon
236
237#### Database Configuration
238
239Soft Serve supports both SQLite and Postgres for its database. Like all other Soft Serve settings, you can change the database _driver_ and _data source_ using either `config.yaml` or environment variables. The default config uses SQLite as the default database driver.
240
241To use Postgres as your database, first create a Soft Serve database:
242
243```sh
244psql -h<hostname> -p<port> -U<user> -c 'CREATE DATABASE soft_serve'
245```
246
247Then set the database _data source_ to point to your Postgres database. For instance, if you're running Postgres locally, using the default user `postgres` and using a database name `soft_serve`, you would have this config in your config file or environment variable:
248
249```
250db:
251  driver: "postgres"
252  data_source: "postgres://postgres@localhost:5432/soft_serve?sslmode=disable"
253```
254
255Environment variables equivalent:
256
257```sh
258SOFT_SERVE_DB_DRIVER=postgres \
259SOFT_SERVE_DB_DATA_SOURCE="postgres://postgres@localhost:5432/soft_serve?sslmode=disable" \
260soft serve
261```
262
263You can specify a database connection password in the _data source_ url. For example, `postgres://myuser:dbpass@localhost:5432/my_soft_serve_db`.
264
265#### LFS Configuration
266
267Soft Serve supports both Git LFS [HTTP](https://github.com/git-lfs/git-lfs/blob/main/docs/api/README.md) and [SSH](https://github.com/git-lfs/git-lfs/blob/main/docs/proposals/ssh_adapter.md) protocols out of the box, there is no need to do any extra set up.
268
269Use the `lfs` config section to customize your Git LFS server.
270
271## Server Access
272
273Soft Serve at its core manages your server authentication and authorization. Authentication verifies the identity of a user, while authorization determines their access rights to a repository.
274
275To manage the server users, access, and repos, you can use the SSH command line interface.
276
277Try `ssh localhost -i ~/.ssh/id_ed25519 -p 23231 help` for more info. Make sure
278you use your key here.
279
280For ease of use, instead of specifying the key, port, and hostname every time
281you SSH into Soft Serve, add your own Soft Serve instance entry to your SSH
282config. For instance, to use `ssh soft` instead of typing `ssh localhost -i
283~/.ssh/id_ed25519 -p 23231`, we can define a `soft` entry in our SSH config
284file `~/.ssh/config`.
285
286```conf
287Host soft
288  HostName localhost
289  Port 23231
290  IdentityFile ~/.ssh/id_ed25519
291```
292
293Now, we can do `ssh soft` to SSH into Soft Serve. Since `git` is also aware of
294this config, you can use `soft` as the hostname for your clone commands.
295
296```sh
297git clone ssh://soft/dotfiles
298# make changes
299# add & commit
300git push origin main
301```
302
303> **Note** The `-i` part will be omitted in the examples below for brevity. You
304> can add your server settings to your sshconfig for quicker access.
305
306### Authentication
307
308Everything that needs authentication is done using SSH. Make sure you have
309added an entry for your Soft Serve instance in your `~/.ssh/config` file.
310
311By default, Soft Serve gives ready-only permission to anonymous connections to
312any of the above protocols. This is controlled by two settings `anon-access`
313and `allow-keyless`.
314
315- `anon-access`: Defines the access level for anonymous users. Available
316  options are `no-access`, `read-only`, `read-write`, and `admin-access`.
317  Default is `read-only`.
318- `allow-keyless`: Whether to allow connections that doesn't use keys to pass.
319  Setting this to `false` would disable access to SSH keyboard-interactive,
320  HTTP, and Git protocol connections. Default is `true`.
321
322```sh
323$ ssh -p 23231 localhost settings
324Manage server settings
325
326Usage:
327  ssh -p 23231 localhost settings [command]
328
329Available Commands:
330  allow-keyless Set or get allow keyless access to repositories
331  anon-access   Set or get the default access level for anonymous users
332
333Flags:
334  -h, --help   help for settings
335
336Use "ssh -p 23231 localhost settings [command] --help" for more information about a command.
337```
338
339> **Note** These settings can only be changed by admins.
340
341When `allow-keyless` is disabled, connections that don't use SSH Public Key
342authentication will get denied. This means cloning repos over HTTP(s) or git://
343will get denied.
344
345Meanwhile, `anon-access` controls the access level granted to connections that
346use SSH Public Key authentication but are not registered users. The default
347setting for this is `read-only`. This will grant anonymous connections that use
348SSH Public Key authentication `read-only` access to public repos.
349
350`anon-access` is also used in combination with `allow-keyless` to determine the
351access level for HTTP(s) and git:// clone requests.
352
353#### SSH
354
355Soft Serve doesn't allow duplicate SSH public keys for users. A public key can be associated with one user only. This makes SSH authentication simple and straight forward, add your public key to your Soft Serve user to be able to access Soft Serve.
356
357#### HTTP
358
359You can generate user access tokens through the SSH command line interface. Access tokens can have an optional expiration date. Use your access token as the basic auth user to access your Soft Serve repos through HTTP.
360
361```sh
362# Create a user token
363ssh -p 23231 localhost token create 'my new token'
364ss_1234abc56789012345678901234de246d798fghi
365
366# Or with an expiry date
367ssh -p 23231 localhost token create --expires-in 1y 'my other token'
368ss_98fghi1234abc56789012345678901234de246d7
369```
370
371Now you can access to repos that require `read-write` access.
372
373```sh
374git clone http://ss_98fghi1234abc56789012345678901234de246d7@localhost:23232/my-private-repo.git my-private-repo
375# Make changes and push
376```
377
378### Authorization
379
380Soft Serve offers a simple access control. There are four access levels,
381no-access, read-only, read-write, and admin-access.
382
383`admin-access` has full control of the server and can make changes to users and repos.
384
385`read-write` access gets full control of repos.
386
387`read-only` can read public repos.
388
389`no-access` denies access to all repos.
390
391## User Management
392
393Admins can manage users and their keys using the `user` command. Once a user is
394created and has access to the server, they can manage their own keys and
395settings.
396
397To create a new user simply use `user create`:
398
399```sh
400# Create a new user
401ssh -p 23231 localhost user create beatrice
402
403# Add user keys
404ssh -p 23231 localhost user add-pubkey beatrice ssh-rsa AAAAB3Nz...
405ssh -p 23231 localhost user add-pubkey beatrice ssh-ed25519 AAAA...
406
407# Create another user with public key
408ssh -p 23231 localhost user create frankie '-k "ssh-ed25519 AAAATzN..."'
409
410# Need help?
411ssh -p 23231 localhost user help
412```
413
414Once a user is created, they get `read-only` access to public repositories.
415They can also create new repositories on the server.
416
417Users can manage their keys using the `pubkey` command:
418
419```sh
420# List user keys
421ssh -p 23231 localhost pubkey list
422
423# Add key
424ssh -p 23231 localhost pubkey add ssh-ed25519 AAAA...
425
426# Wanna change your username?
427ssh -p 23231 localhost set-username yolo
428
429# To display user info
430ssh -p 23231 localhost info
431```
432
433## Repositories
434
435You can manage repositories using the `repo` command.
436
437```sh
438# Run repo help
439$ ssh -p 23231 localhost repo help
440Manage repositories
441
442Usage:
443  ssh -p 23231 localhost repo [command]
444
445Aliases:
446  repo, repos, repository, repositories
447
448Available Commands:
449  blob         Print out the contents of file at path
450  branch       Manage repository branches
451  collab       Manage collaborators
452  create       Create a new repository
453  delete       Delete a repository
454  description  Set or get the description for a repository
455  hide         Hide or unhide a repository
456  import       Import a new repository from remote
457  info         Get information about a repository
458  is-mirror    Whether a repository is a mirror
459  list         List repositories
460  private      Set or get a repository private property
461  project-name Set or get the project name for a repository
462  rename       Rename an existing repository
463  tag          Manage repository tags
464  tree         Print repository tree at path
465
466Flags:
467  -h, --help   help for repo
468
469Use "ssh -p 23231 localhost repo [command] --help" for more information about a command.
470```
471
472To use any of the above `repo` commands, a user must be a collaborator in the repository. More on this below.
473
474### Creating Repositories
475
476To create a repository, first make sure you are a registered user. Use the
477`repo create <repo>` command to create a new repository:
478
479```sh
480# Create a new repository
481ssh -p 23231 localhost repo create icecream
482
483# Create a repo with description
484ssh -p 23231 localhost repo create icecream '-d "This is an Ice Cream description"'
485
486# ... and project name
487ssh -p 23231 localhost repo create icecream '-d "This is an Ice Cream description"' '-n "Ice Cream"'
488
489# I need my repository private!
490ssh -p 23231 localhost repo create icecream -p '-d "This is an Ice Cream description"' '-n "Ice Cream"'
491
492# Help?
493ssh -p 23231 localhost repo create -h
494```
495
496Or you can add your Soft Serve server as a remote to any existing repo, given
497you have write access, and push to remote:
498
499```
500git remote add origin ssh://localhost:23231/icecream
501```
502
503After you’ve added the remote just go ahead and push. If the repo doesn’t exist
504on the server it’ll be created.
505
506```
507git push origin main
508```
509
510Repositories can be nested too:
511
512```sh
513# Create a new nested repository
514ssh -p 23231 localhost repo create charmbracelet/icecream
515
516# Or ...
517git remote add charm ssh://localhost:23231/charmbracelet/icecream
518git push charm main
519```
520
521### Deleting Repositories
522
523You can delete repositories using the `repo delete <repo>` command.
524
525```sh
526ssh -p 23231 localhost repo delete icecream
527```
528
529### Renaming Repositories
530
531Use the `repo rename <old> <new>` command to rename existing repositories.
532
533```sh
534ssh -p 23231 localhost repo rename icecream vanilla
535```
536
537### Repository Collaborators
538
539Sometimes you want to restrict write access to certain repositories. This can
540be achieved by adding a collaborator to your repository.
541
542Use the `repo collab <command> <repo>` command to manage repo collaborators.
543
544```sh
545# Add collaborator to soft-serve
546ssh -p 23231 localhost repo collab add soft-serve frankie
547
548# Add collaborator with a specific access level
549ssh -p 23231 localhost repo collab add soft-serve beatrice read-only
550
551# Remove collaborator
552ssh -p 23231 localhost repo collab remove soft-serve beatrice
553
554# List collaborators
555ssh -p 23231 localhost repo collab list soft-serve
556```
557
558### Repository Metadata
559
560You can also change the repo's description, project name, whether it's private,
561etc using the `repo <command>` command.
562
563```sh
564# Set description for repo
565ssh -p 23231 localhost repo description icecream "This is a new description"
566
567# Hide repo from listing
568ssh -p 23231 localhost repo hidden icecream true
569
570# List repository info (branches, tags, description, etc)
571ssh -p 23231 localhost repo icecream info
572```
573
574To make a repository private, use `repo private <repo> [true|false]`. Private
575repos can only be accessed by admins and collaborators.
576
577```sh
578ssh -p 23231 localhost repo icecream private true
579```
580
581### Repository Branches & Tags
582
583Use `repo branch` and `repo tag` to list, and delete branches or tags. You can
584also use `repo branch default` to set or get the repository default branch.
585
586### Repository Tree
587
588To print a file tree for the project, just use the `repo tree` command along with
589the repo name as the SSH command to your Soft Serve server:
590
591```sh
592ssh -p 23231 localhost repo tree soft-serve
593```
594
595You can also specify the sub-path and a specific reference or branch.
596
597```sh
598ssh -p 23231 localhost repo tree soft-serve server/config
599ssh -p 23231 localhost repo tree soft-serve main server/config
600```
601
602From there, you can print individual files using the `repo blob` command:
603
604```sh
605ssh -p 23231 localhost repo blob soft-serve cmd/soft/root.go
606```
607
608You can add the `-c` flag to enable syntax coloring and `-l` to print line
609numbers:
610
611```sh
612ssh -p 23231 localhost repo blob soft-serve cmd/soft/root.go -c -l
613
614```
615
616Use `--raw` to print raw file contents. This is useful for dumping binary data.
617
618## The Soft Serve TUI
619
620<img src="https://stuff.charm.sh/soft-serve/soft-serve-demo-commit.png" width="750" alt="TUI example showing a diff">
621
622Soft Serve serves a TUI over SSH for browsing repos, viewing files and commits,
623and grabbing clone commands:
624
625```sh
626ssh localhost -p 23231
627```
628
629It's also possible to “link” to a specific repo:
630
631```sh
632ssh -p 23231 localhost -t soft-serve
633```
634
635You can copy text to your clipboard over SSH. For instance, you can press
636<kbd>c</kbd> on the highlighted repo in the menu to copy the clone command
637[^osc52].
638
639[^osc52]:
640    Copying over SSH depends on your terminal support of OSC52. Refer to
641    [go-osc52](https://github.com/aymanbagabas/go-osc52) for more information.
642
643## Hooks
644
645Soft Serve supports git server-side hooks `pre-receive`, `update`,
646`post-update`, and `post-receive`. This means you can define your own hooks to
647run on repository push events. Hooks can be defined as a per-repository hook,
648and/or global hooks that run for all repositories.
649
650You can find per-repository hooks under the repository `hooks` directory.
651
652Globs hooks can be found in your `SOFT_SERVE_DATA_PATH` directory under
653`hooks`. Defining global hooks is useful if you want to run CI/CD for example.
654
655Here's an example of sending a message after receiving a push event. Create an
656executable file `<data path>/hooks/update`:
657
658```sh
659#!/bin/sh
660#
661# An example hook script to echo information about the push
662# and send it to the client.
663
664refname="$1"
665oldrev="$2"
666newrev="$3"
667
668# Safety check
669if [ -z "$GIT_DIR" ]; then
670        echo "Don't run this script from the command line." >&2
671        echo " (if you want, you could supply GIT_DIR then run" >&2
672        echo "  $0 <ref> <oldrev> <newrev>)" >&2
673        exit 1
674fi
675
676if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then
677        echo "usage: $0 <ref> <oldrev> <newrev>" >&2
678        exit 1
679fi
680
681# Check types
682# if $newrev is 0000...0000, it's a commit to delete a ref.
683zero=$(git hash-object --stdin </dev/null | tr '[0-9a-f]' '0')
684if [ "$newrev" = "$zero" ]; then
685        newrev_type=delete
686else
687        newrev_type=$(git cat-file -t $newrev)
688fi
689
690echo "Hi from Soft Serve update hook!"
691echo
692echo "RefName: $refname"
693echo "Change Type: $newrev_type"
694echo "Old SHA1: $oldrev"
695echo "New SHA1: $newrev"
696
697exit 0
698```
699
700Now, you should get a message after pushing changes to any repository.
701
702## A note about RSA keys
703
704Unfortunately, due to a shortcoming in Go’s `x/crypto/ssh` package, Soft Serve
705does not currently support access via new SSH RSA keys: only the old SHA-1
706ones will work.
707
708Until we sort this out you’ll either need an SHA-1 RSA key or a key with
709another algorithm, e.g. Ed25519. Not sure what type of keys you have?
710You can check with the following:
711
712```sh
713$ find ~/.ssh/id_*.pub -exec ssh-keygen -l -f {} \;
714```
715
716If you’re curious about the inner workings of this problem have a look at:
717
718- https://github.com/golang/go/issues/37278
719- https://go-review.googlesource.com/c/crypto/+/220037
720- https://github.com/golang/crypto/pull/197
721
722## Feedback
723
724We’d love to hear your thoughts on this project. Feel free to drop us a note!
725
726- [Twitter](https://twitter.com/charmcli)
727- [The Fediverse](https://mastodon.social/@charmcli)
728- [Discord](https://charm.sh/chat)
729
730## License
731
732[MIT](https://github.com/charmbracelet/soft-serve/raw/main/LICENSE)
733
734---
735
736Part of [Charm](https://charm.sh).
737
738<a href="https://charm.sh/"><img alt="The Charm logo" src="https://stuff.charm.sh/charm-badge.jpg" width="400"></a>
739
740Charm热爱开源 • Charm loves open source