podverse / podverse-ops Goto Github PK

Mac

The podverse-ops repo is intended to help you run or deploy all apps from all Podverse repos. Basically if you wanted to deploy your own forked version of any/all of the Podverse apps, you would use the podverse-ops repo.

We need to update our documentation to make it easier for people to deploy Podverse apps. It would be a huge help if we can work with someone who doesn't already have podverse-ops running on their computer (or server), so we can go from a clean slate to up-and-running with podverse-ops, and document the steps we take along the way.

If you are interested in contributing to Podverse, and have at least some experience setting up a JavaScript dev environment, this could be a great way to get started with the Podverse code base. I'm happy to do a screen share with you over Discord if you would like, to walk you through the setup process and update the documentation as we go.

Please feel free to join our Discord and chat with us in the #dev channel if you'd like to work on this.

The current screenshots on the stores don't include a boostagram or streaming sats example.

When running docker-compose up for the podverse-web container, I ran into failures during the npm run build step that did not happen when I ran npm run build at the same commit in the podverse-web repo.

Specifically it was these props that were throwing the error when building through podverse-ops docker-compose process: podverse/podverse-web@2958411

But for some reason those props did not throw an error when running npm run bulid in the podverse-web repo.

There must be some kind of discrepancy between the build processes leading to this different outcome, but I don't have any ideas yet as to what could be the cause.

Linux

The podverse-ops repo is intended to help you run or deploy all apps from all Podverse repos. Basically if you wanted to deploy your own forked version of any/all of the Podverse apps, you would use the podverse-ops repo.

We need to update our documentation to make it easier for people to deploy Podverse apps. It would be a huge help if we can work with someone who doesn't already have podverse-ops running on their computer (or server), so we can go from a clean slate to up-and-running with podverse-ops, and document the steps we take along the way.

If you are interested in contributing to Podverse, and have at least some experience setting up a JavaScript dev environment, this could be a great way to get started with the Podverse code base. I'm happy to do a screen share with you over Discord if you would like, to walk you through the setup process and update the documentation as we go.

Please feel free to join our Discord and chat with us in the #dev channel if you'd like to work on this.

I haven't updated the Github descriptions in years...podverse-web still describes us as if we're just a podcast clipping app.

Windows

The podverse-ops repo is intended to help you run or deploy all apps from all Podverse repos. Basically if you wanted to deploy your own forked version of any/all of the Podverse apps, you would use the podverse-ops repo.

We need to update our documentation to make it easier for people to deploy Podverse apps. It would be a huge help if we can work with someone who doesn't already have podverse-ops running on their computer (or server), so we can go from a clean slate to up-and-running with podverse-ops, and document the steps we take along the way.

If you are interested in contributing to Podverse, and have at least some experience setting up a JavaScript dev environment, this could be a great way to get started with the Podverse code base. I'm happy to do a screen share with you over Discord if you would like, to walk you through the setup process and update the documentation as we go.

Please feel free to join our Discord and chat with us in the #dev channel if you'd like to work on this.

Upgrade to PG 16.2

We had emergency DB work last week and upgraded the db

Create alerts in VPS do notify of issues

The descriptions on our store listing are over a year old at this point, and don't highlight some of the major features we have added since then.

The current solution streams the data to gzip (with default level 6 compression) to a separate xfs block storage device.
The result is a fairly well compressed sql file; with about 90G of saving
The pv-db it took about 8 hours with the current solution

Looking around this might be a viable option https://serverfault.com/questions/1081642/postgresql-13-speed-up-pg-dump-to-5-minutes-instead-of-70-minutes

Also looking into adding the fast flag, streaming the data uncompressed to the volume and then compressing, or moving over to something like zstd

Rebuild Web/API server

Identify what is needed to make server work
Determine where the gaps are
Discuss improvements like Jenkins for coordination
Review droplet size

Rebuild API Worker server

Identify what is needed to make server work
Determine where the gaps are
Discuss improvements like Jenkins for coordination

Is your feature request related to a problem? Please describe.
We are seeing issues with PG around wait times to access data

Describe the solution you'd like
Bumping the point version of PG might help with the access and get Podverse to supported version of PG

Describe alternatives you've considered
Jumping to PG 14, but that will take a migration step and more work.