saasform VS openmiko

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.

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...

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

Starter kit to "transform your project into a SaaS", with auth+payments.

https://github.com/saasform/saasform

Saasform: shameless plug, this is my project, modern (at lease I hope), written in typescript

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 :-)

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...

Have a Wyze Cam V2 running openmiko. I can pull the feed via the camera's IP, but Klipper (Fluidd, Mainsail on BTT CB1) shows like below. Additionally, moonraker-timelapse throws an error. This was working fine until I tried Hyperlapse. Now I can't wrap my head around this

I'm running MainsailOS, and a Wyze cam v2 running openmiko. I have Tailscale installed on the Pi for remote access. In Mainsail config, I have the camera configured via private IP. When I access the web control panel externally, I do not get video output. Is there a way to get this to work? I do not think there's a way to connect the Wyze cam to my tailnet.If it's not possible, have any good recommendations for a good, cheap, wide-angle (110 degrees FOV or better) camera I can purchase? I wouldn't want to spend more than $25 for one. Quick search yielded this one, but don't know if there's a Klipper-community recommended one that everyone uses.

you wish lol. the mod allows you to get highest possible resolution video out of it without all the compression pixelation. its super easy to install. but it does take a little bit of linux knowledge to edit config files and stuff. heres the link if interested: https://github.com/openmiko/openmiko

I bought a used Wyze Cam V2 relatively cheap and installed OpenMiko on it for example.

I have a WyzeCamV2 running OpenMiko firmware, which supports (and I have configured for) H264 RTSP streaming. I can view the video stream through VLC with the url rtsp://192.168.1.199:8554/video3_unicast. I am executing the command docker run -p 8081:80 --name mycamera -e AGENT_CAPTURE_IPCAMERA_RTSP="rtsp://192.168.1.199:8554/video3_unicast" kerberos/agent:latest on my host. The agent seems to run fine and I can connect via browser. With our without AGENT_CAPTURE_IPCAMERA_RTSP... set, I cannot add the RTSP stream; no cameras show attached and when I try to connect one via dashboard->settings, it just spins. The logs aren't really helpful (see below).

OpenMiko is one example.

That's why I only use cameras flashed with open firmware: https://github.com/openmiko/openmiko

If all else fails, you can flash different firmware and use them locally. I'm using [OpenMiko](https://github.com/openmiko/openmiko) on my Wyze Cam v1 (I'd assume there's a similar open-source project for the v3), and Wyze themselves publishes an RTSP firmware. Without a bit of technical know-how and some supporting hardware (namely a router than supports OpenVPN) you won't have access to the stream off your local network, but you can stream locally with VLC Player.