goffy
localias
goffy | localias | |
---|---|---|
1 | 4 | |
19 | 521 | |
- | - | |
8.2 | 6.2 | |
about 1 month ago | 7 days ago | |
Go | Go | |
GNU General Public License v3.0 only | 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.
goffy
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
What are some alternatives?
f-license - Open Source License Key Generation and Verification Tool written in Go
puma-dev - A tool to manage rack apps in development with puma
commando - An easy-to-use command-line application builder.
overmind - Process manager for Procfile-based applications and tmux
wifiqr - Create a QR code with your Wi-Fi login details
go-camo - A secure image proxy server
gojq - Pure Go implementation of jq
mkcert - A simple zero-config tool to make locally trusted development certificates with any names you'd like.
mob - Tool for smooth git handover.
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
gnt - Quickly create your Go project in your favorite terminal with `gnt`.
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.