As of 1st July 2023 we no longer use our now legacy subdomain of 'shop' (https://shop.rockstor.com): a Shopify backed shop-front previously used to take financial contributions and, in-turn, via API polling from our Appliance ID manager 'Appman' (https://appman.rockstor.com), play a part in fulfilling Stable Update subscription memberships via activation code issuance via email.
We have now begun the process of enabling Appman's interoperability instead with our new Fiscal arrangements managed, in the open, by our newly established Open Collective:
https://opencollective.com/the-rockstor-project
See the following forum thread for context of this earlier-than-planned transition:
https://forum.rockstor.com/t/appman-rockstor-com-maintenance-open-collective-integration/8867
It is proposed that, in the context of the above, we establish a new landing page for those visiting shop.rockstor.com to explain the now differing arrangements regarding fiscal contributions - and differing requirements regarding activation code emails.
Our prior shop took Appliance ID entry via Web-UI or url 'applianceid' specification. This has yet to be established in our Open Collective Stable Updates subscription tier - but is believed to be possible via customFields and their consequent order values presented in order.customData. However this Open Collective counterpart has yet to be enabled on the front-end but is partially implemented in our Appman back-end. So for now we have implemented, within Appman, the ability to enter an initial Appliance ID on newly created (via WebHook initiated call backs from Open Collective) orders.
So we now have two Stable Updates subscription membership activation code receipt paths:
- Become a "Stable Updates subscription" member at Open Collective with NO Appliance ID entered:
- Email will be sent to the new member inviting then to enter their Appliance ID into Appman.
- Appman can then create the activation code, and send it.
- Become a "Stable Updates subscription" member at Open Collective WITH Appliance ID entered:
- Email will be sent to the new member with their activation code.
(2.) is akin to our prior arrangement - as detailed earlier - but we are currently developing 1. for overall flexibility and because we have yet to establish the associated tier customFields. There is also the potential for less friction/fuss when less elements are involved in any one step - even if further steps will ultimately include the otherwise complicating info: read Appliance ID requirement being dropped as an option in our Open Collective tier membership. However optional entry would be good for convenience renewal links and the like.