Seems like that’s the case, for now I’ve just got the tool downloading the video and audio, this app runs in docker containers so I’d have to setup the environment, and aspire has been giving me trouble doing so. Then, a tiny app on the host finds the two parts and merges them, temp fix

I’ve been playing around with that. Interesting thing is with .net aspire I can take the background task and convert it to use a dockerfile, that builds fine. But if I use the app host it will not build. It sees the file, but bugs out accessing the dependency projects. Might be a bug with aspire

Essentially I have a plugin that I’d like to use it in, and since it’s in a plugin I can’t setup the environment to install the library and dependencies. Might just be out of luck though, or need to change my structure a bit

Dotnet containers and all the bits of this are not new, but being able to orchestrate it and pull everything together simply, and make running locally for dev simple is really well done in aspire

I love how aspire lets you define a db, and it’ll create it in a container and share the connection string to all other containers consuming it automatically. This lets me move the app anywhere I need it, just spin up a new docker instance

Then, a download worker project checks the database, and sees if there’s a registered handler for that website. Handlers are added via dotnets plugin ability so you can develop a plugin, and drop the dll to a directory. Lets me keep things separate and if I ever release the code people can expand it

First component is a webapi, bound to local host but using a reverse proxy to give me a public endpoint with certs. The api simply has a post endpoint for urls so I can post from my phone using the shortcuts app on iOS. This puts the url in a database for the rest of the suite