localias
piku
localias | piku | |
---|---|---|
4 | 27 | |
521 | 2,601 | |
- | 5.3% | |
6.2 | 6.7 | |
10 days ago | about 1 month ago | |
Go | Python | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
localias
-
You Can't Follow Me
I empathize with the author and found the post to be a interesting and concrete example of what it's _actually like_ to try to publish a blog to Mastodon, which is something that I have thought about and read about in abstract. So, thank you sir for writing this up.
One thing to consider would be to try to use Caddy [0], or a tool like localias [1], as a local https proxy. You might be able to run both the mastodon server and your blog software on the same computer and refer to local-only urls like "https://blog.test" and "https://mastodon.test" and have everything work.
I'd be curious to know why the author didn't try this, they seem to be quite knowledgeable of other web technologies so I have to assume there's a problem that I'm not seeing here.
[0] https://caddyserver.com/
[1] https://github.com/peterldowns/localias
-
Show HN: Local development with .local domains and HTTPS
Sure, but there are also excellent FOSS solutions for this, such as https://github.com/peterldowns/localias which has the benefit of being cross-platform.
-
Free and open source software projects are in transition
Pretty good overview from Baldur — I don't always agree with everything he writes but this seems relatively correct.
One question I'd ask him (and anyone else reading) is: what are some other options for monetization?
Over the last few weeks I had three different VCs reach out to me about some of the open source projects I've been releasing, and ask me if I'd thought about making a business out of them. I told them that no, based on the problem the software was solving, I didn't see how I could adopt open-core or companion-saas business models, and I wasn't sure how else it could be done while keeping the code open source.
Can anyone suggest a viable business model that would allow:
* Code remains at least source available, ideally open source for non-commercial use.
* I can charge for commercial use.
* Actually doing the licensing is reasonable, ie no spyware or phoning home from the tool.
Wouldn't need to be perfect, I understand that if the code is open source a company could easily fork and use it without paying me. The idea would be to make it zero-headache to pay me for a license if the code is being used by a funded team.
The projects:
* https://github.com/peterldowns/localias
* https://github.com/peterldowns/pgmigrate
- Show HN: Localias, securely manage local devserver aliases
piku
-
Open-source alternative to Heroku, Vercel, and Netlify
I should add one to https://piku.github.io (spoiler - this doesn't use Docker at all)
-
Show HN: Hancho – A simple and pleasant build system in ~500 lines of Python
I like it. I wrote Piku (https://github.com/piku/piku) with much the same interest in fixing some of my pains, so I get where you're coming from with this. Will drop it into one of my current projects to build ESP32 binaries :)
-
Gokrazy Is Cool
I never had any serious issue with SD cards since the Pi 2B (and I've kept Pis running for years).
Anyway, for those wanting to deploy more generic apps, that is why I initially wrote https://github.com/piku/piku - you still have to flash the OS (and rpi-imager does that with sane defaults these days), but once you're done you have Heroku-like deployments for any language runtime you install on the Pi.
I also have https://github.com/rcarmo/ground-init, a cloud-init like shim that simplifies setting up machines (I'm a big fan of cloud-init, but since Raspbian doesn't support it and Ubuntu on ARM requires some fiddling to make it work I decided it wasn't too hard to roll my own).
(I probably should look into glueing that into rpi-imager, but there is are only so many hours in the day...)
-
Show HN: Local development with .local domains and HTTPS
I automated that away a long time ago: https://github.com/piku/piku/blob/master/piku.py#L814
-
Tool to deploy docker images from github repos?
Piku https://github.com/piku/piku
-
Stupid question: Why not use 'baremetal' OS instead of docker containers to run web apps?
So, stupid question: why couldn't I just use the 'baremetal' OS provided by Hetzner, install Postgres, Redis & node, create a separate db for each app, and run each app with https://github.com/piku/piku on a different port? For backups, I'll setup crontab to dump dbs locally and to S3.
-
Selfhosted PaaS? (No dokku pls)
piku?
- How do you deploy your side-projects?
- Ask HN: What's Your Proudest Hack?
- Piku
What are some alternatives?
puma-dev - A tool to manage rack apps in development with puma
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
goffy - A command-line tool for downloading public playlists, albums and individual tracks via Spotify URLs.
RaspberryPi-Note - Raspberry Pi note
overmind - Process manager for Procfile-based applications and tmux
awesome-home-kubernetes - ⚠️ Deprecated: Awesome projects involving running Kubernetes at home
go-camo - A secure image proxy server
awesome-paas - A curated list of PaaS, developer platforms, Self hosted PaaS, Cloud IDEs and ADNs.
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
flyctl - Command line tools for fly.io services
jkt48-showroom-cli - JKT48 Showroom CLI - A lightning-fast and lightweight CLI tool to access real-time information and live streams of JKT48 members on Showroom
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).