Shouldn't the readme first explain what this project is about? How would I know if this is relevant for me/my work. Not trying to be obtuse, I am fairly new to CS and I would like to understand what I am looking at and how I could use it in future.
Spent a little time poking around to see what this is...<p>It's a bare-bones hosting service with a limited free tier (25MB asset storage), and a cheap premium tier (10GB asset storage for $2/month).<p>The big selling point is this:<p><i>"The secret ingredient to all our pico services is how we let users publish changes to their sites without needing to install anything. We accomplish this with what is colloquially termed SSH Apps. By using the SSH protocol and golang's implementation of SSH, we can create golang binaries that interface with SSH in unique ways."</i><p>They offer these pre-built services + client side tools<p>- static hosting (pgs.sh for normal static hosting, prose.sh adds blog platform)<p>- expose your local/home webserver to the internet (tuns.sh)<p>- private docker registry (imgs.sh)<p>- private pastebin like service (pastes.sh)<p>- rss client, pulls rss feeds, sends email notifications (feeds.sh)<p>There's also a labs area with some experimental services, and it feels like you may also be able to roll your own stuff that uses the base pieces.
I think the main thing here is <a href="https://pico.sh/pgs" rel="nofollow">https://pico.sh/pgs</a> which works well as a landing page - it's a static site host that you push files to using rsync and can manage using ssh. Gives the impression someone built this for themselves and then rolled it out to the general public. At least, the subset of it that isn't overly frightened of a terminal.
> <i>To get started, simply SSH to our CMS.</i><p>pico.sh is a content management system (CMS) for hackers.<p>That's what I infer from the site, but it would be helpful if they added a one-liner to the home page and repo.
should really link to <a href="http://pico.sh" rel="nofollow">http://pico.sh</a> which has a better landing page for this project and what it can do
The GitHub page (and frankly, to a degree also the landing pages) do not explain very well why the project is so great.<p>Basically, pico.sh is a collection of minimal web services that you control via SSH. Since it uses your SSH key as identifier, there is no registration process needed. For instance, setting up a blog with prose.sh[^1] took me less than a minute.<p>There is no real GUI, you manage everything via the terminal. Since publishing stuff is just running a one-liner in shell,[^2] it is very simple to automate/customize stuff. Copied the one-liner into the shell commands plugin for Obsidian, and I was able to publish notes from Obsidian to my prose.sh blog with one hotkey.<p>[1]: here as a showcase mine: <a href="https://nanotipsforvim.prose.sh/" rel="nofollow">https://nanotipsforvim.prose.sh/</a><p>[2]: <a href="https://pico.sh/prose#publish-your-posts-with-one-command" rel="nofollow">https://pico.sh/prose#publish-your-posts-with-one-command</a>
Looks a bit like a competitor to <a href="http://omg.lol" rel="nofollow">http://omg.lol</a> ? Just missing a Mastodon instance and a URL shortener.
Hey all, co-creator of pico.sh. We are reading your feedback loud and clear: we need to improve our messaging around what pico.sh offers.<p>I've updated the main repo README as well as the landing page. We will make it a priority to continue updating our docs.<p>Thanks for all the feedback!
I see that you guys do auth using ssh <a href="https://github.com/picosh/ptun">https://github.com/picosh/ptun</a> and generally use ssh identities heavily.<p>I think you might wanna consider providing a vault alternative that's based on ssh identities too. Here is my draft implementation of this idea <a href="https://taras.glek.net/post/github-to-sops-lighter-weight-secret-management/" rel="nofollow">https://taras.glek.net/post/github-to-sops-lighter-weight-se...</a><p>I wrote my crappy script in anger at how poorly passwords integrate with gitops workflows. It's just a matter of making a nice UX for this flow to make it useful. All the libs you need for this are already done in go.
Thanks for posting. There are many things down this rabbithole and I hadn't seen pico.sh before.<p>The github repo has the sources for the backend, but the services themselves are accessible over https at eg: pico.sh, prose.sh, pastes.sh, pgs.sh<p>Onboarding to the free stuff is easy by sshing with an existirng Identity to pico.sh, which creates subdomains for you at the various services above.<p>The central idea is to expose a whole bunch of simple services using SSH for auth and for tunneling, and occasionally rsync as a file-transport. While this may not be an efficient way to run high-traffic services, it's a great way to stand up simple back-of-house tools and I wish more people were doing things like this.<p>Love the aesthetic and the commitment to proving this out.
One description they provide for all of this is:<p>> <i>We think of pico.sh as a hacker lab where we can experiment with new ways to interact with the web.</i>
This project is terrible at telling, what it does.<p>At first I thought, this was some Pi Pico shell-stuff with a web-interface, but the site doesn't really tell.<p>It's proprietary in a way, tries to seem open sourcey?<p>Gives you a way to have a static website or blog hosted?<p>I am still not sure, what they do, but they have a plus-tier which requires you to ssh-forward the port 1337, so they are hackers at least...