Use pinafore as frontend for social.data.coop #126
Labels
No labels
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: data.coop/ansible#126
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It might be worth trying out pinafore as a front-end on a different domain.
I'm all for it! Although I would say that we should keep
social.data.coop
as mastodon and maybe dopinafore.data.coop
for our own installation of pinafore.What if we put it up for evaluation / testing?
So instead of running it at a URL that says "here is a permanent service", we nest it somewhere like pinafore.testing.data.coop ?
I like that! Maybe a good idea to have
testing.data.coop
as a general testing-subdomain as well, for when we wan't to test other services in the future?I think I like it better after a second thought.
We have a whole "service" catalog with badges and perhaps even more democratic governance around the decisions of why and how to run a service.
So we could make processes for adding services that are like:
Set up the demo/testing ground => Run a trial where people get some familiarity => Write a proposal with everyone => Decide if we want it permanently in the "catalog"
*) I didn't know what to use in place of "catalog", there must be something more fun and less corporate.
I think that's a great idea!
I set pinafore up on pinafore.data.coop - I had forgot about this suggestion. As pinafore heavily uses indexeddb on the client it's not obvious to me how you can migrate pinafore to a different domain without losing stored credentials etc.
Would you be okay with keeping it at pinafore.data.coop? I've already started using it a lot with three accounts.
I will definitely keep in mind to use *.testing.data.coop next time.
@reynir it's no big deal :) maybe you pina-forgot it? :D
We have already added extentions in different ways that are most likely because we should try to come up with a simple procedure that we can follow.
Pinafore has been added. Closing this.