saasform
hotwire-rails
Our great sponsors
saasform | hotwire-rails | |
---|---|---|
16 | 98 | |
271 | 960 | |
- | - | |
0.0 | 3.2 | |
over 1 year ago | over 2 years ago | |
JavaScript | Ruby | |
Apache License 2.0 | 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.
saasform
-
Ask HN: What are your successful open source projects you lost interest in?
Saasform: https://github.com/saasform/saasform
I had to prioritize another project (solokeys).
I still really believe both: 1) in an open source alternative to auth0, 2) in combining auth+payments for saas.
However, because they’re two problems, it’s probably best to focus on just one. For me trying to launch Saasform the issue has been to find and onboard customers quickly and at scale.
-
Ask HN: How to build a good looking SaaS landing page?
I also purchased Landkit, but eventually found it very heavy. I then essentially remade it on top of Fresh [1]. Code is here if anyone needs it [2].
[1] https://github.com/cssninjaStudio/fresh
[2] https://github.com/saasform/saasform/tree/main/data/themes/f...
-
Ask HN: No / low-code tools to build an application in 2021?
If it's a web saas, we're building Saasform [1] with your use case in mind.
One relevant example is launching your MVP as a serverless API (e.g. on Firebase) + react/vue front end. Just iterate on your core product and features, we handle home page, registration and payments.
For mobile apps I'd recommend Expo [2] and, if you can, stay with their managed flow. If you want to iterate fast, you need to take into account the time to release to the stores and Expo can help with that. Similarly as for the web, I'd look into a serverless API model to start.
For email notifications I'd go with Sendgrid.
I personally never used no-code solutions but different people recommended Bubbles [3].
[1] https://saasform.dev
[2] https://expo.io
[3] https://www.bubbles.io
- A more secure express-session package
- Show HN: Drop-in replacement of express-session to enhance security
-
Ask HN: What is your current side-project?
Starter kit to "transform your project into a SaaS", with auth+payments.
https://github.com/saasform/saasform
- Show HN: We made a starter kit for SaaS (microservice instead of boilerplate)
-
Authentication best practices and state of the art for a junior dev?
Saasform: shameless plug, this is my project, modern (at lease I hope), written in typescript
-
I made an authentication server that handles user registration, authentication & authorization with JWT.
We are also doing something like that lol. It's a crowded field I see. Of course any cross contamination of PR is more than welcome :-)
-
Show HN: Checklist/exercise to make a SaaS marketing page
I made this exercise to guide myself throught the process of starting from a list of features, summarizing benefits, prioritize them, sparkle some keywords and finally output a marketing page.
Working to make a marketing/public site for a micro-saas I was building, I realized there's plenty of articles about the structure of the landing page, sticky header, include quotes, etc. but there's little on how to actually write the content. I worked w/ different marketing professionals in the past and, though everyone has their own style/processes, the tldr is "talk about benefits, not features".
If you're making a marketing page, I hope you can find it useful too!
Please lmk if 1) the exercise makes sense to you, 2) the format is clear/unclear - what can be improved, 3) should I maybe write an accompanying blog post? other ideas?
For context, I expect to launch a number of micro-saas in the next months, so I wanted to build a repeatable process. I then plan to run all these sites out of config files like this [1].
[1] https://github.com/saasform/saasform/blob/main/data/config/w...
hotwire-rails
- It's not Ruby that's slow, it's your database
- Howire Not Working after deploying to Heroku
-
What's New in Rails 7
Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.
-
Ask HN: What tech stack would you use to build a new web app today?
For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."
https://htmx.org/
https://hotwired.dev/
- Ask HN: Do we need JavaScript web frameworks?
-
anyone have full tutorial how to upgrade from rails 6.1 to rails 7 ?
For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).
-
Ask HN: What are you favorite goto frameworks when writing Web Aplications
I was recently interested in similar topic. Here are 3 similar solutions I found:
* https://htmx.org/
* https://unpoly.com/
* https://hotwired.dev/
My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:
* https://htmx.org/essays/hateoas/
* https://htmx.org/essays/locality-of-behaviour/
-
Hotwire isn't only for Rails
At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.
-
How do you handle views?
I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).
- Why learn Rails as a frontender?
What are some alternatives?
openmiko - Open source firmware for Ingenic T20 based devices such as WyzeCam V2, Xiaomi Xiaofang 1S, iSmartAlarm's Spot+ and others.
htmx - </> htmx - high power tools for HTML
SuperTokens Community - Open source alternative to Auth0 / Firebase Auth / AWS Cognito
SvelteKit - web development, streamlined
okta-aws-cli-assume-role - Okta AWS CLI Assume Role Tool
Alpine.js - A rugged, minimal framework for composing JavaScript behavior in your markup.
Svelte - Cybernetically enhanced web apps
Tailwind CSS - A utility-first CSS framework for rapid UI development.
phoenix_live_view - Rich, real-time user experiences with server-rendered HTML
exomind - A personal knowledge management tool hosted on your own personal cloud
inertia-laravel - The Laravel adapter for Inertia.js.