eGeoffrey forum migration and other upcoming changes

[user2684]

[This post has been migrated from the old forum, it was originally sent by user2684 on 2022-04-03 11:41:24]

Dear eGeoffrey users and developers,

In the upcoming days and weeks a few changes will be applied to the eGeoffrey ecosystem. Please note that none of them will be impacting the eGeoffrey software per-se, but only the supporting services, with the aim of consolidating them towards well-known, public services so to move away from a self-hosted logic which is not very reliable and challenging to maintain:

• The forum will be moved to the Github Discussions service, which provides the same level capabilities and more. This will allow keeping closer our interactions with the development tools and leverage a more solid and high available service like Github. At the time of migration, every topic and post will be migrated to the new platform automatically so the historical interactions will not get lost. The forum will still be accessible from the url https://forum.egeoffrey.com but the path of the topics and the authentication will be based on those from Github (yes, you will need a Github account but I guess most of you already have one). Once live, to receive again email notifications you will need to "Watch" the repository which will be hosting the forum since notification settings cannot be migrated, being GitHub based on a different users base.
• The demo website will be terminated since it has a high cost of operation and it is not heavily used. Also because users willing to test eGeoffrey simply needs to run a single command to setup their own environment.
• The Cloud Gateway service will be suspended since requires a resource-intensive workload to be maintained and is used sporadically by very few users. The documentation will be updated accordingly and alternative ways for accessing eGeoffrey when not at home will be provided.
• Static websites will be moved to GitHub, such as the documentation, developer, marketplace etc. will be moved out of the self-hosted logic towards GitHub Pages service. This change will be completely transparent to the end user and the associated URLs will not change.
• Mobile notifications will keep running for now and the situation will be re-evaluated in a few months. As of today very few users have the service configured.

Thanks for using eGeoffrey and for your understanding!