Setup one click deployment to railway #356
Conversation
…adex/postiz-app into setup-one-click-deployment
|
@fadexadex is attempting to deploy a commit to the Listinai Team on Vercel. A member of the Team first needs to authorize it. |
|
This is so awesome! |
|
Oops I forgot to add the environment variables, let me get on that now, when a user runs a one click deploy, they would need to include their cloud fare info right? |
|
No, you created the volume with the /uploads, cloudflare is not necessary |
|
Alright, I am trying to redeploy with the required envs so I can test |
|
This is the link to the deployed app postiz-app-production-9283.up.railway.app The create account is not working as expected could it be because of the exclusion of the /config volume? |
|
Heya, at first I was a bit freaked out by this, but actually this generally looks fine. :-) I do worry a bit about having so much duplication between the two dockerfiles though, but I cannot see a way around this at the moment. So, this technically should work without /config or /uploads, as long as railway allows you to set runtime environement variables. Your test deployment isn't working at the moment because the NEXT_PUBLIC_BACKEND_URL is set to the default ( |
|
Ohh alright, I would make the change. |
|
So I made changes and redeployed but still have issues interacting with the deployed link |
|
Hello sir any help with this sir?@jamesread |
|
Yeah, so you've set it, but it's still set to the wrong values, so it's causing CORs errors. What's your public deployed URL, and your .env look like? |
|
|
|
API is wrongly configured, there is no any mapping to exposed port ( |
|
Can you please explain further, like it should be 3000 for the backend url? |
I'm not an official maintainer, just trying to deploy it with your solution. About the problem; I see that There should be logic that maps |
|
You should use port 5000 for everything, don't use the port :4200 and :3000 directly anymore. Check out the postiz docs on the pre-reqs to understand more. |
|
Has anyone had any success with this? |
What kind of change does this PR introduce?
I included two new files in the folder directory, "Dockerfile.railway" and railway.toml. I also included the template button link to the readme file to allow for a one click deploy on railway. I have tested the changes with a sample deployment on my railway dashboard to ensure the changes work as expected
Why was this change needed?
So the reason for the new file "Dockerfile.railway" was because volumes are banned in railway, so I was forced to use the inbuilt volume from railway and delete the volume declarations from the docker file. However, I didn't want to alter the main Dockerfile.dev so it doesn't affect the other one click deployment options that would be implemented later. The railway.toml file was to direct railway to the Docker file on the build instructions.
Other information:
Yes I chatted with the author of the issue for guidance while working on it. I had to also make a compromise with the VOLUME, instead of two I setup just one volume in the template which is "/upload", the reason for this is because railway doesn't allow creation of more than a single volume.
Checklist:
Put a "X" in the boxes below to indicate you have followed the checklist;