Accessing filesystem of one service through another

Hi, I have two services A and B. I want to access and modify the filesystem in Service A through Service B. How do I accomplish this? Essentially this: 1. curl -X post serviceb.url/write-files 2. Files in Service A are modified 3. Profit
16 Replies
Percy
Percy2w ago
Project ID: N/A
Samuel Barnholdt
Samuel BarnholdtOP2w ago
N/A
Brody
Brody2w ago
you would need to build that functionality into your code
Samuel Barnholdt
Samuel BarnholdtOP2w ago
Can I somehow colocate A and B on the same machine? I won't have access to the code inside A
Brody
Brody2w ago
yeah you could, but that comes with its own set of challenges
Samuel Barnholdt
Samuel BarnholdtOP2w ago
happy to take those on if I have to - unless you think there is a smarter way to accomplish this essentially I want to run someones npm run dev -> embed it through an iframe -> modify code over API
Brody
Brody2w ago
that sounds like a security nightmare
Samuel Barnholdt
Samuel BarnholdtOP2w ago
live and die by the sword I guess
Brody
Brody2w ago
why run a development server anyway? that's costly and comes with its own issues
Samuel Barnholdt
Samuel BarnholdtOP2w ago
I'm trying to do dev environments for customers and want hot reload enabled prompt to modify code stuff but with your actual code
Brody
Brody2w ago
respectfully, I think you need to rethink this project, specifically so that you can easily run it on railway
Samuel Barnholdt
Samuel BarnholdtOP2w ago
As in this will be death to run on railway?
Brody
Brody2w ago
railway or anywhere
Samuel Barnholdt
Samuel BarnholdtOP2w ago
I mean it's obv not ideal but is really that bad apart from it being a hassle and costly running dev?
Brody
Brody2w ago
it's more than that, from my perspective it seems like the project is chalked full of bad practices.
RyanKnack
RyanKnack2w ago
Lol this is exactly what I did in one of my projects just because Railway doesn't support shared volumes. I have service A running as an API server that is only exposed to the PRIVATE network within Railway, which itself modifies its own volume contents. Service B literally just calls service A through the private network and passes in any files or whatever configuration to B's API and modify it from there. Service A is also exposed to the PUBLIC network through another PORT (since Railway now supports exposing multiple ports) and is read-only.
Want results from more Discord servers?
Add your server