yourBackend - time for a rebrand!
An important lesson in being rigid about staying flexible, our previously announced name for this module is making people think its unneeded.
It seems I have missed a trick with branding! After meditating a lot on this, and meeting with a few people about it, I have decided to change the name of our First Champion Module from yourFrontend to yourBackend.
If anything, it might make people pay attention a bit more - after all we seem to have a lot of front-ends around HIVE - but how many backends do we have? The only one I know about it @buttcoins.
So let's try to grok it together. Stop looking at the front end. Yes we could have spent 15 hours stripping down someone elses javascript code. Instead we spend 7 hours putting together exacly the ENV vars we needed for:
yourBackend
You can fork it!
Yes of course I am promoting open source, but wordpress does not require repository forking or code editing. It is also not built entirely of javascript, I should mention. It has a LAMP stack. You can decide where you think HIVE fits into the LAMP, but does it really matter?
I asked @thecrazygm to explain what it is he did, to make the "yourFrontend" page feature, rapidly and efficiently created by @mirafun, actually become the click-to-deploy yourBackend that I am trying to show you. Let's read it together because I could only manage to jumble together words about caddy and api configs.
Scope dump
Configuration Management
To streamline the configuration of yourBackend, we've developed a Flask application that provides access to user settings stored in MongoDB through a fast, straightforward API.
Each instance we deploy is a complete, self-contained git clone of the repository with full configuration capabilities. This architecture allows for efficient management through API calls while maintaining flexibility.
As an open-source project, YourBackEnd can be configured without using our API service. Users can either edit the settings file manually or utilize the included configuration builder application.
All instances are served using Caddy, which simplifies deployment with automatic SSL/TLS certificate management. Caddy can be configured without directly editing the Caddyfile. We have plans to further automate the provisioning system for the instances we host.
What it is not
Its not a wallet, you can't find your friends, you can't write a snap or a post. No one can use your domain to randomly append to the url and find someone elses content on HIVE.
It would be quite unprofessionally for a corporate domain to accidentally show something on someone else's post wouldn't it? yourFrontend yourBackend give you CONTROL! over what is seen. Without forking anybody, especially not the hardworking teams building out important frontend options for our HIVE chain.
Acknowledgements
Special Thanks to @mengao - beloved builder of the SkateHive frontend, for helping me work this out. SkateHive frontend "mycommunity" is very interesting, its a stripped down version of ecency designed to fit into vercel. Lowkey: Brilliant idea. I have sent him a bounty of 5 HBD:
And also, thanks to @adesojisouljay - savvy developer of the Breakaway communities. This one is a little bigger, 521mb for the base instance last we checked, but they have now integrated deployment with docker (!!!)
Sidebar: I didn't mention in our official DHF support staff list, but @kit.andres is my docker guy. He keeps busy nowadays dockerizing processes for big companies around latin america, but I onboarded him in 2018 to work with me on @coffeesource.net and he was also the one I tapped to help @josephsavage build the https://www.hivesbi.com and api.
If I needed help Redhat-ing a docker process, I would call him first.
I think both of these frontends have great and powerful use cases. I am fascinated by the idea of offering a B2B Microservice for both, they are different.
Imma be there
I see what is being built. I like these people, and I consider that their work is not in vein - I see (great and powerful) usecases for both frontends mentioned above. I hope to consider every builder on HIVE a friend - but I definitely know them to be allies.
And something tells me, they are going to be reaching out to me when the first customer says "lol wut? you want me to fork what?"
HIVE needs a Redhat hero!
So once again I am asking for your scathing criticisms. 5 HBD bounty for the first one that gets me the Bernie.gif with this amended text okok.
Simplest Vision - RedHat of HIVE
Champion Modules
Vote my proposal Bro
If you are having lots of fun along with us, don't forget to click that @synergy.witness - We are 88!! 😍 What a lucky number!
Refocusing on the backend is a good choice Mr Eco. Frontend solutions get plenty of attention, but having more control over deployment and configuration fills a real gap in the ecosystem. Wish you the best in this one
Its not a refocus this is literally the thing
Love You
well noted man 👍
I think i understand, refocusing my "marketing"/explaining efforts. And you nailed it.
Btw i have found your comments valuable! Thanks for caring
you're most welcome Mr Eco, glad you got me 💯💯🥰🥰🥰
Clearly there needs to be a rebrand of the rebrand … myButtend
The logo spells it out very velumptiously
😍
This is hilarious and brings me nothing but joy to see development taking its course. YourBackEnd is a glorious rebrand that is sure to catch eyes. WenMoon???
!PIZZA
Ahoy!
I don't recall seeing a link to a demo of your back end configurability system - is there one available?
The comments made by both @starkerz and I about the scope clash between this project and Ecency / Breakaway Communities are based on both projects seeking to fill a gap between Hive and requirements for customised Hive installations. Both projects result in a customisable front (and back) end, plus open source editability. However, Ecency is already funded to expand on this and their feature set is pretty large in comparison. So I'm still not seeing why you don't see an issue with funding two projects that are aiming at the same target and where the one that is already funded is way, way ahead already.
As Matt already pointed out, it makes sense for people who want to achieve this goal for Hive to join forces with Ecency and to make that code the best it can be. My own view on what I've seen of deployment of the previous versions of their breakaway communities is that it can be extremely powerful but is really lacking great customisation of the back end - which is now what you are selling your poject as.. So, to me, the clash is made doubly relevant by viewing your project in this way.
I do understand that Ecency's funding is theirs and isn't automatically going to go to you - so I don't have a straightforward solution - other than that it would be good if @good-karma would comment on this (if he hasn't already and I have missed it) and if we can somehow rejig this situation so that everyone gets what they need and progress for Hive is expanded.
@breakaway-dev should also suggest ways that My Front End team can contribute to adding customisability to Ecency breakaway communitiy front ends
@breakaway-dev please share links to github issues! We can meet as well, please link @ecotheexploiter account so I get the pings.
There are no links to any demos, because there are no demos. Its a live redhat service, you can see https://content.hsbi.com for validated use case.
This site helps @steembasicincome monitor vote delivery and check for spam or abuse, monitor program flow, and possibly identify users who need extra love.
Since this module is essentially complete, we will likely remove it from the proposal tomorrow to focus on the other modules, which still require more attention.
$PIZZA slices delivered:
@danzocal(9/10) tipped @ecoinstant
Moon is coming