SSH Workaround?
I have Directus deployed as a service via a Docker image. I need to provide the application the "path to key file on disk" via an environment variable to enable file storage.
Any thoughts on how to go about this? Must I create a custom Dockerfile?
22 Replies
Project ID:
1ccd180a-5a98-431c-af65-1f09bf8fec13
ProjectID=1ccd180a-5a98-431c-af65-1f09bf8fec13
@Medim - think you can assist with this directus question
"Google Cloud Storage" to be specific.
going to be blunt, there are better and easier storage methods you could use that don't require you to place files on disk
for example, what's wrong with using the attached volume? that's already preconfigured for you
That was my first choice, however some of my client may fly through the current available storage. I want to ultimately move all of my clients over to Railway. Using GCS allows me to directly pass the storage cost to them.
yeah that makes sense, but I do stand by my statement, an S3 compatible storage provider would definitely be the move
putting a file onto disk (a volume) is generally not a straight forward task, and you definitely don't want to put that credential file in a repo, regardless if it's a private repo or not
Is there a way to directly access a volume, possibly storing the key file on there?
directly, no, that's why I have said that it's generally not straightforward
railway doesn't provide any kind of sftp access or a native filebrowser
all file access for the volume has to go through the service it's attached to, that's why it wouldn't be straightforward
Okay, hear me out... using the Railway CLI, it is possible to create a custom Dockerfile which includes the key file, and deploy directly to a service bypassing the risks of storing within a repository?
yes, railway up
S3 was only a suggestion because it's going to be easier in the long run to use a service like backblaze b2, but now you've got me curious, you seem to really wanna use Google for this, why is that, if you don't mind me asking?
Google simply has a simpler user interface than AWS.
First time hearing of backblaze b2. Looking into it now.
oh no i would never recommend someone to use aws
sorry if i was misleading
Successfully implemented using Storj. They're both web3 and s3 compatible.
Thank you for your assistance @Brody
oh perfect, that was actually going to be my second recommendation, guess i dropped the ball on just saying s3
No problem. You were a big help.
happy to help!
please stop closing the thread though
in 1 hour i can, at the gym atm nvm seems like its fixed
Now I'm curious @Prentiss, sorry for the ping and if I misinterpretated something, but are you using STORJ as STORAGE in Directus?
STORJ via their s3 api, as far as i can tell
Oh wow, that's super cool
Gonna do that on my Directus instance
didn't know storj had a sort of S3 Drop-in Gateway/Interface
Is actually working out great... so far at least. Good enough to where I many need to (no financial advice, lol).