-
Notifications
You must be signed in to change notification settings - Fork 48
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
Release v2.0.0 #43
Comments
Will this also be included in the Docker container release via 'docker compose'? Asking since my setup uses Portainer with the related 'Docker compose' file. |
What are the planned developments regarding the save manager? |
Wow, it looks great. I'm looking forward to try it. Do you have a test version for docker? I could be a tester if you want. Cheer up with the project. |
Could you generate a docker container to test the 2.0 version? Thank you very much for your time and project. |
@SamuelBanya @SiscuPrats Docker image for testing v2 is available, see the issue description. @CortezSMz The save manager implementation will come later, I need to implement separate permission for each user (Shop Access, Library Access, Backup Access, Admin), then a profile page for users who can manage backups, then auto discovery of Switch device and linking it to a user... This means lots of development in the backend and fronted. |
Ownfoil v2 is a complete rewrite of the project, using a web framework that allows much more flexibility. Instead of generating a static shop file (custom .tfl index) and serving it with Nginx, the shop is now directly served with an HTTP API when Tinfoil connects. It is far from completed, but should address all the main issues with the current implementation. It's available in the
v2
branch.The main advantages of the v2 are:
Roadmap to release
In no particular order, things left to do before releasing Ownfoil v2:
/config/settings.yaml
Setup
page to guide users on how to access the shop on Tinfoil, DBI... (http adress, port, auth...)How to test
To report issues and/or discuss about v2, see the discussion: #52
Use v2 tag, built every commit pushed to the v2 branch:
The text was updated successfully, but these errors were encountered: