tangled.org
engineering blog at https://blog.tangled.sh
minor rewording
anirudh.fi
+16
-15
+8
-8
flake.nix
+8
-8
flake.nix
···
63
''}/bin/vite-build";
64
cwd = ./.;
65
};
66
-
deploy = {
67
-
type = "app";
68
-
program = "${pkgs.writeShellScriptBin "s3-sync" ''
69
-
#!/usr/bin/env bash
70
-
${vite.packages.${system}.vite}/bin/vite build
71
-
${pkgs.awscli2}/bin/aws s3 sync build s3://site/ --size-only
72
-
''}/bin/s3-sync";
73
-
};
74
serve = {
75
type = "app";
76
program = "${pkgs.writeShellScriptBin "vite-serve" ''
···
87
${vite.packages.${system}.vite}/bin/vite serve &
88
find pages/ static/ templates/ | ${pkgs.entr}/bin/entr ${vite.packages.${system}.vite}/bin/vite build --drafts
89
''}/bin/vite-serve";
90
};
91
}
92
);
···
63
''}/bin/vite-build";
64
cwd = ./.;
65
};
66
serve = {
67
type = "app";
68
program = "${pkgs.writeShellScriptBin "vite-serve" ''
···
79
${vite.packages.${system}.vite}/bin/vite serve &
80
find pages/ static/ templates/ | ${pkgs.entr}/bin/entr ${vite.packages.${system}.vite}/bin/vite build --drafts
81
''}/bin/vite-serve";
82
+
};
83
+
deploy = {
84
+
type = "app";
85
+
program = "${pkgs.writeShellScriptBin "deploy" ''
86
+
#!/usr/bin/env bash
87
+
${vite.packages.${system}.vite}/bin/vite build
88
+
${pkgs.wrangler}/bin/wrangler pages deploy --project-name tangled-blog ./build
89
+
''}/bin/deploy";
90
};
91
}
92
);
+8
-7
pages/blog/intro.md
+8
-7
pages/blog/intro.md
···
22
23
24
25
-
Our addition to this model is the idea of "knots". Knots are
26
-
lightweight, headless servers that enable users to host git repositories
27
-
with ease. Knots are designed for either single or multi-tenant use
28
-
which is perfect for "community" servers. By default, Tangled provides
29
-
managed knots where you can host your repositories for free.
30
31
The [App View][appview] at [tangled.sh](https://tangled.sh) acts as a
32
consolidated "view" into the whole network, allowing users to access,
···
34
completely seamlessly.
35
36
Tangled is still in its infancy, and we're building out several of its
37
-
core features as we [dogfood it ourselves][dogfood]. We developed these three core
38
-
tenets to guide our decisions:
39
40
1. Ownership of data
41
2. Low barrier to entry
···
22
23
24
25
+
Our approach to this is the idea of "knots". Knots are lightweight,
26
+
headless servers that enable users to host Git repositories with ease.
27
+
Knots are designed for either single or multi-tenant use which is
28
+
perfect for self-hosting on a Raspberry Pi at home, or larger
29
+
"community" servers. By default, Tangled provides managed knots where
30
+
you can host your repositories for free.
31
32
The [App View][appview] at [tangled.sh](https://tangled.sh) acts as a
33
consolidated "view" into the whole network, allowing users to access,
···
35
completely seamlessly.
36
37
Tangled is still in its infancy, and we're building out several of its
38
+
core features as we [dogfood it ourselves][dogfood]. We developed these
39
+
three tenets to guide our decisions:
40
41
1. Ownership of data
42
2. Low barrier to entry