-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE][Feedback needed] Use alovoa-expo as official frontend for the web #284
Comments
Please do not submit or request new GUI features and translations to this repository, but here alovoa-expo until further notice. This only applies to pages only accessible when logged in. |
Is a headless server branch planned? If Alovoa-Expo should be used as only frontend, Alovoa server needs REST frontend, only. |
@ip6li No headless only server is planned. Only the user area will be removed. Simple static pages like FAQ, contact, index and the admin area will still be available from the web. Progess of this issue is being made on staging branch |
Hmm, I may have a different opinion regarding architecture, because I would consider a more microservice like architecture. My reverse proxy instances in front of my Alovoa instances can redirect static files to static only Nginx instances, which is optimized for caching support by a CDN (e.g. Cloudflare, free edition). Nginx is much faster than a Tomcat based Java solution. |
New frontend launched on beta.alovoa.com! If you encounter bugs or missing features, please report them here: https://github.com/Alovoa/alovoa-expo/issues |
Merged PR: 8ff8757 |
EDIT: Feedback needed! Visit beta.alovoa.com to try out the new web frontend!
No need to maintain 2 separate frontends, as expo/react-native official supports building for the web.
The text was updated successfully, but these errors were encountered: