subscribie VS wave

Subscribie, payment automation for people who don't want to spend a lot of time setting up a subscription and website but want to collect subscriptions/recurring payments, automate bills and also charge ad-hoc on-demand.

https://github.com/Subscribie/subscribie/blob/1831a949a244c516e91f75e13cd6351966bbb151/subscribie/blueprints/admin/__init__.py#L1838

plus a more general thought dump on the topic: https://github.com/Subscribie/subscribie/issues/1

Step 1: To begin, on Subscribie.co.uk click Get Started and fill out some basic information and details for your subscription. Once you submit, your shop will be generated and you'll be redirected to your shop.

But if you want create a simple subscription website you can check out Subscribie It gives you a website that only deals with subscriptions and payments, it's nocode so you don't have to configure much, but it's only in the UK for now.

see https://github.com/Subscribie/subscribie

Wave - Open source and based on Laravel.

I knew it would require a membership management system, payment processor, etc, and despite thinking Wordpress is great for what it does and who it's for, I absolutely hate working in it with a passion. I also knew trying to build each of theses website functions (even with pre-made things to help) was going to take more time than I had to get going, so I ultimately ended up going with Wave, which is just a SaaS starter kit thing, built on(with?) Laravel that has everything I needed (membership manager, payment processor, db integration, etc). It's done really well.

Google for related frameworks. Maybe these will help set up things faster. For example, https://devdojo.com/wave is a free Laravel-based SaaS setup that takes care of users, login, admin, basic pages, blog, etc. You can install that and begin building on top of that. Maybe there is a similar solution for your tech stack.

I'm using a pre-built thing called Wave that uses Laravel, and a few other things like Voyager to have a functioning member-ready site. It works really well, but something about it does not seem to jive with Cloudways, and my only thought is that it could be something about the database configuration or something, but I have no clue. I tried a brand new Wave install just to test, and it still happens on all fresh everything.

Last question (sorry for asking so much) In the git instructions there are a couple of commands that say something about database migration, do you know if I will need to do these commands still if I'm running this db separately? I wasn't sure if this was only needed if it was going to be built into the app, or if this is also needed regardless. https://i.imgur.com/jJFGY0m.png Thank you again so much for being helpful. I'm still learning the basics and it's hugely beneficial.

Side note - we are using Wave as a template for our app which has helped us with most of the backend so far with payment + user authentication, etc.

Dev Dojo's Wave - https://devdojo.com/wave - a complete solution with user profiles and payments.

For those confused, I just want something like https://devdojo.com/wave but with support for Stripe or Paypal. It has to be free, I don't mind if I have to self-host.

4. Wave #