Accessing filesystem of one service through another
samuelbarnholdt
TRIALOP

a year ago

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

17 Replies

samuelbarnholdt
TRIALOP

a year ago

N/A


a year ago

you would need to build that functionality into your code


samuelbarnholdt
TRIALOP

a year ago

Can I somehow colocate A and B on the same machine? I won't have access to the code inside A


a year ago

yeah you could, but that comes with its own set of challenges


samuelbarnholdt
TRIALOP

a year ago

happy to take those on if I have to - unless you think there is a smarter way to accomplish this


samuelbarnholdt
TRIALOP

a year ago

essentially I want to run someones npm run dev -> embed it through an iframe -> modify code over API


a year ago

that sounds like a security nightmare


samuelbarnholdt
TRIALOP

a year ago

live and die by the sword I guess


a year ago

why run a development server anyway? that's costly and comes with its own issues


samuelbarnholdt
TRIALOP

a year ago

I'm trying to do dev environments for customers and want hot reload enabled


samuelbarnholdt
TRIALOP

a year ago

prompt to modify code stuff but with your actual code


a year ago

respectfully, I think you need to rethink this project, specifically so that you can easily run it on railway


samuelbarnholdt
TRIALOP

a year ago

As in this will be death to run on railway?


a year ago

railway or anywhere


samuelbarnholdt
TRIALOP

a year ago

I mean it's obv not ideal but is really that bad apart from it being a hassle and costly running dev?


a year ago

it's more than that, from my perspective it seems like the project is chalked full of bad practices.


a year 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.


Loading...