What is the state of this app ?
gnouts opened this issue · 12 comments
Hi,
I am interested by glitch-soc app, but there is a WIP in the readme. What should I expect from this package ?
Tell me if I'm wrong, but if glitch-soc is a fork of mastodon relatively stable and the package mastodon_ynh is a stable and well integrated (LDAP and all) package, then glithc-soc_ynh should be stable enough for production.
What's missing in this package to be ranked at level7 on the yunohost scale ?
🆙 I'm interested too :)
What's the status of this package, and its relationship with https://github.com/YunoHost-Apps/mastodon_ynh ?
As both apps are very similar, could that package benefit from the work on Mastodon package ? Then I guess only a few glitch-soc specific updates would be needed (update to latest commit for instance).
ping @yalh76
Idk but don't plan to work on it ^^
That's fine :)
🤔 I believe that working on a glitch-soc package could be done by reusing your work on Mastodon package, and "just" updating the source code and package version… which would create zero extra work for you and little work for this package.
@Tagadda what do you think about that ?
edit : I realize I did already talk about this here : YunoHost-Apps/mastodon_ynh#146
@lapineige Yep, that's what I've done last year but I couldn't make it work at this time and I decided to wait for YunoHost 4.
I think forking again https://github.com/YunoHost-Apps/mastodon_ynh again is a good idea too, lots happens since last commit.
YunoHost-Apps/mastodon_ynh#264 seems to be a cool branch to fork, let's wait until test is done 👀
I can give you some help if needed :) (with limited knowledge and no server to test it 😅)
@lapineige I did some text search and replace yesterday, you can look at it on this branch https://github.com/YunoHost-Apps/glitch-soc_ynh/tree/rebase and this commit 5fe7264
The thing install but I've got an issue with assets not loading, but this could come from my testing environment so... I don't know yet ^^
I did test an install on a server that a friend kindly lent for the test: same issue.
I'll wait until the upstream PR is merged, rebase and test again.
Upstream seems to be good now!
I did rebased again and the port is here 43184e1
Installs and run great!
Only one issue remain : when you log in, you get an HTTP 422 Error and the page says "Vérification de sécurité échouée. Bloquez-vous les cookies ?", but you're logged in successfully anyway, you just have to go to /web/timelines/home
ignoring the error page
I really have no clue
I'll give it a look, but I'm unsure that I will have any clue about that…
The app installs now so I guess. I merged to master since the app was totally broken before.