puma-dev VS localias

Puma-dev: A fast, zero-config development server for macOS and Linux - https://github.com/puma/puma-dev

Developing a rails application with subdomains is much more difficult on Linux than on MacOS. On Mac it requires nothing more than installing puma-dev and following the installation guide, which also covers linux but we don't understand why that works, or how, and so we close our minds to whats beyond that rabbit hole.

Check out puma-dev. It's intended to be a successor of sorts.

you can also use them with puma-dev

You develop using this approach by running the bundler in watch mode in a terminal with yarn build:css --watch (and your Rails server in another, if you're not using something like puma-dev). Whenever the bundler detects changes to any of the stylesheet files in your project, it'll bundle app/assets/stylesheets/application.[bundler].css into app/assets/builds/application.css. This build output takes over from the regular asset pipeline default file. So you continue to refer…

I will describe the installation for macOS, for Linux you can use https://github.com/puma/puma-dev#linux-support.

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

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.

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