I set up a @peertube instance! (personal use / experiments)
🥁 🎉 https://bengo.tube 📺
To try it out, I shared this old diving video of a bunch of Galapagos Garden Eeels[1] https://bengo.tube/w/wWccigJ46EWVaAm3aPQtRj
I set up a @peertube instance! (personal use / experiments)
🥁 🎉 https://bengo.tube 📺
To try it out, I shared this old diving video of a bunch of Galapagos Garden Eeels[1] https://bengo.tube/w/wWccigJ46EWVaAm3aPQtRj
Something is wrong with this Video. It has a https ID, but attributed to http actors:
"attributedTo": [ { "id": "http://bengo.tube/accounts/bengo", "type": "Person" }, { "id": "http://bengo.tube/video-channels/bengo.tube", "type": "Group" } ],@silverpill @peertube Thanks for the heads up! I learned @peertube keeps full URLs including schemes in its db. I think it must have set these to `http://` from before I enabled PEERTUBE_WEBSERVER_HTTPS?
I ran some manual sql queries and I think/hope it's fixed. 😅
```sql
UPDATE "actor"
SET "url" = REPLACE("url", 'http://', 'https://')
WHERE "url" LIKE 'http://%';
```
(and for other columns too)
@bengo It's working, thanks
@silverpill @bengo Prefer https://docs.joinpeertube.org/maintain/tools#update-peertube-instance-domain-name to update internal PeerTube URLs :)
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.